WINS/DHCP? problem

[hillboy]

Halfway through the day many of our users received the following message when trying to log onto the network:

" No domain server was available to validate your password. You may not be able to gain access to some network resources." All network access was denied to these users.

All of the users were able to log on earlier in the day, but received the message after logging off/on sometime in the afternoon.

All users were configured to use DHCP and were using Windows 98 machines (none of the statically IP assigned or W2K machines were affected).

I was able to workaround the problem by assigning a static IP address. However, I will need to solve this since I have approximately 200 '98/DHCP users on this node of the network.

We should I start?!!!!! I looked at the DHCP Server configuration and replicated (pushed/pulled) WINS to no avail. Nothing seems out of the ordinary.

 

[djhawthorn]

Have you set up your DHCP scope with a WINS Server entry, and a WINS/NBT Node Type?

 

[Guest_imported]

hi,
did you get a solution to your DHCP problem you described on Jul 31, 2002 ?
I have the same problem and would be glad to resove it.
Thanks for your reply.

franmem
email without the begining "bee"
beefranmem@bluewin.ch

 

[Guest_imported]

hi,
did you get a solution to your DHCP problem you described on Jul 31, 2002 ?
I have the same problem and would be glad to resove it.
Thanks for your reply.

franmem
email without the begining "bee"
beefranmem@bluewin.ch

 

[Guest_imported]

hi,
did you get a solution to your DHCP problem you described on Jul 31, 2002 ?
I have the same problem and would be glad to resove it.
Thanks for your reply.

franmem
email without the begining "bee"
beefranmem@bluewin.ch

 

[Yardyy]

Hi Hillboy,

Did the problem get solved, really like to know what happened as i have a similiar problem.. Regards

Yardyy

 

[Guest_imported]

This problem can have many causes.

First question I would have is have you checked your Event Viewer for any futher information. Both System and Application?

Start at the workstation:

1. When this happens goto each of the workstations and do a few tests.
2. Do IPConfig /all record all this information.
3. Do netstat -r to get your routing information.
4. Try rebooting one machine and see if the problem clears.

Goto the server.

1. If your getting the IP's from NT make sure your scope is not too small that the machines in question are not actuall getting and IP. if its 2000 worstation you would see and address of 169.*.*.* meaning you actually did not get an IP.
2. If your connection to the server is a switch. Have your administrator check to see if the port that it is connected to is taking errors. These ports have the threshold that when they reach they basically reset themselves causing loss of connectivity.

The only time I personally have seen this happen in my many years is when the servers are build on very slow low spec machines with power management. For some reason I think the machine attempts to put it self in sleep mode and it never comes back. I have heard others that have had everything from hardware issues with LAN equipment to problems with bad drivers on the NIC to SID problems from inproper cloning to IP conflicts with the server.

If you get this info and still need help post the details from you test and ill see if I can help you.