Win95 clients can't logon to win2k server after 2 days?

[BJacques]

I just installed win2k server SP3 and am running it with winXP and win95 clients. My problem is with the win95 clients (dynamic ip), after approximately 48 hours they can no longer logon (password incorrect or access to server denied) is the error. The clients can ping the server, and by giving the error that it does, it seems to find it and know it's the domain controller... The winXP pro clients work fine.

After rebooting the server the win95 clients can connect no problem, for about 48 hours... If they logoff the network they are not allowed back on.

I think it may be a security problem, but don't know, I'm new to win2k server. Maybe the server does not reissue the tickets??

Single Win2k Server DHCP, WINS, DNS

Need any more info?
Thanks in advance!

 

[butchrecon]

Create a new file called LMHOSTS (NO extension ie .txt .doc). add the following to it....
192.168.1.1 Servername #PRE #DOMOMAIN
where the IP address is your server IP. Servername is the name of your server. and DOMAIN is your domain name. If you are not running a WINS server then this should help. If yo are running WINS then this wont hurt. Let me know if this help. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[BJacques]

Thanks I will try that. I am using WINS...

I believe it has something to do with the VPN and WINS. Seems when I connected through it last night it cause a master browser election and it looks like my Laptop won. This cause a netbt error and a conflict with the domain servers wins entry.

I've found some information on this and since set the IsDomain registry key to TRUE on the server, and turned off the Computer Browser service on my laptop.

The only way I can really test this is to VPN again and see if this happens.
The same thing happened two nights ago, after I had VPNed no win95 clients could logon.

I'm still looking for other ideas...

 

[Dazzleman]

BrianJacques,

I believe that you are going in the right direction. We had similar issues with 95 workstations until we took away their ability to become a Browse Master and installed the AD patch.

I cheered the day our last Win95 and W98 box went away and we could shut down WINS

JDazell@buckeye-express.com

 

[BJacques]

It is the RAS that is doing it, the winxp laptops are becoming wins domain controllers and browser masters when they connect through RAS. It happened again last night.

There must be a fix for this other then turning off the browser in all the winxp laptops...

Can I not tell the server to deny a client from taking over the role of domain controller and master browser in wins? What am I missing here??
In the meantime I have turned off RAS.