Discussion Locked

Registry tweak for domain VPN on W/S

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

I would like to use an NT workstation as a VPN host for a domain with one NT Server PDC. The objective is to allow a user to get in over PPTP, log in with his domain username and password, and access shares on the server for which he has permissions. I have succesfully made the VPN connection from a laptop outside the LAN, but I had to create a local user account on the workstation to do that. I have heard there is a registry tweak that can be performd to allow one to use domain accounts instead of local user accounts, but I have not been able to find out how to do it. (BTW, I am using RAS, not RRAS, if that makes a difference.) How can I accomplish my goal of VPNing onto the workstation with a domain account and accessing appropriateshares on the Windows NT PDC? Please provide answers or links to documentation that is detailed enough to execute.

Thanks!

5 replies

by chriswales

First, make sure your RAS server can perform all typical network operations (e.g., browse the LAN, connect to LAN resources, connect to the Internet, browse the Internet). Then, *enable dial-up permission* for your account. problem you might encounter is when a connected client can't log on. You need to check three possible causes for this problem.

Configure domain and server accounts. RAS by default authenticates client credentials against the local SAM. A user can authenticate to a standalone server in two ways: with a local account on the RAS server or with a Registry edit that forces the server to authenticate credentials against the domain SAM. In all cases, the account you supply *must have permission to dial in*.
Configurecomputer accounts. If the client is an NT workstation or server, the computer must have an account in the domain. If the client is a new system, create the new computer account in Server Manager before you test the connection. If the client system already has an account on the network but has been disconnected for a week or more, the computer account password might not be synchronized with the server. Every computer account has a hidden password that the PDC resets automatically; if a system isoffline for a long period of time, the account password can be different on the PDC and the client. Ordinarily, you can delete and re-add the account to correct this problem.

If it's a 9x client, make sure you set the workgroup to the target NT domain name on all Win9x systems.

Registry Key:
HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Services \RASPPTPF \Parameters. If AllowPacketsForLocalMachine of REG_DWORD data type = 1, then the remote client can't see any other resources on yournetwork.

This discussion is closed to new replies.