I agree with Svyatoslav. See the link below if you have not already where
Microsoft does not recommend using a Windows 2003 VPN using L2TP/ipsec
server behind a NAT device/firewall if that is what you are using on your
network. --- Steve
We do not recommend Internet Protocol security (IPSec) network address
translation (NAT) traversal (NAT-T) for Windows deployments that include VPN
servers and that are located behind network address translators. When a
server is behind a network address translator, and the server uses IPSec
NAT-T, unintended side effects may occur because of the way that network
address translators translate network traffic.
If you where to set up a VPN Server, where would you typical place it?
I plan to set up a W2K3 server as a VPN server for out little network.
Should we locate it in the DMZ or could we safely located within our
internal LAN and only open the necessary ports to allow inbound connection
to it? We plan to use L2TP/Ipsec with digital certifictes.
Re: [Full-disclosure] Remote Desktop Command Fixation Attacks ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ... (Full-Disclosure)
Re: VPN with SBS 2003 (not R2) and DSL. ... Reading property value for VPN returned OK ...Reading VPN Server Name returned OK ...identical network cards.... it seems doubtful that SBS will work properly with two NICs ... (microsoft.public.windows.server.sbs)
RE: VPN Connection Problems ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ... (microsoft.public.windows.server.sbs)
Re: VPN clients unable to connect to other resources. ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ...client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ... (microsoft.public.windows.server.sbs)
Re: RRAS as VPN Server Configuration Questions... ...Ethernet adapter VPN:... Name resulotion on VPN Connection issues on DC, ISA, DNS and WINS server as ... Issue in a VPN client ... ... How to Setup Windows, Network, VPN & Remote Access on ... (microsoft.public.win2000.ras_routing)
