up vote 0 down vote favorite
share [g+] share [fb]

I have a home PC and a work PC right next to each other.

The work PC is connected to my corporate Lan, when it is connected I cannot RDC to it.

When it is not connected to the corporate Lan I can RDC to it find through my internal private IP's, 192.168.x.x.

So, I'm wondering to i need to build a special route on my work pc so it can still communicate via the internal address even though it is connected to the corporate lan via VPN software

or

what I have tried is to use 2 network connections, 1 for VPN and 1 that still has an internal IP that I can connect using RDP. The problem with this is when I do that it seems to break things on the VPN, maybe i need a way to say that only this network connection is used for this service? not sure how to get around it. Also as long as the VPN is connected, RDC still does not connect in this scenario.

link|improve this question
How are you connecting to your corporate LAN? Have you ensured that your firewall settings are not controlled by the company (ie: it gets "tighter" when on the domain, possibly denying RDP)? – techie007 Oct 14 '11 at 14:38
I'm using our own flavor if an IPSEC client, the Tech support guys use RDP to connect to fix things, so it must be open. – Scott Oct 14 '11 at 14:44
If I put the IP SEC client on my home PC, connect to the lan, then I can RDC, but that kinda defeats the point. – Scott Oct 14 '11 at 14:44
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.