The Hipersockets is strictly internal, and requires the user to point with the actual IP address.
The FTP is using the external 10.x.x.x links, and those are connected to a DNS. We can actually get from one LPAR to another LPAR using the domain names, but that does not use the Hipersockets. The /32 defined routes were not used, as they are added dynamically. On Thu, 2 Nov 2006 15:58:57 +0100, Chris Mason <[EMAIL PROTECTED]> wrote: >Matthew > >Thanks for letting us all know that something now works. > >However, there are two types of route, those to the Ethernet LAN and those >to the Hipersockets links. > >Which of these supports your FTP work? Have you performed any testing using >the other? > >Did you include the "/32" entries that I suggested may have been added >dynamically and hence do not need to be among the defined ROUTE statements? > >Chris Mason > >----- Original Message ----- >From: "Matthew Stitt" <[EMAIL PROTECTED]> >Newsgroups: bit.listserv.ibm-main >To: <[email protected]> >Sent: Friday, 27 October, 2006 9:31 PM >Subject: Re: I love TCPIP (not!) > > >Hi Chris; > >I think we've finally gotten a set of ROUTES definitions that are working. >I performed an FTP to the server after settting these up according to your >examples, and it worked. > >I'll keep monitoring things for a while. > >Thanks for your assistance and patience on this issue. Hopefully some >others on this list learned a few things. I know I did. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
