I'm running into a strange problem at home.
Home PC: Dell 9150 Dekstop
OS: Windows Vista Ultimate
VPN: Cisco VPN 5.0 for Vista
Router: Dlink DGL4300
IP: 192.168.0.100 via static assignment
ISP: Optimum Online (Cablevision)
Work Machine
ell Optiplex 745c Desktop
OS: Windows XP w/ SP2
Remote Desktop Version: 6.0.6000
Scenario 1:
When working from home, I start up the Cisco VPN client on my home machine.
I can access network resources from my work network.
I then close out the VPN connection. I also exit the Cisco VPN software (from the system tray)
The next day, I head into work. From my work machine, I attempt to connect to my home machine via RDC. I cannot access my machine at home via RDC.
Scenario 2:
I cold boot my home machine. I do not start the Cisco VPN client and do not create a VPN session.
The next day, I go into work. From my work machine, I am able to connect to my home machine via RDC. Everything works as it should
--
What is happening here? Is it normal that when I run a VPN client on my home machine and then exit the VPN session/software that it somehow breaks RDC? Could it be that the VPN assigned IP address is somehow staying resident, and my router can no longer forward RDC requests to the machine because the IP isn't correct? This doesn't really make much sense, because when at home, I'm still able to access the network and all local resources in the home.
I've checked IPconfig, and it looks like the VPN Adapter IP is released.
I'd really like to figure this out as I hate having to reboot my machine everytime I use the VPN in order to clear this problem.
Any suggestions would be appreciated!
Thanks,
-Matt
Home PC: Dell 9150 Dekstop
OS: Windows Vista Ultimate
VPN: Cisco VPN 5.0 for Vista
Router: Dlink DGL4300
IP: 192.168.0.100 via static assignment
ISP: Optimum Online (Cablevision)
Work Machine
ell Optiplex 745c DesktopOS: Windows XP w/ SP2
Remote Desktop Version: 6.0.6000
Scenario 1:
When working from home, I start up the Cisco VPN client on my home machine.
I can access network resources from my work network.
I then close out the VPN connection. I also exit the Cisco VPN software (from the system tray)
The next day, I head into work. From my work machine, I attempt to connect to my home machine via RDC. I cannot access my machine at home via RDC.
Scenario 2:
I cold boot my home machine. I do not start the Cisco VPN client and do not create a VPN session.
The next day, I go into work. From my work machine, I am able to connect to my home machine via RDC. Everything works as it should
--
What is happening here? Is it normal that when I run a VPN client on my home machine and then exit the VPN session/software that it somehow breaks RDC? Could it be that the VPN assigned IP address is somehow staying resident, and my router can no longer forward RDC requests to the machine because the IP isn't correct? This doesn't really make much sense, because when at home, I'm still able to access the network and all local resources in the home.
I've checked IPconfig, and it looks like the VPN Adapter IP is released.
I'd really like to figure this out as I hate having to reboot my machine everytime I use the VPN in order to clear this problem.
Any suggestions would be appreciated!
Thanks,
-Matt
Facebook
Twitter