"Could not connect to the printer..." error on W2K Pro

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Pat_McCrotch (anonymous_at_discussions.microsoft.com)
Date: 05/20/04 

Date: Wed, 19 May 2004 21:56:04 -0700

"Could not connect to the printer..." error on W2K Pro
I have an NT 4.0 server which hosts several shared printers. On
Monday, two of my W2K Pro SP4 users complained that they cannot
connect to any printers shared on this or any server. All other users
are fine.

On closer inspection, they both get the "Could not Connect to the
printer. You either entered a printer Name that was incorrect or the
specified printer is no longer connected to the server" message when
they try to add a shared printer.

Here's a few quick facts:

* both users are administrators on their machines
* the same thing occurs even when domain admins logon to their
machines
* both users can browse and connect to all network shares
* I have tried renaming and rejoining the machines to the domain
* I removed all anti virus software
* The same thing occurs when starting in safe mode with networking
* I removed all hotfixes - no luck. I reapplied SP4, no luck.
* I checked DNS/Wins etc - all ok
* I can successfully print directly to the printer via IP
* it's not licence logging or anything - all licence logging is
disabled
* both machines are free of viruses, spyware and adware.

I'm tearing my hair out over this one. Please help!

Thanks - PmC
Australia
Post a follow-up to

Relevant Pages

  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • "Could not connect to the printer..." error on W2K Pro
    ... I have an NT 4.0 server which hosts several shared printers. ... two of my W2K Pro SP4 users complained that they cannot ... * both users are administrators on their machines ...
    (microsoft.public.win2000.printing)
  • Re: Two XP Questions for new XP Pro User
    ... > Hello - I have just upgraded two of my Home LAN machines to XP Pro from ... > I've done this after having sucessfully upgrading my PDC from NT4 Server ...
    (microsoft.public.windowsxp.basics)
  • Re: XP Home Edition
    ... > XP Home can connect to Server 2003 provided the ... Upgrading to XP Pro is an option, but at almost $200 per copy it may not ... be worth the price if the machines will be replaced anyhow. ...
    (microsoft.public.windows.server.sbs)
  • EnterpriseService Component: problem enlisting in a distributed transaction
    ... developing that is responsible for writing data to an SQL Server. ... The problem host machines are running Windows 2000 Pro, ... The ES Component is set to Require transactions. ...
    (microsoft.public.sqlserver.programming)