|
Somebody lied. If you have a subnet of 255.255.255.240 then your address range is x.x.x.112 to 127. 112 would be the network address (not usable) and 127 is the broadcast address. Your valid addresses then are 113 to 126. SO to fix it you need an address on your 400 in the range above. I'll bet with the current .139 address you can't even ping the NT server or the router. The .112 to .140 address range makes NO sense at all. In fact unless you have an entire class 'C' (255.255.255.0 mask) you can't have addresses on both sides of .128 in the same subnet! HTH - Larry Jim Langston wrote: > > First of all, I'm on V3R7M0. > > I'm trying to set up my AS/400 so that it can "see" the internet. I > already have 2 NT servers talking to the internet with no problem. I > also have my AS/400 talking to my NT servers on a private sub network no > problem. > > I have my AS/400 set up with 192.168.1.61 with a netmask of > 255.255.255.0 and the NT servers on the same subnet, and they talk > together. > > Now, I have my NT servers on the internet, IP range of x.x.x.112 to 140, > 112 is broadcast, 113 is my router, which leaves me 114 to 139 usable > (don't remember what 140 is, but you can never use it either). They > gave us a subnet mask of 255.255.255.240 > > I set up a server with x.x.x.114, set up the default gateway, rebooted, > and am on the 'net. > > I tried the same with my AS/400, I added tcp/ip interface x.x.x.139, > subnet mask of 255.255.255.240, started the interface, then tried to add > a default route, but was having > problem, because my default gateway is x.x.x.127. The message was that > it was outside > of my subnet mask. I tried changing my subnet mask to x.x.x.0 and it > worked for > communication between my NT server and my AS/400, but when I added the > *DFTROUTE > it took it, but would not communicate with the internet (I tried PINGing > the same internet > machine from my NT machine, where it worked, and my AS/400, where it > didn't). > > Is there something I'm missing here? What is the piece of the puzzle > that is different > from talking to the internet and talking to "local" machines on the same > wire? > > Regards, > > A confused Jim Langston > > +--- > | 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 > +--- -- Larry Bolhuis | What do You want to Reload today? Arbor Solutions, Inc | Don't throw your PC out the window, (616) 451-2500 | throw WINDOWS out of your PC. (616) 451-2571 -fax | Two rules to success in life: lbolhui@ibm.net | 1. Never tell people everything you know. +--- | 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.
midrange.com
