Link to home
Start Free TrialLog in
Avatar of DeanUnited
DeanUnited

asked on

Windows Server route table problem

Hi,

I have a question. Im trying to get our exchange servers outbound email to go through our router default gateway.  The default gatway on the exchange serer is pointed to the router. I changed our router default gateway to 192.168.93.150 (our firewall).  I checked the ROUTE PRINT command on our exchange server and it had the route of below present. I deleted it (because it was going to our ISA server (192.168.93.155) and I want it to go to our firewall direct (192.168.93.150) for a test.

The problem is,  everytime I send an email on the exchange server the route below is added again.  I think this route is somehow persistant. How do  I check if it's presistant route or not? It comes back after each time I delete it.

Dean



    216.129.90.70  255.255.255.255   192.168.93.155   192.168.93.234      1
Default Gateway:    192.168.93.254
Avatar of gnar
gnar
Flag of United States of America image

Is it listed in the Advanced Settings for the TCP/IP properties on your NIC?  There's a default gateways area there that can have multiple routes listed.
Avatar of DrDave242
When you issue the "route print" command, the output includes a "Persistent Routes" section under the "Active Routes" section.  Any persistent routes that have been created will be shown in there.
ASKER CERTIFIED SOLUTION
Avatar of isaman07
isaman07
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DeanUnited
DeanUnited

ASKER

tcp/ip properties:  the nic is pointing to our router 192.168.93.254 so that is working.
I have two nics teamed. the teamed nic properties only have on DG.  ROUTE PRINT returns "no persistant routes"

I'll need to check the router like suggested.
Thanks so far...

Dean
Could you check your router to see what is the routing line for the 0.0.0.0

Harout
Looks like our router had a static route still in it. We'll remove it.

Thanks!