Question Locked

VPN RRAS as well as a hardware VPN

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok, there were a few topics similar to this already, but not quite with the setup I am working on.

So, I have 2 Private networks in different city's

Site A. 192.168.1.x + Dial in VPN with win2k3 using DHCP relay agent to get IP's from the router
Site B. 192.168.2.x

I have a hardware VPN setup (with 2 d-link routers) between the 2 networks, and both networks can see each other fine as well as ping and do windows shares, HOWEVER people on the dial in VPN can only see the network it is on (192.168.1.x), it does not seem to see the established VPN between the routers.

I'm sure I just have to set a static route in the windows RRAS but have had no luck with it thus far.

Any help would be greatly appreciated If it is a static route, can you give me an example of what i have to set in the fields? if I'm way off, a gentle push in the right direction would be nice

Thanks in advance!

Chad. E

O yeah, also there is only one network card in the Dial in server! (the other one died). It is set to a static IP, outside the DHCP range of the router of Site A.

11 replies

by cg it

you have a point to point VPN tunnel. Users must use that tunnel between the 2 networks to see both networks.

if you have a user that skips that tunnel and creates their own, that tunnel is between the client and whomever the client creates that VPN tunnel with.

That's why they can't see the point to point tunnel. Their simply not using it.

by oo_dragon

The dial in server is on the LAN that has the PP VPN setup on already, as well as the dial in clients are getting the DHCP info from that router that has the established VPN (AKA the IP info that is given out is the same info of all the computers on that LAN at Site A). So in theory should they not be able to see the routes just like all the other computers? If not I should just be able to set that static route in the RRAS options so it knows there is another Network it can access right? I would do this, but I'm not sure what info I have to put in there :P (cause i tried and failed already).

Also I'm not sure if i mentioned this, but the windows 2k3 VPN is going through the internet, its not an actually phone line dial in VPN (not that it should matter).

by cg it

if your clients dialup something using POTS they aren't using the point to point tunnel therefore cant see it let alone use it.

the point to point tunnel is a persistent tunnel. It's always there. clients just need to create a network connection that uses that tunnel.

you CAN create a connection via VPN to a remote network and that connection is the same as if you were directly connected to the LAN. Then use the remote LAN resources and even their internet connection. but if you want to connect using 1 VPN tunnel then turn around and use a remote network VPN tunnel back [basically making a circle], what's the point?

by oo_dragon

Ok, maybe I'm not explaining it quite right...

to start, forget the "dial in VPN"

I have 2 sites already setup with a hardware VPN (the constant VPN connection you spoke of). Now its working great, both sides see each other etc.
Now here is where the "dial in VPN" comes in. lets say Some one from this company goes to there moms house and wants to grab a few files from their work computer, so he dials in to the Windows 2K3 server over the internet. He connects OK, and can access the files on the network he is connected to (aka Site A), but his computer/Data is at Site B. but he cant access site B for some reason using the "dial in VPN".

So I want him to be able to access site B using the "dial in VPN" at site A.

So we know Site A can access site B already, just the people using the "dial in vpn" cant.

help.

by cg it

VPN in creates a tunnel connection that's unique between the client initiating the tunnel and the other client that accepts the tunnel. in this case it's between the server and the client.

A point to point VPN tunnel is a persistant tunnel between 2 points. in your case I'll assume it's router to router. clients do not initiate the tunnel, rather access it to pass data between the two points. It's almost like having a dedicated line.

What you want is to have another VPN point on your W2003 Server where clients VPN to the server, are assigned a LAN IP address and are connected just like if they were on the server LAN. that would let them access everything available on the LAN that directly connected clients have, excluding the VPN tunnel to another site because that would require creating a second connection between the remote VPN client to the server and then the remote VPN client to the persistant VPN tunnel between to endpoints.

The real question is, do clients on Site A & B have a LAN network connection they have to use to access the point to point VPN tunnel?

If that is the case, then the remote client can not establish a second VPN network connection while connected to the W2003 Server while the first VPN connection is active. Remote Desktop would give you this ability as your connected remotely to one computer and then use that computers network connection to initiate another network connection to access the point to point tunnel.

by oo_dragon

what you said
"What you want is to have another VPN point on your W2003 Server where clients VPN to the server, are assigned a LAN IP address and are connected just like if they were on the server LAN." Yeah that's what i have setup right now. Basically I forwarded the VPN ports through the router to the win2k3 server. But if i understand you right, your saying anyone that "dials in" to create the VPN connection to the server will only be able to see the network the server is directly connected to? There is no way to connect it to another subnet?

by cg it

because the client can only initialize 1 VPN [Virtual Private Network] connection at a time.

This discussion is closed to new replies.