6 replies
by cg it
by larrys
by larrys
by nettek
It has been my experience that Win9x is less than reliable when it comes to remote access. I have found the following checklist helpful when trying to resolve remote access problems with 9x clients.
1. Make sure the local Windows 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 domain name.
3. Make sure you have the latest DUN, VPN, and RAS updates installed. You can find them at
http://www.microsoft.com/downloads/search.asp?LangID=20&LangDIR=en-us (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 on the clients.
6. If your are using laptops, and they are connected to your LAN via aNIC at some point, 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.
by larrys
by larrys
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending