Intermittant login problem

[PatBo]

Any help or direction appreciated, just back from holidays and maybe I am not up to speed yet!!
Server: PDC NT4 SP6 and BDC NT4 with Exchange 5.5 with Win98 workstations(100+)
Unable to pin down a pattern but this is what happens:
a) Unable to log in, switch PC on and off a few times then ok. Next day same again!
b) Logon on and all ok, log out and then unable to log back in.
c) Same results using admin or client passwords.
d) Laptops - login ok as profile already on laptop - no Internet/Emails/mapped drives - connection unavailable. Username new to laptop - unable to login - domain unavailable!
e) Wanted to run a 'GHOST' session similar result, some PC's connected others did not. Reboot a few times and eventually connected. GHOST image successful but then similar login problems.

The symptoms are random across the network clients, nothing seems adrift! Example - ICT Room with 14 PC's, 5 ok the rest nothing. Next day 8 ok the rest nothing and it will be different PC's each time.


Slán agus beannacht.
Patrick Boland

 

[PatBo]

No takers? Problem still there.
This message on 1 PC this morning:
'The system has detected an IP address conflict with another system on the Network. The local interface has been disabled. More details are available in the system event log. Consult your system administrator to resolve the conflict'
Event Log messages
1) The IP address lease 1--.1--.-.1-- for the Network Card with network address 004......... has been denied by the DHCP server 1-.1--.1-.1 (The DHCP Server sent a DHCPNACK message).
2) No Windows NT or Windows 2000 Domain Controller is available for domain ABCDEFG. The following error occurred:
There are currently no logon servers available to service the logon request.

After reboot - no problems. Willing to checkout any ideas.
Thanks in advance again.


Slán agus beannacht.
Patrick Boland

 

[h5n1]

lol...sounds like a network problem more than anything else....your switch, cabling or nic....how big is your network? take everything off and just leave 1 server and 1 client and let that try to log in....then go 1 by 1 from there and if there's an ip conflict, you'll know right away which one....but make sure you do monitor all your client as well as the server since conflict message only appears on the machine who get kicks out....