Windows Forum

Ask something
Discussion Locked

Problem accessing shared printer

0 helpful
13 replies

by greg.gotcher

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a shared printer on a Windows 2000 machine. It has a share name of \\payroll\payroll6422. I was able to access it and no longer can. Also when I go run and issue the command \\payroll, I get this message:

\\payroll is not accessible
There are currently no logon servers available to service the logon request

I tried uninstalling and reinstalling File and Printer sharing for Microsoft Networks. Any help is greatly appreciated.

13 replies

by maxwell edison

The WINS database does not have the proper domain registrations for pass- through authentication.

This problem occurs most often in environments where the administrator has created a two-way trust between two previously independent domains. Most often, there are WINS servers in each domain and the WINS servers do not replicate their databases to each other.

To resolve this problem:

Allow WINS dynamic registration.

This ensures that Domain Controllers register their DOMAIN<1C> NetBIOS names with the WINS Server.

Make certain that WINS database replication is successful between WINS Servers. Missing database entries for domain names may indicate Problems with the WINS Servers and replication.

To work around this problem:

NOTE: Microsoft does not recommend using static mappings in the WINS database for WINS enabled computers.

Run the WINS Administration Utility to add static mappings for the Domain<1C> registrations (of the trusted domain) that are not listed in the WINS database:

Name: Master DOMAIN Name
IP Address: Address of the Primary Domain Controller (PDC) of the
domain
Type: Domain Name

If you are logged on as an administrator at aDomain Controller, remote administration works now successfully. If you are attempting to remotely administer the domain while logged on to a Server (not a domain controller) or Windows NT Workstation, you must add DOMAIN<1C> entries for both the trusted and trusting domains.

More Information:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q139410

(REMOVE SPACES from the pasted URL.)

Maxwell

by maxwell edison

.
.
Another possibility:Check that the network cable is connected.

Check that that the NT logon server is up and running.

Don't use any special characters in the Computername

You try to logon with your fingerprint, using a smartcard, which has been enrolled on a domain (local or global), which doesn't exist on the NT workstation or on the connected network.

Maxwell

by greg.gotcher

I am not using a WINS database. I have an LMHOST file on each computer. The printing was up and working for about two weeks before it stopped.

by curlergirl

Check the permissions on the Windows 2000 machine where the printer is installed. Your user ID would have to have the rights to that computer and to the shared resource (printer) on that computer. If it did work at one time, possibly the permissions got changed or your password expired. Hope this helps!

by ustutz

Try this: In your LMHOSTS file(s) add an entry like:

10.10.10.10 "domainname \1B"

Where domainanme is the name of your domain, and the IP address is that of your PDC (emulator). You can also add the same receord with the \1C option as well.These entries add the domain controller registrations normally found in a WINS database to teh LMHOSTS file.

Also, your client workstation accounts with in the domain may have 'died'. Every so often, you just have to delete a workstation from the domain and re-add it.

by timthetoolman

Hi,

Check the event log on the Win2K server to look for clues on how to fix this.

You may see entries in the security area of unauthorised entry attempts of under system, you may see failed services.

Something to look at, anyway...

Cheers,
Tim.

This discussion is closed to new replies.