HELP REQUIRED

  • Thread starter Thread starter John Dalton
  • Start date Start date
J

John Dalton

Help!
When all users try to connect to a network drive this is my errror message
they get, as of monday morning!

"There are currently no logon servers to service the logon request"

There are no other errors such as DNS, DHCP when logging on, but it just
doesn't map everyones drives.
All machines are ping'able from each other, but yet they will not connect to
shared network resources. Setup is Windows2000 Server, windows2000
wkstations. All on latest service packs from MS and Virus Check has showwn
nothing.
Everything was working fine on thursday last week, and no body has been on
the server!?! Or been able to change any setting over the network. Only
thing I know of that may have is AutoUpdate that is scheduled to run at 12pm
every friday.

Any help that can be given will be greatly appreciated.
PS. Could you post any replies to (e-mail address removed)

Regards,

John Dalton

--
Phoenix Ironworks Co. Limited.
Incorp. Stainless Steel Products

Newall Street,
Littleborough,
Lancashire.
OL15 9DW

Tel: 01706 378102
Fax: 01706 379937

Email: Sales<AT>phoenix-ironworks.co.uk
Web: www.phoenix-ironworks.co.uk


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone
else is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful.

Phoenix Ironworks Co. Limited will not be held liable for any computer
related viruses or other malicious software passed as a result of this email
being sent or forwarded to any parties. It is the sole responsibility of the
recipient to check the email and any attachments for viruses.
 
I've seen this several times, and it usually is a connectivity problem. I
had it happen on a client's network. We could ping everything, but could not
access resources with the same message. After about 2 hours of frustration,
we rebooted a switch, which sloved the problem ... go figure! Also DNS /
WINS errors. Make sure you can resolve by name, not just ping by IP address.
Check forward and reverse loookups.

....kurt
 
Thanks folks, it turned out to be a faulty Network card in the Server, got a
new one in now...

John
 
Back
Top