I have a NT server running with 3 client PCs....one of the clients is Win 98 and the other two are Win 95. I've had the entire network running for several months now with no problem. I'm not running DHCP, but, instead, have the server set up as 192.168.0.1 and the clients as 192.168.0.2, 3 and 4, respectively. I recently changed the subnet on the server and its address is now 192.168.1.100. I changed the clients' addresses as well, making them 192.168.1.101, 102, and 103, respectively. No problem with either Win 95 machine...they can both logon just as they did before. But with the Win 98 machine, I cannot logon. My Win 95 machines are working without specifying the domain name in the Client for Microsoft Network properties tab and they logon without a problem. I added the domain name to see if it made a difference and they were still able to logon. With the Win 98 machine, it doesn't seem to make a difference...with or without the domain name mention, it still won't sign on. The Win 98 machine can ping the server just fine and the server can ping it. The error message I get when the domain is not specified is: "The specified computer did not receive your request". The error message I get when the domain name is specified is: "The domain password you supplied is not correct, or access to your login server has been denied". I changed the workgroup name to be identical to the domain name & still received this message. Any help would be appreciated...thanks! Jim Lake jimclake@ix.netcom.com

Jim, Workgroup names, and domain names are independent of each other. Specifying the same name in both locations really won't help you. Have a look in your \windows directory for the file named "hosts.sam" and "hosts". If you have a hosts file, make sure the entries in there are correct. If you don't have one, get to a command prompt, and copy hosts.sam to hosts, then edit it. The file has enough instructions in it to direct you to make the proper changes. Just follow the pattern already set. There is another file that can mess things up. It's called the "lmhosts" file. Like the hosts file, it also contains hostname and IP's. You don't need this one, but if you use it, be sure they've both the the same information. Cheers! Chase

Thanks, Chase! You helped me solve the problem, although not in the way you mentioned! I checked the 2 Win 95 machines that could log on to the server. They had no hosts file but they did have a this hosts.sam file: ------------start of hosts.sam file---------- # Copyright (c) 1998 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98 # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost -------------end of hosts.sam file----------- The Win 98 machine had a 0 byte hosts file. I deleted it, re-booted the server & clients, and the Win 98 machine logged on successfully! Question, though...although we can log on to the NT server and access its shared drives, I still am unable to "browse the network". I get the message "Unable to browse the network. The network is not accessible". I don't think we've ever been able to do that although we can still access the server's shared drives, as I mentioned. Why would we get this message? Thanks!

Check your "Client for Microsoft Networks" to make sure there's a little check next to the "Log on to Windows NT domain" and your domain name is in there. Below that, you can check either Quick logon, or Logon and restore. I haven't foudn either one to make much practical difference. Also make sure your "Primary Network Logon" is set to "Client for Microsoft Networks" and that you're logging on with a valid userid. The problem you state sounds like the 9x machine hasn't recognized the actual network logon, so it doesn't think you're actually on a network, even though almost everything worls correctly. Good luck, Chase

I am having he same problem with remote locations at my site. I recently changed the TCP/IP settings on my PDC. My remote sites are no longer able to get to the PDC. The error message is "Access to logon Server has been denied."

Hy!@ I have the same problem, but my solution, was create a bat file... a:\win.bat attrib -a -r -s -h c:\windows\hosts attrib -a -r -s -h c:\windows\lmhosts nbtstat -RR #this command clean netbios map# nbtstat -c #this command show cached map# winipcfg /release winipcfg /renew ping (server_name) ^z Try this... Bye roger@rogerbernardi.com.br