I have multiple computers on my home network. Recently one of my computers suddenly "forgot" how to connect to my network printer after the system that the printer was installed on was removed and printer connected (and shared) to another PC.
Computer A - older E6600 PC that is currently in pieces due to memory issues, originally had printer installed to it and shared on the network for 2+ years.
Computer B - newer Core i5 built within the past week that did have the printer directly installed and shared, for testing I swapped it to Computer C.
Computer C - home office work system (Core i3) that currently has the printer installed and shared.
Computer D - wifes PC, the main one having the problems connecting.
Computer E - barely used work related with Win8
All computers are Windows 7 ("C" is Windows 7 Pro, rest are Home Prem), and there is one Windows 8 system on the same home network. Router is using dd-wrt and has not had any changes made in 2+ years to cause this although I did restart the router just to make sure that wasn't causing any problems. All active computers except D connect to the printer and are able to print just fine.
D is having the issues. As soon as A was taken off the network, suddenly the print spool service on D started crashing and automatically restarting. I removed any trace of the old connections to A including the shared printer. I was able to get the print spool service fixed, but it still refuses to connect. On D, when I try to connect to the shared printer now, either directly via windows Explorer or via "Add a printer > Network printer", it always come back with an error code and unable to connect. The 2 most recent have been 0x000a and 0x7363. I can use folder explorer to browse the network shares on all PCs from all other PCs, including folders and files from D to the others, it is just something printer related that it is bugging out about.
I already ran cmd as admin and ran SFC /scannow and it did repair a bunch of corrupt files in the spool folder, but I am still getting the same error.
I am a long time tech but this one has me stumped.
Computer A - older E6600 PC that is currently in pieces due to memory issues, originally had printer installed to it and shared on the network for 2+ years.
Computer B - newer Core i5 built within the past week that did have the printer directly installed and shared, for testing I swapped it to Computer C.
Computer C - home office work system (Core i3) that currently has the printer installed and shared.
Computer D - wifes PC, the main one having the problems connecting.
Computer E - barely used work related with Win8
All computers are Windows 7 ("C" is Windows 7 Pro, rest are Home Prem), and there is one Windows 8 system on the same home network. Router is using dd-wrt and has not had any changes made in 2+ years to cause this although I did restart the router just to make sure that wasn't causing any problems. All active computers except D connect to the printer and are able to print just fine.
D is having the issues. As soon as A was taken off the network, suddenly the print spool service on D started crashing and automatically restarting. I removed any trace of the old connections to A including the shared printer. I was able to get the print spool service fixed, but it still refuses to connect. On D, when I try to connect to the shared printer now, either directly via windows Explorer or via "Add a printer > Network printer", it always come back with an error code and unable to connect. The 2 most recent have been 0x000a and 0x7363. I can use folder explorer to browse the network shares on all PCs from all other PCs, including folders and files from D to the others, it is just something printer related that it is bugging out about.
I already ran cmd as admin and ran SFC /scannow and it did repair a bunch of corrupt files in the spool folder, but I am still getting the same error.
I am a long time tech but this one has me stumped.
Facebook
Twitter
Instagram