"Add A Printer" Wizard Fails To Find Network Printer

[mbhinz]

1. The firewalls have been properly enabled.
2. The printer has been shared.
3. The network has a setup disc created and run on both computers.
4. The "add a printer" wizard run.
5. My own printer and the workgroup is displayed, only.

Neither "Browse" nor \\computername\printername will connect to the external
printer. I am out of all ideas. I have followed all help files and
instructions. Nothing works. The wizard just hangs waiting for information.
Can anyone offer a suggestion?

 

[Lem]

1. The firewalls have been properly enabled.
2. The printer has been shared.
3. The network has a setup disc created and run on both computers.
4. The "add a printer" wizard run.
5. My own printer and the workgroup is displayed, only.

Neither "Browse" nor \\computername\printername will connect to the external
printer. I am out of all ideas. I have followed all help files and
instructions. Nothing works. The wizard just hangs waiting for information.
Can anyone offer a suggestion?

On the computer to which the printer is actually connected, share a
file. Can you access this file from the other computer? If not, what
error message do you get?

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

 

[smlunatick]

Check anti-virus Internet worm protection module. As a sample, Norton
Anti-Virus Internet Worm protection module blocks all "NetBIOS" name
resolution, which will not let you see any PC by computer name
(\\computername.) As to test this out, if you were to try by IP address
(\\192.168.1.1) you should be able to see the printer.

 

[mbhinz]

Thanks for your interest in my network difficulty.

By entering

\\computername\filename

or

\\192.168.15.101\filename

the error received is : "No Network Provider Accepted the Given Path". Not
very helpful, I'm afraid, as I already knew that. The question is why. I have
followed all microsoft instructions from help files and knowledge bases to no
avail. There must be something I have forgotten, but cannot imagine what it
might be.

 

[smlunatick]

Thanks for your interest in my network difficulty.

By entering

\\computername\filename

or

\\192.168.15.101\filename

the error received is : "No Network Provider Accepted the Given Path".  Not
very helpful, I'm afraid, as I already knew that. The question is why. I have
followed all microsoft instructions from help files and knowledge bases tono
avail. There must be something I have forgotten, but cannot imagine what it
might be.






- Show quoted text -

Go to My Network Places and browse to \\192.168.15.101 and you should
the "shared" printer name.

 

[Lem]

Go to My Network Places and browse to \\192.168.15.101 and you should
the "shared" printer name.

See if this helps:
http://support.microsoft.com/kb/841570/en-us

You'll need either your Windows XP install CD or a C:\i386 directory on
your hard drive.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

 

[mbhinz]

See if this helps:
http://support.microsoft.com/kb/841570/en-us

You'll need either your Windows XP install CD or a C:\i386 directory on
your hard drive.

--
Lem -- MS-MVP

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

Thank you Lem for the http://support.microsoft.com/kb/841570/en-us
suggestion. Although the sfc complained about a missing .dll, which it
removed from off the install CD, mup.sys did not prove to be corrupted or
missing.

One odd thing that I did notice is that the wizard will automatically enable
the windows firewall regardless if a personal one is already installed. I
thought that this might be complicating things. Nevertheless, shuting down
the personal firewall had no effect. I am ready to declare defeat, I can not
solve this problem. In over 30 years working with computers, I have never run
into such an obstinate and undocumented OS.