Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Let's say I have a server at 12.34.56.78 that provides PPTP among other things. Right now I'm on a network that has most outbound ports blocked, and I'm using my VPN to break through the firewall. My server also provides a service on a port blocked by the network I'm on.

My problem is that even though I'm connected to my VPN at 12.34.56.78, I still can't connect to the blocked service. Looking in TCPView, it seems that connections to 12.34.56.78 are not routed through the VPN. Why? Can this be changed?

share|improve this question
    
You should revert your edit and post your edit as an answer if it is indeed fixed. You can even accept your own answer for that matter. –  Magellan Jan 27 '12 at 13:37
    
I meant to, but it said I had to wait 8 hours because I was a new user or something. Thanks. –  Kieran Menor Jan 27 '12 at 19:41

1 Answer 1

I managed to fix this myself by adding a new entry to my routing table with a lower metric value (second route).

 Destination          Netmask            Gateway          Interface   Metric
 12.34.56.78  255.255.255.255    <local gateway>  <local interface>     4251
 12.34.56.78  255.255.255.255   <remote gateway> <remote interface>      306

The first route was added upon connecting to the VPN. I don't know if there are any ill effects, though. The route seems to disappear automatically upon disconnecting from the VPN, so it has to be readded every time I connect.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.