Vpn routing problem in windows 7

December 23, 2010 at 01:55:04
Specs: Windows 7
Hi
I have the following situation:
I want to connect from home (win 7) to work "server"(also win 7) via vpn to be able to use the ip from the work network. i configured it to accept incominc connections, everythig is ok, i can connect fine, i see the local connection. the problem is that i cannot figure out how to route my home pc connection to go out to the internet on the same adapter as the one it comes in. is this even possible? i get assigned a local ip (192.xxx), but i cant seem to figure out this routing
thank you very much

See More: Vpn routing problem in windows 7

Report •

#1
December 23, 2010 at 05:58:28
i see that there is a similar problem if i try to connect from the internal network from work to the server via vpn. same thing, no routing. what can i do? thank you

Report •

#2
December 23, 2010 at 07:27:49
everythig is ok, i can connect fine, i see the local connection. the problem is that i cannot figure out how to route my home pc connection to go out to the internet on the same adapter as the one it comes in. is this even possible? i get assigned a local ip (192.xxx), but i cant seem to figure out this routing

When connected to your VPN, if it's configured correctly, you get an internal IP from the VPN server. When attempting to surf the web, you should be going out the same way as any internal client does.

The fact that it's not happening, both when you connect remotely via the VPN and locally on the LAN to the VPN server makes me think you have the TCP/IP settings in the DHCP service associated with the VPN configured incorrectly.

That's where I'd start looking.

Without knowing more about your setup, that's all I can tell you. It would be nice to know what you're using for your VPN endpoint. I know it's not a Windows 7 box. I must be a Windows 2000/2003/2008 server or a VPN device.

Some detail might help pinpoint the problem.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#3
December 23, 2010 at 09:16:07
the "server" IS a win 7 pro pc :)
the vpn server is created by "new incoming connection" and the client connects directly via windows 7 client
the virtual interface is assigned a local ip, yes, and the routing is like this:
192.168.0.101 255.255.255.255 On-link 192.168.0.101 291
192.168.0.104 255.255.255.255 192.168.0.104 192.168.0.101 36
101 is the interface and 104 is the client. the problem is the routing, but i dont know very much about routing
thank you very much

Report •

Related Solutions

#4
December 23, 2010 at 09:17:41
maybe ics doesnt know to route both adapters to my net connection? both thel "real" local one, an the virtual one?

Report •

#5
December 23, 2010 at 09:51:47
Well, there's your trouble, trying to setup Win 7 as a VPN.........lol.

I have no real experience with 7 yet. I've looked at it but that's all. I suspect if it's designed to do VPN then it should be able to and I suspect the issue you're having is with your DHCP setup.

Since this isn't a network issue, you should ask over in the Windows 7 forum where people who do have experience with 7 hang out.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#6
December 23, 2010 at 09:59:09
how come it isnt a network issue if it is a routing issue? :)
and i think i would have the same problem if there was no vpn involved
let's say i drop the vpn. if i have one external interface(connected to internet) and i want to route 2 different local subnets on 2 different adapters so that i have internet acces on both of them, how would i do that?
ics only knows to route one
thank you

Report •

#7
December 23, 2010 at 13:51:10
"to go out to the internet on the same adapter as the one it comes in. is this even possible?"

That's just it. Its not possble. You can't "route" on the same subnet.

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#8
December 23, 2010 at 23:16:29
but it doesnt need to route the same subnet. the one coming in is assigned a virtual adapter... and this works on win server with rras. it should work here also, but i need the right route added manually

Report •

#9
December 24, 2010 at 05:43:28
x.x.x.101 and x.x.x.104 are in the same subnet and you can't route in the same subnet.

This 'route', excuse my pun, is a dead end

Now if you had two wan interfaces with two different lan ips you could have one wan on one interface/ip and outgoing route would be to the other interface/ip and then you would be routing.

Answers are only as good as the information you provide.
How to properly post a question:


Report •

Ask Question