-----Original Message-----
Here is a challenge for you...
***Environment****
*NT 4.0 Domain...
*Various types of Network Printers spooled on NT 4.0 BDC
*Windows 2000 Professional SP3 Clients (Clean install,
Office 2000, McAfee 4.51, Custom Default User Profile with
IE Home page, Office Tool Bar, and Desktop Preconfigured,
[used a temporary local account called temp to create this
custom default user profile] Syspreped and cloned with
Ghost 6.5)
***Issue***
Installing a network printer works. Users able to print
ok. However print queue window does not display print jobs
user sent to printer so user is unable to manage own print
jobs, Users print job is visible from an NT Workstation
with same printer installed, Blue title bar
reads "PRINTERNAME ON SERVERNAME Access Denied, Unable to
connect." Users can print ok to this printer. Issue exist
on all types of printers and all Print Servers on domain.
These machines are also getting multiple Failure Audit
messages in the Security Event Viewer, Priviledge Use
Event ID: 577
Privileged Service Called:
Server: Security
Service: -
Primary User Name: "USERNAME"
Primary Domain: "DOMAINNAME"
Primary Logon ID: (0x0,0xDFE3)
Client User Name: -
Client Domain: -
Client Logon ID: -
Privileges: SeIncreaseBasePriorityPrivilege
Any Help is greatly appreciated.
Thanks
.
I am having a similar problem:
I have a small office network with 1 Windows 2000 Server
and about 10 Windows XP Pro workstations. All workstations
can print to the print queues on the win2k server,
however, when you open up the print queue for a particular
printer, it displays the error message you mentioned
above: "access denied, unable to connect". Any user logged
in to a workstation will see this problem, however, there
are a couple of workstations which don't have this problem
but I have yet to discover any configuration of registry
differences between these workstations and the ones that
don't work.
FYI: the Windows 2000 server is running SP3 and the XP Pro
workstations are running SP1 with the most recent Critical
Updates applied.
If you have had any success resolving this please let me
know... I have been searching for answers throughout the
Microsoft KB and the Internet for several weeks now and
have yet to make any headway.
Thanks,
David Mans
(e-mail address removed)
