Windows Forum

Ask something
Discussion Locked

MS VPN Solutions Sucks!

0 helpful
5 replies

by tmcdowell

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Win2000 VPN server running on a NT4 domain. VPN server is running fine and clients authenticate, map drives, map printers, and browse maped resources. BUT, clients cannot browse the internal LAN via "my network places" and see the resourceson our LAN. Clients point to WINS and DNS servers, we have tried using a LMHOSTS file and static mappings in the WINS database. NO luck yet! MS says everthing should be working fine...but it ain't....Any suggestions?

5 replies

by bcross

Some history on how things should be set up:

1. Your VPN server must be running Active Directory

2. If you run Active Directory and have NT 4.0 boxes on your network, they must either be member servers or BDC's, not a one can be a PDC because your Win2K box which has active directory uses a "PDC Emulator" and will reek havok

3. Win2K makes little use of Wins and netbios name resolution. They want you to go to a more DNS'y solution. Make sure your Win2K server is running DHCP and DNS aswell (I'd personally distribute the fuctions across several W2KSVR's, but I don't have all the details).

4. Use only TCP/IP. Config your DHCP svr Scope settings to send the users DNS info.

The biggest thing is having Active Directory installed. Run DCPROMO to install it. Without active directory, your computer cannot be a domain controller, and if it isn't a domain controller, my guess is, it won't let your client PC's browse anything other than local resources.

by mgo

When you use ipconfig does it specify the domain suffix. If it doesn't that might be the problem. On the client specifiy the connection suffix or install a DHCP relay agent on the RRAS server. There is actually a note in the Windows 2000 resource kit about it. Hope it helps a bit.

This discussion is closed to new replies.