Question Locked

Network printer listed but can't connect

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

I will try to be concise --
Problem: Cannot connect w/s1 (XP/SP2) to shared printer on w/s2 (XP/SP3)
Process: On w/s1 I tried to add a network printer by browsing and selecting from 'find a printer in the diectory'. resulting error = Windows cannot connect to the printer - it then suggests that it is was spelt incorrectly or the printer's connection to the server was lost (not - w/s2 continues to print fine). Same error if I enter/force it to UNC \\server\printer. Windows Troubleshooter should be shot -obviously no help. If I try to connect to it as a local printer and create a new local port '\\server\printer' I get error = network path not found.
Attempts: I have removed and readded file and printer sharing on both w/s1 and w/s2. I have removed and readded and shared the printer on w/s2. I have verified w/s1 can still print to shared printer on w/s3.
Post Script: this shared printer on w/s2 had been set up on w/s1 previously, then after creating a new useer on w/s1 the shared printer in question dissappeared. I am trying to readd it using domain admin account..
Resolution: That's where you people take up the torch. Feel free to jump right in. I hope I haven't overlooked something mundain and had a stupid attack.

7 replies

by larryd4

Signin to the PC with the share as the local admin.

1. Delete the printer
2. Delete the drivers
Go to File - Server Properties and delete all of the drivers not needed.
3. Reinstall Printer as the local Admin and share it out.

Try to connect to the printer from the other PC and print.

by ccurry

thanks but no go. Local admin total pruge and reistall of printer was unsuccessful.
In addition, I've had discovered that w/s1 will not connect to any (tried 6) shared comodity (printer, folder etc.) on any w/s - only on a domain controller. At this point w/s shared have been verified wide open - everyone/all, max #, etc...

by larryd4

Could this be a rights issue? Is the computer account ok on the network?

And is their anything in the event logs on the respective systems?

by Former member

If the printer is a true network printer then make sure that the drivers are on each machine.
If this printer is of the USB type and you are trying to add it to your other computer then what you need to do is:
1). Turn off the printer.
2). Take it off the computer it is attached to.
3). Plug it back in to the computer and make sure you can print from it, if ok then good.
4). Make the hdd in the computer that the printer is attached to as shared.
5). Go to the other computer and open up your network connection icon and select the machine that the printer is connect to and the printer should be shown, click on it, it should now say something like "connecting to printer" and then say "wait while adding drivers" or something similar. keep this window open and go to your printer section and see if the printer is in there. If it is then mark it as DEFAULT. Now you should be able to print out from these two machines.
You might need to re-boot both computers for this to work.

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

by ccurry

Drivers are installed (uninstalled, reinstalled...) on each machine.
It was working working previously as per PS on OP.
I ndertand it ought to be as easy as your step 5 - it has been for the past 1000 times, but this one is causing me to pull my hair out.
Thanks though

by ccurry

The computer account in AD is good.
User rights don't get much better than domain and loacl admin.
The event logs just show an event ID4356 = The COM+ Event System failed to create an instance of the subscriber... Can't see that it's at all related. This occured on both w/s1 and w/s2 after boot up this am.
Where did that hammer go...

This discussion is closed to new replies.