|
I think this will solve my problem (thanks Ray Peterson): That's your problem. The 192.168.1.x subnet is defined for your ethernet, and cannot also be your ppp. I'm assuming you have a subnet mask on the ethernet of 255.255.255.0. Somebody owns the 1.1.1.1 address, so you definitely shouldn't be using it. You should just use one of the public address ranges - I use the 172.20.x.x subnet. If you are using 255.255.255.0 as your subnet mask on the ethernet, then you could use 192.168.2.1 and 192.168.2.2 on the ppp for example. I know that the following ranges are labeled as private by RFC 1918 and are available to you. 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 Ray At 05:33 PM 12/14/1999 -0500, you wrote: >When you dial in and fail you'll have a job log under the name of the >profile. Examine it and see where the failure is occurring. It's >probably on adding a route. What sort of routing parms have you set >anyway? If the connection appears to go active but you can't "see" the >other end, check NETSTAT and see what routes and masks have been added >that relate to this link - there should be just one with the IP address >for the remote and a mask of *HOST (255.255.255.255). The IP address for >the PC that you enter under DUN and what you enter for the remote IP >address on the OPs Nav don't have to be the same. If you see the >connection in the 400 netstat try ping the PC. This should tell us if >the routing problem is from the 400 or the PC end. > >TrailBlazer Systems, Inc. >http://www.as400ftp.com >AS/400 Communications & E-Commerce Solutions > >Chaos, panic, & disorder - my work here is done. > >> -----Original Message----- >> From: Jerome Draper [SMTP:jdraper@wco.com] >> Sent: Tuesday, December 14, 1999 1:12 PM >> To: MIDRANGE-L@midrange.com >> Subject: Re: PPP dialup and IP numbers >> >> One more element is that the ethernet adapter on the AS/400 is set to >> 192.168.1.100 >> >> Jerry >> >> At 09:04 PM 12/13/1999 -0500, you wrote: >> >Jerry, what are you using for a mask? 255.255.255.0? >> > >> >_______________________ >> >Booth Martin >> >boothm@earth.goddard.edu >> >http://www.spy.net/~booth >> >_______________________ >> > >> > >> > >> > >> >Jerome Draper <jdraper@wco.com> >> >Sent by: owner-midrange-l@midrange.com >> >12/13/1999 08:19 PM >> >Please respond to MIDRANGE-L >> > >> > >> > To: midrange-l@midrange.com >> > cc: >> > Subject: PPP dialup and IP numbers >> > >> >I got the RS232 com port on a mod 170 configured for PPP dialup via >> OOPS >> >NAV (thanks everyone). The com port on the AS400 is 192.168.1.111 >> and the >> >PC I'm using for dialup is 192.168.1.110. Strangely, it doesn't work >> but >> >when I change the AS400 com port to 1.1.1.1 and the PC to 1.1.1.2 it >> works >> >fine. >> > >> >What gives? >> > >> Jerry Draper, Trilobyte Software Systems, since 1976 Specializing in connecting PC's, Windows, MAC's, and LAN's to the AS/400 Representing Synapse, Apple, IBM, UDS, Nlynx, MI, Perle, Netsoft, etc. (415) 457-3431; (415) 258-1658fax; jdraper@wco.com +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.