 moschopsPremium join:2003-12-20 Oakland, CA | [XP] RIP listener service breaks NetBIOS browsingI have three machines connected to a single subnet 10.0.1.x which has a D-Link DI-804HV router running DHCP.
Also on the subnet is an NetGear MR314 router-access point with DHCP disabled and no WAN connection - its just acting as an access point to put the 10.0.1.x subnet out over WiFi.
Everything works fine until I turn on the RIP listener service on one of the PCs. Then start having problems browsing the Windows network via NetBIOS - i.e. I can no longer ping via the computer names, just via IP address (which works fine).
It looks like an extra entry in the route table is appearing when I turn on RIP listener... thats even when no other computer has the RIP listener service running (or routing and remote access services running) and neither the MR314 or D-I-804HV has RIP enabled.
Here's the router table before RIP listener is enabled:
Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.0.1.1 10.0.1.3 20 10.0.1.0 255.255.255.0 10.0.1.3 10.0.1.3 20 10.0.1.3 255.255.255.255 127.0.0.1 127.0.0.1 20 10.255.255.255 255.255.255.255 10.0.1.3 10.0.1.3 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 10.0.1.3 10.0.1.3 20 255.255.255.255 255.255.255.255 10.0.1.3 10.0.1.3 1 Default Gateway: 10.0.1.1
and after:
Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.0.1.1 10.0.1.3 20 10.0.1.0 255.255.255.0 10.0.1.3 10.0.1.3 20 10.0.1.0 255.255.255.0 10.0.1.1 10.0.1.3 2 10.0.1.3 255.255.255.255 127.0.0.1 127.0.0.1 20 10.0.2.0 255.255.255.0 10.0.1.4 10.0.1.3 2 10.255.255.255 255.255.255.255 10.0.1.3 10.0.1.3 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 10.0.1.3 10.0.1.3 20 255.255.255.255 255.255.255.255 10.0.1.3 10.0.1.3 1 Default Gateway: 10.0.1.1
I don't know where this extra 10.0.1.0 subnet route with a gateway of 10.0.1.1 is coming from, if I do route -f it goes away and shows up in a few seconds.
But I can still ping all the machines in the subnet just fine, however the NetBIOS browsing breaks. To prove this I use the nbstat -R command to flush the NetBIOS tables and then ping a host on the subnet by its name and it fails. If I remove the route and quickly retry it works. If I remove the route, wait for it to come back, ping by name and it fails.
So my guess is the new route is interfering with broadcast on the subnet.
I'm not sure if there is really an utility to enabling RIP listener on any of the PCs - can someone say if its worth it? The alternative is to just enable the "Routing and remote access" service on all PCs and routers which I believe implements RIPv2 in and out. So longer as the RIP listening service is not running that works fine, although again, I'm not sure what the benefit is, especially on a single subnet. |
|
 army dudePremium,MVM join:2002-12-17 The Internet | I think you would only need to enable RIP if you had a PC with 2 NICs and were using it as a router...even then, RIP is a "dynamic" way to learn routes and populate it's routing table. You could just use static routes and leave RIP turned off. Since your network already has a router, what happens if you just leave RIP turned off on the PCs? |
|
 army dudePremium,MVM join:2002-12-17 The Internet 1 edit | Also leave "Routing and Remote Access" turned off...again, this should only be needed (on a PC) if you want to use this PC as a router. As long as you have "Default Gateway" set on each PC and it points to your inside interface of your edge router of that subnet, that (and good DNS) is all they should need for Internet access. Local network resources are, local, and therefore don't need a "route" to be able to find them.
Hope this helps. |
|
 moschopsPremium join:2003-12-20 Oakland, CA | reply to army dude
Re: [XP] RIP listener service breaks NetBIOS brows Well, I wondered if they were doing anything useful. I'd enabled them last week when I was experimenting with bridging two subnets. But I've removed those now so I guess they are superfluous.
But I wonder where the bogus route was coming from every time I enabled RIP listener service? Those things bother me.... |
|