• Subject: Re: DB2 Connect error
  • From: Howard Weatherly <hweatherly@xxxxxxxxxxxx>
  • Date: Thu, 22 Jul 1999 09:03:35 -0400

Perhaps a bit late, but DRDA uses port 460.

Murphy, Guy wrote:
> 
>         No.  Tcp/ip is a protocol.  Services which use tcp/ip are
> assigned ports.  Telnet is assigned port 23, http is assigned port 80,
> ftp ports 20 and 21, etc.  There are 65535 ports available under
> tcp/ip and whatever service the DB2Connect client connects to on the
> 400 has to be assigned one of them.  Your DB2Connect client has to
> know what port it's supposted to use to connect the 400.  This info
> might be contained in an .ini file associated with DB2Connect or it
> might be in the Windows registry file.  To see what services are
> active on your 400 and what ports they're using, type NETSTAT *CNN on
> a command line.
> 
> 
> 
> Guy Murphy - FACTS system
> University of Illinois
> 217-333-8670
> 
> -----Original Message-----
> From: Wayne Capwell [mailto:wayne@redoaktech.com]
> Sent: Wednesday, July 21, 1999 9:09 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: DB2 Connect error
> 
> According to the installation manual, DB2Connect runs over TCP/IP with
> 
> no other products required on the 400 side.  The client does ask for a
> 
> port number during the installation.  Is there a default port number
> for
> the AS/400 TCP/IP?
> 
> > "Murphy, Guy" wrote:
> >
> >         We don't use this product but what the hell, I'll take a
> guess
> > at yout problem.  Is there an AS/400 component that has to be
> running
> > when you connect?  Does it have the same port assignment that your
> > client expects?
> >
> > Guy Murphy - FACTS system
> > University of Illinois
> > 217-333-8670
> >
> > -----Original Message-----
> > From: Wayne Capwell [mailto:wayne@redoaktech.com]
> > Sent: Tuesday, July 20, 1999 6:48 AM
> > To: midrange
> > Subject: DB2 Connect error
> >
> > Hello again,
> > I tried this post on Friday and got no response.  Am I the only one
> > attempting to use DB2 Connect?  I'll try this again and hope for
> some
> > help.
> >
> > I am attempting to connect a Win95 workstation to our AS/400 running
> 
> > V4R2 using IBM's DB2 Connect Personnel Edition over TCP/IP.  I can
> > ping
> > the AS/400 and have network access to the AS/400 from other Win95
> PC's
> >
> > on the same network using Client Access.  I get the following error
> > message when I try to search of a database on the AS/400.
> > _________________________________________________
> > The connection test failed.
> >
> > [IBM][CLI Driver] SQL30081N  A communication error has been
> detected.
> > Communication protocol being used: "TCP/IP".  Communication API
> being
> > used: "SOCKETS".  Location where the error was detected: "".
> > Communication function detecting the error: "gethostbyname".
> Protocol
> >
> > specific error code(s): "*", "11002", "*".  SQLSTATE=08001
> > ____________________________________________________
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].