Can't Print to network share.

  • Thread starter Thread starter Shannon
  • Start date Start date
S

Shannon

User is getting message " There are currently no logon
servers available to service the logon request."

Environment:

PC1 has a local printer that is shared.
PC2 connects to this printer to print.

Both pc log onto a Domain set up on an Active Directory
Win2000 Server. This is the only server in the domain.
WINS services were never setup.

The Network Printer share worked untill will had problems
with our domain server. The Server started smoking and we
shut it down. It couldn't start up again. This is a know
issue will the manufacturers hardware. The Manufacturer
was scheduled to replace a faulty Perc controller a week
before this happen.

I only got a call a week after the server went down; from
the user that they were receiving this shared error
message and couldn't print. (MY QUESTION #1) I don't think
it could be because the server is down, or could it? Both
pc can ping each other. (QUESTION #2) If the pc that is
sharing the printer is configured to share to everyone;
shouldn't anyone on the network be able to access the
share regardless of them logging into a domain or not? Or,
is it because they are settup to log into a domain which
is down, that they can't share. (QUESTION #3) How is it
that the users are still able to log into their pc's if
the domain is down. They don't have local accounts that
logs onto the pc. When i setup up their login accounts, i
went computer manager, than to groups, than to users and
searched for their user accounts in the domain and added
them to users. (QUESTION #4)I believe this was the proper
way to set up a user logging into a domain? Is it? Im just
starting to learn about Active Directy. Our current
network to Novell, but im trying to convert our network to
Windows.
 
--------------------
From: "Shannon" <[email protected]>
Subject: Can't Print to network share.
Date: Thu, 8 Jan 2004 10:52:26 -0800
Newsgroups: microsoft.public.win2000.printing

User is getting message " There are currently no logon
servers available to service the logon request."

Environment:

PC1 has a local printer that is shared.
PC2 connects to this printer to print.

Both pc log onto a Domain set up on an Active Directory
Win2000 Server. This is the only server in the domain.
WINS services were never setup.

The Network Printer share worked untill will had problems
with our domain server. The Server started smoking and we
shut it down. It couldn't start up again. This is a know
issue will the manufacturers hardware. The Manufacturer
was scheduled to replace a faulty Perc controller a week
before this happen.

I only got a call a week after the server went down; from
the user that they were receiving this shared error
message and couldn't print. (MY QUESTION #1) I don't think
it could be because the server is down, or could it? Both
pc can ping each other. (QUESTION #2) If the pc that is
sharing the printer is configured to share to everyone;
shouldn't anyone on the network be able to access the
share regardless of them logging into a domain or not? Or,
is it because they are settup to log into a domain which
is down, that they can't share. (QUESTION #3) How is it
that the users are still able to log into their pc's if
the domain is down. They don't have local accounts that
logs onto the pc. When i setup up their login accounts, i
went computer manager, than to groups, than to users and
searched for their user accounts in the domain and added
them to users. (QUESTION #4)I believe this was the proper
way to set up a user logging into a domain? Is it? Im just
starting to learn about Active Directy. Our current
network to Novell, but im trying to convert our network to
Windows.
--

Shannon,

Your users are logging into the client systems using cached domain profiles\credentials. Since they are logging in using
these domain credentials when one tries to access resources on the other the system with the resources will attempt to
authenticate the credentials be passed by the connecting system. Since we currently do not have Domain Controller (DC)
up it is unable to authenticate\validate the credentials and the message we are seeing would then be displayed.

Once you get your DC backup and running this should resolve the message we are seeing.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
 
Back
Top