14 replies
by mckaytech
From your description, it sounds like something happened to your routing tables and the problem is in the router itself (since the routers can ping each other, I'm assuming the WAN is okay). If you have information from when the routers were set upand known to be working, you need to compare that information with the current configuration. My guess is that you lost a static mapping from the LAN port to the WAN port and once you restore it, you'll be okay.
paul
by joshg
After I got the routes back in order I still couldn't contact the servers by name, I could ping just fine. After that I looked towards WINS. The WINS addresses got changed some how to point to an unpopulated backup WINS server. I pointed the boxes to the correct WINS servers and we are back in business. As to why this happened ????
Thank you
by arwjnplanotx
When you say multihomed, what are the NT boxes connected to other than the subnets?
If your default gateway is correct then verify that your subnetmask is correct. The IP address and the subnet mask must be set for the network it is connected to. Each NIC should be set for the network it is connected to. One thing about the subnet mask it can be wrong and you will still be able to have some network connectivity. If the subnet mask is the problem then it's making your computers think the addresses they are pinging are local.
Also the NIC should be pointing to the near side of the routers.
by joshg
by steve cody
Do your multi-homed NT servers have more than one default route? If so, that is not a good idea. Go in and set one default route, then go to the routing table and edit it manually for any other routes. I use batch files to set up my additional routes on my server. Go to a Command prompt and type ROUTE PRINT. This will list the routes. Also, do a TRACERT to the IP address on the other side of your routers. Watch the path and see if it is going to the correct router. Also, make sure your subnet masks are correct. If they are wrong that will cause you all kinds of routing problems.
- Steve
by joshg
by phinaddict
IT sounds to me like you have lost a static route. Do a route print and check everything out. You might need to add something back in using route add. We had a similar problem and this resolved it for us.
Good luck
by joshg
You need to clarify. Especially your statement on multi-homed NT boxes. Are they on the same subnet? None of them can ping the far side? WHat is the IP address scheme? Subnetting scheme? You said ALl the routers can ping the NT boxes, but the NT boxes cannot ping the other side of the WAN?! Then that would indicate an OUTGOING routing problem. If you have Cisco routers you can view the IP packets by debuging IP packets.
Tracert can be used on both routers and NT as well. Check your routing tables on the routers and their protocols. If the NT boxes are on different subnet, check thier tables.
by joshg
by _degan_
One good thing to check is that your multi-homed NT boxes on have a default gateway associated on one address, blank out the others.
For more information:
Do your routers use static or dynamic tables?
Does pinging work with IP adress and not NetBIOS name?
by joshg
by nrodriguez
routing table are screwed!
but since you said they are multihomed i am assuming you have multiple nics in your servers. if this is so add RIP under service in the network control panel. this will pretty much allow anything to go through untilyou get the tables are fixed. it will require a reboot. but it will dynamically learn the routes kind-a-sorta. but it will work
on your routers what kind of routing protocol are they using. you need to have them all the same. (ex. rip, igrp, egrp,...)
hope this helps
by joshg
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending