Windows Forum

Ask something
Discussion Locked

Client route to Exchange Server wrong

0 helpful
8 replies

by sdschafer

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
If anyone can help with this I would be greatful. The company that I work for has 8 remote sites and a 4.0 bdc at each site. The PDC is at the HQ building, there are also some W2K member servers at HQ mixed in. Once in a while, in a remote site, a user will not be able to get into the Exchange 5.5 Server at HQ. They are able to ping other servers (locally and at HQ) but not the Exchange Server. The routing table has the wrong info in it for the client computer. Once you delete the route, it works fine again. Is there a way to stop the routing table from getting incorrect routes?

8 replies

by shmaltz

How are the sites connected?
You didn't give enough information.
The routes don't get messed up for no good reason, something has to be done that this should happen. Usualy this will happen if one of the connections is not available.

by sdschafer

The other thing is if it couldn't find the connection, everyone at the site should be getting bad routes, this is not the case, it only happens to one person and then it could not happen for weeks.

by sturner

Add a static route. THen regardless of the incorrect route it may recive it will have the static route to fall back on

by sdschafer

The IP addresses are given out dynamically to the clients, so there is really no way to add a static route.

This discussion is closed to new replies.