SageTV and VPN issues

[DarkWolf77]

Hi there,

I've looked around the forums to see if anyone else has had the issue, but it seems most of the entries are about connecting to sage via a VPN... not the problem I'm having.

Basically, I have a Cisco VPN connection to the office that I use to connect to work when I'm working at home. The same computer I use for that doubles as my Sage server. The problem is, that if I do not completely disable the VPN software (stop the service and exit the software), Sage for some reason wants to listen on the IP address associated with the VPN connection instead of the local IP address of the machine, so when that happens, all my HD-300s stop being able to connect to the Sage server. I've tried manually configuring the internet connection in the GUI, but it doesn't let me set the listening IP, only the tcp port.

So when I have the VPN enabled and connected, my network connections look like this:

Cisco Systems vpn adapter, IP 999.bla.bla.bla, "VPN Network Connection"
Networking Controller, IP 10.bla.bla.bla, "Local Area Connection"
(Not real IP's of course )
And Sage listens on 999.bla.bla.bla tcp 31099 instead of 10.bla.bla.bla.

Any ideas?

[gplasky]

Try moving your regular wired connection higher in priorty than the Ciscon VPN. I think in Windows 7 go to Go to Control Panel -> Network and Sharing Center -> Change adapter settings -> Then hit Alt to get the menu and choose Advanced -> Advanced Settings.

Then you can re-order your connections in that list.


Gerry

[david1234]

I think you may just be out of luck. Running a VPN client on your Sage server is going to be difficult.

While your connected to VPN, that connection, very properly, takes over, so you aren't connecting a foreign network to your work network.

Once you disconnect VPN, you have to restart anything that was connected through it in order to have it switch back to the local network.

[Taddeusz]

There is a way for it to work but I believe it requires your company to do the proper routing so that your local network is still accessible (i.e. your web browser goes through your internet rather than through the VPN).

[sflamm]

gplasky is correct. In windows the way to put local routes first is to change the priority... this has long been a known issue/solution.

[brewston]

Cisco VPN has an 'allow local network' setting but this can be disabled at the other end. You can always run VPN in a VM

[DarkWolf77]

Hm... thanks guys, I'll have to check it out when I get home from the office.