In order to talk (e.g., 'ping'), the sender must have a route to the receiver *and* the receiver must have a route back to the sender (for the replies!!) :) If you are on 1.x and have a route to 2.0 route -p add 192.168.2.0 mask 255.255.255.0 192.168.1.3 metric 1 then your packets can get *to* any 2.x box. *But*, that 2.x box, *itself*, must have route to the 192.168.1.0/24 network (or at least its default route must lead toward someone that has such a route). The reason that you can ping 2.3 is because that box *does* have route to 1.0 -- his own NIC, 192.168.1.3, on that network !! You conveniently left out the routing tables from any 2.x box :) Let's suppose that the 2.x boxes are defaulting to the other NT box, 192.168.2.2. Then on *that* NT box, add a specific route back to 1.0. route -p add 192.168.1.0 mask 255.255.255.0 192.168.2.3 metric 1 It should then work (even though it would be more efficient for each 2.x box to have that route, itself). ----------------------------------------------- Tks | [EMAIL PROTECTED] BV | [EMAIL PROTECTED] Sr. Tech. Consultant, SBM Vox 770-623-3430 11455 Lakefield Dr. Fax 770-623-3429 Duluth, GA 30097-1511 =============================================== -----Original Message----- From: Windows NT/2000 Discussion List [mailto:[EMAIL PROTECTED]]On Behalf Of Clark, Pete Sent: Thursday, February 01, 2001 2:08 PM To: [EMAIL PROTECTED] Subject: Re: NT Routing Problems I believe that your gateway setting for the .2.0 network is misconfigured. You have: 192.168.2.0 255.255.255.0 192.168.2.2 192.168.2.3 >From your description, it should be: 192.168.2.0 255.255.255.0 192.168.2.3 192.168.2.3 - Pete Clark > -----Original Message----- > From: Scott Daves [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 01, 2001 12:00 PM > To: [EMAIL PROTECTED] > Subject: NT Routing Problems > > > Hi all - pardon the "brief" background ... have a subnet > routing problem, > here's my configuration. I have two separate networks A & B > - the primary > server in each lan has two NICs, one of which is connected up > to a cable > modem to the internet. I am not only routing but providing > NAT also. The > two networks are 192.168.1.0 and 192.168.2.0. I also have another NT > server (.1.3) that was providing DHCP, File & Print Sharing > for my A lan. > I have since tackled converting my B lan to DHCP also, so I > installed a > second NIC (.2.3) in my NT DHCP server, created a new scope and it's > working great. I then decided I wanted to route between > networks up so I > could administer remotely from my workstation. So I added > some default > routes for each network to my common NT box ... see below. > > Destination Netmask Gateway Interface > 0.0.0.0 0.0.0.0 192.168.1.2 192.168.1.3 > 192.168.1.0 255.255.255.0 192.168.1.3 192.168.1.3 > 192.168.1.3 255.255.255.255 127.0.0.1 127.0.0.1 > 192.168.1.255 255.255.255.255 192.168.1.3 192.168.1.3 > 192.168.2.0 255.255.255.0 192.168.2.2 192.168.2.3 > 192.168.2.3 255.255.255.255 127.0.0.1 127.0.0.1 > 192.168.2.255 255.255.255.255 192.168.2.3 192.168.2.3 > > From my A lan primary server (.1.2), I send all traffic destined to > the .2.0 subnet to the common NT server (.1.3), otherwise all > traffic goes > out to the cable modem gateway and to the internet. > > From my NT DHCP Server, I can ping anybody on either network - no > problems. However, from my .1.x workstation I can ping to > .1.3 The NIC in the NT Server on my network > .2.3 The other NIC in the same NT server > but not to any other .2.x addresses, to include my server. I > feel it must > be a simple routing issue on my common NT box but it is > eluding me. The > fact I can ping the other network's NIC in the NT box confuses me - it > indicates to me that I am successfully sending .2.0 traffic > to that box but > that that box isn't properly routing then on. > > And yes, I have Enable IP Forwarding checked and have loaded > RIP. Could > RIP be overriding my static routes? Are both needed? > > HELP!?!? > > TIA > > Scott -------------------------------------------------------------------------- The WINNT-L list is hosted on a Windows NT(TM) machine running L-Soft international's LISTSERV(R) software. For subscription/signoff info and archives, see http://peach.ease.lsoft.com/archives/winnt-l.html . _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]