Windows Server route table problem


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 (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 ( and I want it to go to our firewall direct ( 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      1
Default Gateway:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
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.
If it doesn't mantion the letter P at the beginning of the routing line, then it's not persistant. I guess this is rather of a static route. As gnar suggested, check the advanced properties of your NIC on your exchange server to see if there are multiple DG, which is crazy thing to do. Remove any DG within the advanced tab and add the desired DG on your NIC.
If you find nothing on your exchange server, then that means that your router is configures to forward everything to the ISA server. Make sure that you have the following on your router

Let me know.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

DeanUnitedAuthor Commented:
tcp/ip properties:  the nic is pointing to our router so that is working.
DeanUnitedAuthor Commented:
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...

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

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

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.