MS RDP client routing, WinXP.

Picture this!

WinXP client PC with NIC and modem.
Connected via NIC to the local LAN and participating in NT4 based domain.  It has access via MPLS based WAN to terminal servers at a remote site.  Using a current version of MS RDC I want to give the users access to the Terminal Servers (Win2kServers BTW) but via the modem, while they are still connected to the local LAN/WAN; so TCP/IP traffic to a specific number of servers running TS must be routed via the modem (either ISDN or POTS) not via the still connected NIC.

Yes I know it would be easier if I were connecting to a Win2003server and yes I know this can be accomplished with Citrix, but neither are an opption in this senario.

I'll give 500 pts for this one chaps but the answer must be comprehensive.

Let me know if you need any more info.

Thanks EE!
Who is Participating?
scampgbConnect With a Mentor Commented:
OK, making a bit more sense now.
I'm assuming that you've got a modem at the remote site you can dial into?

Unfortunately I don't have the kit to be able to test this out, but if you don't mind a bit of experimentation I've got a theory.

For the sake of demonstation, I'm assuming that you want to route traffic to over the modem, and everything else via the NIC.

On the client PC:
Go to a command prompt, run "ipconfig"
Note down the default gateway.  I'm assuming for this example.

Use the modem to dial-up to the central servers
Run "ipconfig" again.
You should see both the NIC details and the modem interface.  
Note down the default gateway here.  I assume  The modem will probably be the second one, it's important to note down the order.

route delete
route add mask metric 20 if 1             <- route all traffic via first interface, using default LAN gateway
route add mask metric 1 if 2           <- route to 192.168.5.x via second interface

Do some ping tests and see what happens :)

This is all a bit theoretical, and I've not been able to test it so I make no guarantees.

I'm picturing as best as I can, but I'm confused!

You have PCs on a LAN.  These PCs have access to the Terminal Servers over the LAN, but you want them to use a modem dial-in to access them?

It raises the question "why?".

I may be wrong, but when you dial-in the PC will automatically start routing outbound traffic over the dial in connection.
littlebuddahAuthor Commented:
Politics is the reason.

Since the WAN team "upgraded" the WAN and re-weighted the routing things have been a little unpredictable.  They admit there are issues and will resolve them in due course, no help to my users who need ad-hoc access to a couple of critical Apps on some TS servers on a different site.  

The problem is compouded by the fact that the WAN dosen't always just die when there is a problem but may just slow to a crawl or mis-route packets so its's hard to develop a system that can figure "oh the WAN's dropped out, I'll reroute the packets via [insert solution here]".  I have no authority to add routing records hence the reason I want a limited number of TS connections to route via a modem always whether it thinks the LAN/WAN is available or not.

With regards to your last comment, i've set up this type of system with Citrix for a previous company who gave customers and suppliers access to applications via a dial in Citrix server with a primary ISDN card, it was a good setup but one which I can't replicate here because of budget/politics, take your pick.

Hope this makes it a little clearer! and thanks for your reply Sampgb!
littlebuddahAuthor Commented:
Simple and effective!

I configured a RAS Profile and created a batch file along the lines of:

rasdial dialupconn [your pre-configred dial up connection] account password /DOMAIN:yourdomain /PHONE:yourRASnumber
sleep 1
route delete
route add mask [default LAN gateway] if 0x1 [NIC interface]
route add [TS server] mask [ip assigned to modem] if 0x20006 [modem interface]
start c:\default.rdp [call an RDP connection]

With this solution my users were able to use applications in an RDP session while still writing the output of the programs to servers on the local LAN segment while the WAN is down; all in about 20seconds with very little user interaction.

Exactly what I wanted to achieve, no compromise.

Big thanks to ScampGB!!!!  Now to allocate some well deserved points  ;)
Hi Littlebuddah - glad that I could help :-)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.