Networks

The essence of VPN is to create a Virtual encapsulated 'tunnel' using a range of internet portals. Depending on whether you choose IPSec, L2TP, or by Windows default VPN protocol [the least secure by the way] PPTP, will govern how simplistic and/or secure your VPN is. But by creating an 'external' VPN tunnel to the corporate network does not have to impose how the LAN or 'internal' network devices gain access. Either by an 'intranet' to a locally hosted webserver, client/server, or workgroup environment. The use of GPO's are a good thing AND will affect Remote Users and Local Users if configured properly. Careful with Local Policy vs. Group Policy settings and whether or not you are using Active Directory. Certain aspects of domain policy management are overwritten in User Profiles, especially if accessing the Server via Terminal Services Client/RDP.

I use a tier system of Remote User vs. Domain User vs. Terminal Server credentials. A layered approach is far more secure than leaving the front door wide open for User convenience in my opinion. Better to have layers of authentication which is less work than one Username/Password combination.

Hope this helps a bit!

Here's a link to a tutorial I put together a little while ago to show how to configure a basic 2003 VPN server using PPTP:

http://www.dslreports.com/forum/remark,15190829

Ideally, you'll need to enusure the laptops are already part of the domain along with having the required group policies pushed to them prior to deploying them in the field.

Jay

hello, its all sorted now thank you