I have done extensive searches on this but I can't find anything but do excuse me if this is covered elsewhere.
I'm running Merlin 378.55 on a n66u and have port forwarded some ports to a windows 8 machine on my LAN. This all works fine until I have the windows 8 machine connect to a VPN via windows in built VPN PPTP client. After that trying to hit the forwarded ports via the n66u just doesn't work. Whats weird is that internally on my LAN other machines can hit the windows 8 machine on the open ports even when the windows 8 machine is connected to the VPN. I assumed that if the ports can be accessed locally then then the port forwarding from n66u is as though the requests are coming for the local lan and it simply nat's them back out to the remote client.
Any thoughts or am I missing something?
Thanks in advance.
				
			I'm running Merlin 378.55 on a n66u and have port forwarded some ports to a windows 8 machine on my LAN. This all works fine until I have the windows 8 machine connect to a VPN via windows in built VPN PPTP client. After that trying to hit the forwarded ports via the n66u just doesn't work. Whats weird is that internally on my LAN other machines can hit the windows 8 machine on the open ports even when the windows 8 machine is connected to the VPN. I assumed that if the ports can be accessed locally then then the port forwarding from n66u is as though the requests are coming for the local lan and it simply nat's them back out to the remote client.
Any thoughts or am I missing something?
Thanks in advance.
 
	

 
			
 If you run cmd.exe as administrator and type route print you will see the routing table.  The table is processed bottom up and the LOWER (smaller number) metric gets higher priority.  So increase the metric (bigger number) on the PIA until you see the metric of that interface ip is numerically higher on the routing table.  I say to use the routing table because it is the end all- the actual number you input as the metric in the settings will be modified by the os to some extent and the routing table gives you the real deal.
  If you run cmd.exe as administrator and type route print you will see the routing table.  The table is processed bottom up and the LOWER (smaller number) metric gets higher priority.  So increase the metric (bigger number) on the PIA until you see the metric of that interface ip is numerically higher on the routing table.  I say to use the routing table because it is the end all- the actual number you input as the metric in the settings will be modified by the os to some extent and the routing table gives you the real deal.
 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		