W2k server sp3. After patches, issues w routing.

  • Thread starter Thread starter Edwin Davidson
  • Start date Start date
E

Edwin Davidson

I have a default gateway that is a W2k server running sp3.

It has a default gateway of another router which connects us to the
internet. This is connected to the server via a crossover cable, and
is working fine.

I also have routes defined to the server for other networks on our
LAN/MAN/WAN's.

As an example, our local network is 192.168.0.0 and this W2k server
has a route to 192.168.100.0 via router 192.168.0.10.

The problem is, after I installed the latest hotfixes to SP3 the
server is no longer redirecting clients to the proper internal routers
for local net blocks.

The odd part is that if I do a TRACERT 192.168.100.15 then it traces
correctly and I get a dynamic route to the 192.168.100.x network. But
unless I do a tracert on the client, then the client cannot connect to
these local networks.

I am using RRAS (vs. the registry hack to turn on routing.)

Ideas?

Edwin Davidson
 
Packet sniffing reveals that the server isn't issuing a redirect to
the correct router.

As an example, if I specify to telnet to a remote network, I see in my
route table the remote network next hop is the IP of this server.
What should happen is the server should do an (ICMP) redirect and tell
my PC what router to use. My route table should then reflect the
correct router for the remote host.

This isn't happening..?

If I ping the remote host, my routing table then becomes updated with
the correct information (for ~10 minutes) but If I try to access the
remote host before pinging, it just fails.

Is there a setting in RRAS or a registry hack to fix this?
 
Back
Top