Vista & XP Printer Sharing Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Vista and XP networked together. The XP strangely works fine. It
can access all the shared files and printers on the Vista machine. The Vista
machine can access files on the XP with no problem. It can also SEE all of
the XP's shared printers but when I try to connect all I get is:

Windows cannot connect to printer
Access is denied.

This occurs with any printer on the XP and with the firewall off. Any ideas?
 
If create the same user of the Vista in the XP, does that fix the problem? Please post back with the result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a Vista and XP networked together. The XP strangely works fine. It
can access all the shared files and printers on the Vista machine. The Vista
machine can access files on the XP with no problem. It can also SEE all of
the XP's shared printers but when I try to connect all I get is:

Windows cannot connect to printer
Access is denied.

This occurs with any printer on the XP and with the firewall off. Any ideas?
 
If create the same user of the Vista in the XP, does that fix the problem? Please post back with the result.
Click to expand...

Also, don't forget to use actual (identical) passwords for the same user on
all systems -- must NOT be blank!.
 
Thank You all,
Final problem came down to needing both xp patches (KB896427, KB922120) &
telling Norton Firewall on all machines to see the vista laptop's IP.
 
Thank you for the input and update.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Thank You all,
Final problem came down to needing both xp patches (KB896427, KB922120) &
telling Norton Firewall on all machines to see the vista laptop's IP.
 
CJD said:
Thank You all,
Final problem came down to needing both xp patches (KB896427, KB922120) &
telling Norton Firewall on all machines to see the vista laptop's IP.
Click to expand...

Have exactly the same problem. Must come up quite a lot, as surely lots of
people share their printer via an older XP machine and then add a Vista
device to their network?

Hopefuly those patchs will do the trick for me too.


Richard
 
Richard Clements said:
Have exactly the same problem. Must come up quite a lot, as surely lots of
people share their printer via an older XP machine and then add a Vista
device to their network?

Hopefuly those patchs will do the trick for me too.


Richard
Click to expand...

Nope still exactly the same problem. Have installed all latest patches on XP
and Vista. Installed the two mentioned above on XP.

On Vista I can view all my workgroups machines. I can double click on the XP
PC and view all it's shares and printers. I can share any of the files from
XP and view them on Vista.

As soon as I try to connect to the printer though, same error message about
not being able to connect.

Username and password same on XP and Vista. I'm not running any firewalls
other than windows firewall and defender. I'm stuck.


Richard
 
Suggest the method off adding the printer as a local printer, then changing
the port. Worked first time for me, after trying lots of other time wasting
things!


Richard
 
furnituremaven said:
I found out from Microsoft's KB that this problem seems to appear when
you have UAC turned off on the Vista computer. Once I turned User
Account Control back on my Vista laptop loaded the driver just fine and
all is working now.

Good luck!


--
furnituremaven
------------------------------------------------------------------------
furnituremaven's Profile: http://forums.techarena.in/member.php?userid=28420
View this thread: http://forums.techarena.in/showthread.php?t=722282

http://forums.techarena.in
Click to expand...

Nope I had UAC turned on, never turned it off (although it is pretty
annoying!).

Still recommend the work around detailed above that I ended up using, worked
first time and no problems since.


Richard
 
Back
Top