Discussion Locked

WIN98 will resolve Ip# over DUN

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

I have a NT server acting as RAS, there is also WINS and DNS running on the same server

If I dial up from NT W/S it works but from a WINS98/95 I can ping the server by IP# but not by name and I also cannot open Outlook2000 or browser the network If anyone could help with this one I would be most grateful.

5 replies

by nettek

Try the following on your 9x machines:
1. Make sure the workgroup name on the RAS client is the same as the workgroup name or domain of your LAN.
2. If you are using DHCP, make sure you have configured the DHCP scope to provide WINs addresses. Youmay even have to go as far as manually inputting the WINs server IP address under the TCP/IP properties of the DUN settings. You definitely need to do this if your clients have static IP addresses.
3. Your WINs server should not be multihomed (two NICs in one server, each connected to a different network).
4. Verify that you selected the "Allow RAS clients to access entire network option on the NT RAS server" if you want the clients to be able to see other network resources other than the RASserver.
5. If the remote client is a laptop that was recently connected via a LAN connection, allow enough time for the browse list to drop the machine before dialing in. Otherwise, a conflict can occur.
6. For your Win95 clients, download and install the the Dial Up Networking patch:
http://www.microsoft.com/downloads/release.asp?ReleaseID=12646 (there should be no spaces in this link)
7. Download and install RASUPD.EXE for 95 OSR1 clients. Install RAS2UPD.EXE for OSR 2 and 2.1 clients. You'll find them at the MS Knowledge Base under article Q154434.

by ann777

You need an LMHOSTS file on the client computers accessing your servers through RAS. LMHOSTS will have the ip address and name of the computer on the network.

This discussion is closed to new replies.