Cannot share a printer due to errror 0x0000052f

[Chaim613]

Hi,
I am not able to share a printer via Homegroup, where the printer is connected on the USB port of the computer that hosts the Homegroup.
the printer works fine on the computer it is connected to, indicating the driver is OK.
Another computer on the Homegroup can search the host computer, but it cannot access the printer due to error 0x0000052f.
I think that error is due to a corrupted file, whether it is a system file on the secondary Homegroup computer, I don't know.
I've tried several things:

• starting again from scratch, 1) disabling the anti-virus program 2) disabling the Homegroup 3) unconnecting the printer and reconnecting it 3) re-creating the homegroup 4) trying to add a printer to the secondary computer, and getting the message "error 0x0000052f"
• manually investigating the Registry Hkey_Local_Machine>Software>Microsoft>Windows>CurrentVersion>Run where I expected there to be a error 0x0000052f file but found nothing
• invested in a Registry cleaner "RegCurePro" which didn't change the problem

Can anyone suggest what I should do next?
Thank you

 

[MilesAhead]

http://www.sevenforums.com/network-...ts-before-posting-your-networking-thread.html

Edit: since it's not about getting out on the net I can see skipping some detail. But it would be helpful to know how many machines running what OS each are in the network and the type of connections. Also I don't see anything about disabling the firewall.

And of course with Printer issues please post the make and model of Printer.

 

[Kari]

In addition to what Miles already told you, check the time on both computers. Windows Homegroup can have strange issues, parts working while others not, if the system time on all Homegroup computers is not in sync.

Last time I had a similar printer issue it was fixed simply by syncing the time on both Homegroup computers.

Kari

 

[chev65]

Hi,
I am not able to share a printer via Homegroup, where the printer is connected on the USB port of the computer that hosts the Homegroup.
the printer works fine on the computer it is connected to, indicating the driver is OK.
Another computer on the Homegroup can search the host computer, but it cannot access the printer due to error 0x0000052f.
I think that error is due to a corrupted file, whether it is a system file on the secondary Homegroup computer, I don't know.
I've tried several things:

• starting again from scratch, 1) disabling the anti-virus program 2) disabling the Homegroup 3) unconnecting the printer and reconnecting it 3) re-creating the homegroup 4) trying to add a printer to the secondary computer, and getting the message "error 0x0000052f"
• manually investigating the Registry Hkey_Local_Machine>Software>Microsoft>Windows>CurrentVersion>Run where I expected there to be a error 0x0000052f file but found nothing
• invested in a Registry cleaner "RegCurePro" which didn't change the problem

Can anyone suggest what I should do next?
Thank you

It's required that you install the printer drivers onto each machine that needs to use the printer.

USB printers are so XP days and unreliable at best, we use networked printers these days but installing the drivers onto each machine is still required and it should hopefully work for you.

 

[MilesAhead]

It's required that you install the printer drivers onto each machine that needs to use the printer.

That's how it worked for my USB printers when both my machines were XP. But when I bought a new USB printer with an in firmware Vista driver, and a Vista PC, it served the driver over the network. I had dual boot W7 on the XP machine but since there was no W7 driver for that printer the only way everything would work was to connect it to the Vista machine. Royal pain.

Edit: I tried every whichaway of installing printer drivers to the W7 machine. It would show up as the wrong model printer. Connected to the Vista PC, it was just share and use. No water added.

 

[Chaim613]

It still won't see the printer...why? - 0x0000052f!

Hi,
Thanks to everyone who responded, sorry about not reading the responses sooner.
The Homegroup host machine is running W-7 Pro, the secondary machine is running W-7 Home Premium.
The Printer is an HP Laser Jet 1320. I tried re-installing the driver (HP Laser Jet 1320 PCL 5 Universal Driver) and it seemed to do every right but when it came to finding the printer it again said Windows could not connect to the printer because of 0x0000052f.
I didn't turn off the firewall, because it was not recommended to be without one, but I checked which programs were allowed through the firewall, and File & Printer Sharing was allowed, as was Homegroup.
- Thanks

 

[Chaim613]

I also synched the time

Hi,
I synched the time by checking that both clocks were showing the time.
Thanks

 

[chev65]

Hi,
Thanks to everyone who responded, sorry about not reading the responses sooner.
The Homegroup host machine is running W-7 Pro, the secondary machine is running W-7 Home Premium.
The Printer is an HP Laser Jet 1320. I tried re-installing the driver (HP Laser Jet 1320 PCL 5 Universal Driver) and it seemed to do every right but when it came to finding the printer it again said Windows could not connect to the printer because of 0x0000052f.
I didn't turn off the firewall, because it was not recommended to be without one, but I checked which programs were allowed through the firewall, and File & Printer Sharing was allowed, as was Homegroup.
- Thanks

Make sure that the W7 Home Premium machine is joined to the Homegroup and also that the printer is shared from the W7 Pro machine.

It might also help if you add a user password "if you aren't already using one" to each machine in case of any permission issues because the error number "0x0000052f." relates to a log in problem.

There is also a Microsoft Community thread about this networking problem with the HP 1320 with links to drivers for both 32 and 64 bit plus some advice from others who are trying different solutions.
http://answers.microsoft.com/en-us/...7/885caf70-e315-4e1d-9017-78601bcfb09b?page=1

 

[MilesAhead]

I find with network issues it's best to turn off all impediments, including av,firewall, etc..

After you get it working then it's simple to turn them back on. I don't know how many times I looked at firewall settings that "should work." But the network would not work until I disabled all the blocking software.