Directing traffic from one server between two different routers.


We have two Cisco ASA 5505's on two different DSL lines.  Their internal IP addresses are on the same LAN and on the same subnet.  One is and the other is  We have a Windows 2003 server on the same LAN and subnet ( that we would like to be able to RDP to from either of the outside lines.  However, since the default gateway of this server points to the .254 router, we cannot access it from the outside address of the .253 router with RDP because the connection tries to send information back out of the .254 router (Thus giving a "denied, no tcp connection" error).  Is there any way we can use the ROUTE command on this server, or any other method to tell it to send data it receives from the .253 router back to the .253 router so clients can access the server from either outside IP address?

Let me know if I need to clarify anything or go into more detail.

Thank you
OAC TechnologyProfessional NerdsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

You can give a Windows machine more than one default gateway

The problem is you can never, with any great certainty determine which will be used consistently.
No, you won't be able to do that because you are allowing RDP traffic inbound through each firewall from anywhere, I assume, and there is no differentiating factor you can use in a route statement on the server to point return traffic to one firewall or the other.

The best I can think of to do is to configure remote access VPN connectivity for external RDP access to the server with each firewall handing out a separate set of DHCP addresses to the VPN clients.  Then you could configure a static route on the server that points traffic to the .253 firewall for addresses that are in that firewalls DHCP pool.  The default route that is already pointing to .254 will take care of the DHCP pool of addresses in the other firewall so you don't need a separate static route for that one.

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
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

From novice to tech pro — start learning today.