Use the following checklist to resolve your problem:
1. Make sure the local Windows 95 username and password (the *.pwl list in your system.ini file) match the username and password of your NT domain.
2. Make sure your workgroup name = your domainname.
3. Make sure you have the latest Win95 DUN client installed. You can find this at http://www.microsoft.com/downloads/release.asp?ReleaseID=12646 (there should be no spaces in this link)
4. If you are using DHCP to provide the clients with the WINs server and gateway IP addresses, it is often unreliable. Try manually inputting the WINs and gateway IP addresses in the TCP/IP properties of the DUN settings of the clients. You definitely need to do this if you are using static addresses onthe clients.
5. For Windows 95 and Windows 95 OSR1 download and install rasupd.exe. For Windows 95 OSR2, install ras2upd.exe. You will find the download link at the MS Knowledge Base under article Q154434 (It solves other problems in addition to "No domain controller available...") You must have DUN1.3 installed first.
6. If your laptops are connected to your LAN via a nic at sometime, allow sufficient time for the master browser to drop your laptops from the browse list before connecting thru the VPN.
If those to tips don't solve the problem...
7. Add LMHOSTS files to the clients. You definitely need this if you are not running WINs.
As a last resort (it will add to your network overhead)...
8. Install NetBEUI as a protocol on your network. It usually eliminates all RAS browsing problems.