VPN Server 2008 single NIC router
I need some advice and I can't find a thread pertaining specifically to my issue. I am trying to to setup a VPN on Windows Server 2008 that is behind a Linksys router using a single NIC. I install Routing and Remote access. I couldn't connect to to the VPN from a remote location until I configured a static pool of IP addresses different fro mthe DHCP range the router was assigning to the internal network. Now I can connect to the VPN but cannot see the network. For troubleshooting purposes I disabled NAP policies and allowed unrestricted acces to connecting clients. Still no network through the VPN. If I install a second NIC will this fix my problem or is there something involved with being behind a router that I am missing? The routerneeds to be there for a wireless network in the office. Currently the setup is Verizon DSL modem---->router----->ServerI need the VPN for employess to access files on the Server only. I was under the impression that using a single NIC was possible. I don't know a lot about policies so maybe my issue is there. Any help will be greatly appreciated. Thank you.
May 29th, 2009 6:16pm
Hello,During configuration wizard setup, did you choose custom configurationsand then select VPN since you are using one NIC?Isaac Oben MCITP:EA, MCSE
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2009 8:37pm
Yes I did
May 29th, 2009 11:58pm
i alslo might add that I didn't do anything to the default policies. I'm sure it's something to do wth NAT
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2009 12:00am
hi Authenticx,i see that you have posted your query in 2 different / multiple forums, this will introduce confusion among the engineers. Please post your query always in one forum . Duplicate post thanks for understanding.sainath
windows driver development.
June 1st, 2009 8:41pm
dude I had exactly the same problem and I DID solve it :lets neme the range your linksys assigns to your local network is rangeA.the range your VPN server pool assigns to your VPN clients is rangeB.does the linksys(or any client on your home network which your VPN clients want to have interaction with) is aware of the rangeB you have on your VPN? in my case the answer was NO.
this is what happens:your VPN clients send a packet over the tunnel they have on rangeB.the VPN server ROUTEs ( not NATs) that packet to rangeA and delivers it to the linksys (or another intended node on the home network),but the linksys(that client) doesn't know where to send the reply back,so no communication happens.
solution: add a static entry for rangeB on linksys or any home client which is supposed to be accessible by VPN users.that route would look like this:
<dest=rangeB> <netmask=netmask_rangeB> <gateway=the address of VPN server on rangeA>
this way you don't need to NAT you VPN addresses,the VPN addresses natively will work on your home network,ALL WITH ONE NIC.
refer to your clients on your home network to see how to add a static route on them.in windows it is the command line "route" command,the linksys routers have a section of "advanced routing",etc.
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2009 1:16pm
I has the same problem but i have D-link router.
It resolved by your solution . Tnk Sasi2
June 24th, 2010 9:03am