Non-hardware printer goes offline after reboot with no port

[JohnA]

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25 to
USB) that runs just fine. But when I try and add a printer connected to a
Windows XP system, every time I restart the spooler or reboot, the printer
goes offline and the port vanishes (although it's still in the registry just
fine). To get it back, I need to remove the printer and add it back.
Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC name,
the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port is
selected
4) An examination of the registry shows the port is present the same way as
before (I could find no difference). The port is defined and the printer
has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already exists"
error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.

 

[Char Jackson]

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25 to
USB) that runs just fine. But when I try and add a printer connected to a
Windows XP system, every time I restart the spooler or reboot, the printer
goes offline and the port vanishes (although it's still in the registry just
fine). To get it back, I need to remove the printer and add it back.
Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC name,
the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port is
selected
4) An examination of the registry shows the port is present the same way as
before (I could find no difference). The port is defined and the printer
has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already exists"
error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.

I have never tried to install a printer that way, which is not to say
that you're doing it wrong. I think it just means there are other
ways. I always just share the printer on the PC where it's connected,
then on the remote PC I browse the network, locate the shared printer,
right-click on it and select Install. Done, and it has always worked
for me.

 

[Seth]

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25
to USB) that runs just fine. But when I try and add a printer connected
to a Windows XP system, every time I restart the spooler or reboot, the
printer goes offline and the port vanishes (although it's still in the
registry just fine). To get it back, I need to remove the printer and add
it back. Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

But that's not a local port, that's a network printer. Local port would be
used for A) a physical port on your machine or B) a true print server that
you are setting up a local queue for.

 

[Thee Chicago Wolf [MVP]]

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25 to

USB) that runs just fine. But when I try and add a printer connected to a
Windows XP system, every time I restart the spooler or reboot, the printer
goes offline and the port vanishes (although it's still in the registry just
fine). To get it back, I need to remove the printer and add it back.
Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC name,
the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port is
selected
4) An examination of the registry shows the port is present the same way as
before (I could find no difference). The port is defined and the printer
has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already exists"
error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.

UNC path based printing via MS Networking / Printer Sharing can be
beyond frustrating. Is the XP machines on SP3 and fully patched up? It
sounds like it's breaking the previous connection you made to it.

Since you have Win 7 SP1 installed already, try grabbing the hotfix
from http://support.microsoft.com/kb/2457866 and see if it helps. If
not, grab all the below printing-related hotfixes for your Win 7
machines and give it a shot. If all those hotfixes don't solve your
issue, try updating the NIC driver on both the Win 7 box and the XP
PC. If it STILL doesn't fix it, it's the XP PC and I have one more
suggestion after that. Report back on the results.

http://support.microsoft.com/kb/981070
http://support.microsoft.com/kb/2462317
http://support.microsoft.com/kb/2484033
http://support.microsoft.com/kb/2495074
http://support.microsoft.com/kb/2509307
http://support.microsoft.com/kb/2511290
http://support.microsoft.com/kb/2526028

- Thee Chicago Wolf [MVP]

 

[SC Tom]

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25
to USB) that runs just fine. But when I try and add a printer connected
to a Windows XP system, every time I restart the spooler or reboot, the
printer goes offline and the port vanishes (although it's still in the
registry just fine). To get it back, I need to remove the printer and add
it back. Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC
name, the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port
is selected
4) An examination of the registry shows the port is present the same way
as before (I could find no difference). The port is defined and the
printer has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already
exists" error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.

I agree with Char's post. I used the method here
http://www.sevenforums.com/network-sharing/7527-networking-printer-attached-win-xp-pc-win-7-a.html
for an older printer that had no real Win7 drivers. It worked for about a
year before the printer itself finally died (old age, just wore out).

 

[JohnA]

Hi Char,

There is no other way for me with Windows 7 64 bit - the printer is an HP
DeskJet 990C - if I try and add it the intuitive way (choose network
printer, select it and connect), it tells me (after searching Windows
Update) that it can't find a driver. It then allows me to manually find a
driver. I tried to use the driver for the HP DeskJet 990C that is supplied
with Windows 7 by manually pointing the print installer to
Windows\System32\DriverStore\FileRepository\prnhp001.inf_amd64_neutral_081cf2b90ec9e6d5\prnhp001.inf
but it refused to use it. I went to the HP site and they don't have
downloadable drivers for the HP DeskJet 990c and tell you that it is built
in Windows 7. The only problem, it only works if I use the UNC method with
local port or attach my printer via USB cable to my Windows 7 system. So
using the UNC method was my last choice. :-(

So now everytime I reboot my system, I must manually add the port back in
and set it online... one would think that there has to be a better way...

John

"Char Jackson" wrote in message

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25 to
USB) that runs just fine. But when I try and add a printer connected to a
Windows XP system, every time I restart the spooler or reboot, the printer
goes offline and the port vanishes (although it's still in the registry
just
fine). To get it back, I need to remove the printer and add it back.
Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC name,
the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port is
selected
4) An examination of the registry shows the port is present the same way as
before (I could find no difference). The port is defined and the printer
has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already
exists"
error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.

I have never tried to install a printer that way, which is not to say
that you're doing it wrong. I think it just means there are other
ways. I always just share the printer on the PC where it's connected,
then on the remote PC I browse the network, locate the shared printer,
right-click on it and select Install. Done, and it has always worked
for me.

 

[JohnA]

A local port can be a virtual port (e.g. FILE:, NUL:, etc.) or a UNC
sharename - at least that was my understanding and it did let me do it

"Seth" wrote in message

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25
to USB) that runs just fine. But when I try and add a printer connected
to a Windows XP system, every time I restart the spooler or reboot, the
printer goes offline and the port vanishes (although it's still in the
registry just fine). To get it back, I need to remove the printer and add
it back. Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

But that's not a local port, that's a network printer. Local port would be
used for A) a physical port on your machine or B) a true print server that
you are setting up a local queue for.

 

[Thee Chicago Wolf [MVP]]

Hi Char,

There is no other way for me with Windows 7 64 bit - the printer is an HP
DeskJet 990C - if I try and add it the intuitive way (choose network
printer, select it and connect), it tells me (after searching Windows
Update) that it can't find a driver. It then allows me to manually find a
driver. I tried to use the driver for the HP DeskJet 990C that is supplied
with Windows 7 by manually pointing the print installer to
Windows\System32\DriverStore\FileRepository\prnhp001.inf_amd64_neutral_081cf2b90ec9e6d5\prnhp001.inf
but it refused to use it. I went to the HP site and they don't have
downloadable drivers for the HP DeskJet 990c and tell you that it is built
in Windows 7. The only problem, it only works if I use the UNC method with
local port or attach my printer via USB cable to my Windows 7 system. So
using the UNC method was my last choice. :-(

So now everytime I reboot my system, I must manually add the port back in
and set it online... one would think that there has to be a better way...

John

Use the HP Universal Print Driver.

- Thee Chicago Wolf [MVP]

 

[Seth]

A local port can be a virtual port (e.g. FILE:, NUL:, etc.) or a UNC
sharename - at least that was my understanding and it did let me do it

I know the various port differences, and because it let you do it that way
doesn't make it proper or reliable (as you've found out which is why you are
here).

Proper practice is... local port for when the local machine is going to
manage the queue, and choose Network when something else is managing the
queue (such as the XP machine the printer is actually installed on).

It's probably going offline and staying that way when the XP machine reboots
or even hiccups where it is handled differently when you choose Network
printer for the type.

 

[JohnA]

That's the method I'm using - but it doesn't survive a reboot or spooler
restart for some reason... I assume that yours did which means that putting
the UNC name as the local port is just fine.

"SC Tom" wrote in message

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25
to USB) that runs just fine. But when I try and add a printer connected
to a Windows XP system, every time I restart the spooler or reboot, the
printer goes offline and the port vanishes (although it's still in the
registry just fine). To get it back, I need to remove the printer and add
it back. Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC
name, the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port
is selected
4) An examination of the registry shows the port is present the same way
as before (I could find no difference). The port is defined and the
printer has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already
exists" error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.

I agree with Char's post. I used the method here
http://www.sevenforums.com/network-sharing/7527-networking-printer-attached-win-xp-pc-win-7-a.html
for an older printer that had no real Win7 drivers. It worked for about a
year before the printer itself finally died (old age, just wore out).

 

[JohnA]

Hi,

Thank you very much for your reply... see below...

John

"Thee Chicago Wolf [MVP]" wrote in message


UNC path based printing via MS Networking / Printer Sharing can be
beyond frustrating. Is the XP machines on SP3 and fully patched up? It
sounds like it's breaking the previous connection you made to it.

[John] Yes, it is SP3 and fully patched. The connection is fine until I
restart the spooler.

Since you have Win 7 SP1 installed already, try grabbing the hotfix
from http://support.microsoft.com/kb/2457866 and see if it helps. If
not, grab all the below printing-related hotfixes for your Win 7
machines and give it a shot. If all those hotfixes don't solve your
issue, try updating the NIC driver on both the Win 7 box and the XP
PC.

http://support.microsoft.com/kb/981070
http://support.microsoft.com/kb/2462317
http://support.microsoft.com/kb/2484033
http://support.microsoft.com/kb/2495074
http://support.microsoft.com/kb/2509307
http://support.microsoft.com/kb/2511290
http://support.microsoft.com/kb/2526028

[John] I really appreciate the time you spent assembling this list of
potential solutions. However, I'm leary of applying hotfixes unless they
describe the problem that I have. None of the ones you reference seem to do
that - they appear to be variations. For example,
http://support.microsoft.com/kb/2457866 says you get Event 602 which I am
not getting. The other hotfixes appear to be addressing different problems.
The NIC cards on both the XP and Windows 7 appear to be up to date...
suggestion after that. Report back on the results. <<

[John] I have another virtual port printer (Nuance PDF Converter 7) that
behaves the same way and has nothing to do with the XP machine. It really
sounds like the Windows 7 machine does not like something with these ports.
Other ports have no problem and I can't see any difference between them.
- Thee Chicago Wolf [MVP]

 

[JohnA]

Hi Seth,

If that was true (UNC names for localports are invalid), wouldn't more
people be having this problem? But as one poster here has pointed out, they
had no problem at all doing that. As I browse the web, it appears to me
that this is the standard way for Windows 7 to attach to shared printer on
XP...

BTW, I wasn't talking about the XP rebooting - I was referring to the
Windows 7 PC, the XP PC rebooting doesn't matter - I apologize for any
confusion...

John

"Seth" wrote in message

A local port can be a virtual port (e.g. FILE:, NUL:, etc.) or a UNC
sharename - at least that was my understanding and it did let me do it

I know the various port differences, and because it let you do it that way
doesn't make it proper or reliable (as you've found out which is why you are
here).

Proper practice is... local port for when the local machine is going to
manage the queue, and choose Network when something else is managing the
queue (such as the XP machine the printer is actually installed on).

It's probably going offline and staying that way when the XP machine reboots
or even hiccups where it is handled differently when you choose Network
printer for the type.

 

[JohnA]

Thank you for your suggestion - I downloaded and installed the driver -
however, that doesn't seem to work - unlike the "Add printer" method, the
Universal HP driver can't seem to detect my printer at all. If I attach to
the printer manually, with local port, etc. I have the same problem with the
port disappearing.

John

"Thee Chicago Wolf [MVP]" wrote in message

Hi Char,

There is no other way for me with Windows 7 64 bit - the printer is an HP
DeskJet 990C - if I try and add it the intuitive way (choose network
printer, select it and connect), it tells me (after searching Windows
Update) that it can't find a driver. It then allows me to manually find a
driver. I tried to use the driver for the HP DeskJet 990C that is supplied
with Windows 7 by manually pointing the print installer to
Windows\System32\DriverStore\FileRepository\prnhp001.inf_amd64_neutral_081cf2b90ec9e6d5\prnhp001.inf
but it refused to use it. I went to the HP site and they don't have
downloadable drivers for the HP DeskJet 990c and tell you that it is built
in Windows 7. The only problem, it only works if I use the UNC method with
local port or attach my printer via USB cable to my Windows 7 system. So
using the UNC method was my last choice. :-(

So now everytime I reboot my system, I must manually add the port back in
and set it online... one would think that there has to be a better way...

John

Use the HP Universal Print Driver.

- Thee Chicago Wolf [MVP]

 

[Seth]

Hi Seth,

If that was true (UNC names for localports are invalid), wouldn't more
people be having this problem? But as one poster here has pointed out,
they had no problem at all doing that. As I browse the web, it appears to
me that this is the standard way for Windows 7 to attach to shared printer
on XP...

BTW, I wasn't talking about the XP rebooting - I was referring to the
Windows 7 PC, the XP PC rebooting doesn't matter - I apologize for any
confusion...

Hey, you don't want to try my suggestion, suit yourself. But I can say this
is the method and methodology I've been using for years without issues.

Also, I didn't say it was invalid, just not proper. Big difference. One
way will never work, one way is troublesome.

 

[JohnA]

Hi Seth,

I didn't know you had a suggestion that I could use - you said not to use
the UNC name, but if you have an alternative that works, that would be
great. As I said, Network printer and the HP Universal Printer don't work
and are not alternatives that are viable.

-- John

"Seth" wrote in message

Hi Seth,

If that was true (UNC names for localports are invalid), wouldn't more
people be having this problem? But as one poster here has pointed out,
they had no problem at all doing that. As I browse the web, it appears to
me that this is the standard way for Windows 7 to attach to shared printer
on XP...

BTW, I wasn't talking about the XP rebooting - I was referring to the
Windows 7 PC, the XP PC rebooting doesn't matter - I apologize for any
confusion...

Hey, you don't want to try my suggestion, suit yourself. But I can say this
is the method and methodology I've been using for years without issues.

Also, I didn't say it was invalid, just not proper. Big difference. One
way will never work, one way is troublesome.

 

[Seth]

Hi Seth,

I didn't know you had a suggestion that I could use - you said not to use
the UNC name, but if you have an alternative that works, that would be
great. As I said, Network printer and the HP Universal Printer don't work
and are not alternatives that are viable.

I said don't set it up as a local port. That would mean when you get to the
page in the wizard where local port is one of the choices, choose the other
one. "Add a network, wireless or Bluetooth printer", then follow the wizard
that way. You will of course have to enter the UNC, but now you're doing it
as a network resource and not a local port.

 

[JohnA]

Hi Seth,

You write:

Unfortunately, as I thought I explained, this doesn't work. When I pick
network, wireless or Bluetooth, I then select the printer which shows up.
When I click on "next", it searches for a driver, looks at Windows Updates,
and does not find it. It was because that didn't work that I ended up with
the local port approach. If you know of a way around this, please let me
know.

Thanks, John

"Seth" wrote in message

Hi Seth,

I didn't know you had a suggestion that I could use - you said not to use
the UNC name, but if you have an alternative that works, that would be
great. As I said, Network printer and the HP Universal Printer don't work
and are not alternatives that are viable.

I said don't set it up as a local port. That would mean when you get to the
page in the wizard where local port is one of the choices, choose the other
one. "Add a network, wireless or Bluetooth printer", then follow the wizard
that way. You will of course have to enter the UNC, but now you're doing it
as a network resource and not a local port.

 

[JohnA]

Also, http://support.microsoft.com/kb/282842 seems to validate putting the
UNC name in the local port - see procedure for the Windows 2000 based
computer... It seems that Microsoft's definition of a network printer is a
printer directly connected to the Internet.

"Seth" wrote in message

Hi Seth,

I didn't know you had a suggestion that I could use - you said not to use
the UNC name, but if you have an alternative that works, that would be
great. As I said, Network printer and the HP Universal Printer don't work
and are not alternatives that are viable.

I said don't set it up as a local port. That would mean when you get to the
page in the wizard where local port is one of the choices, choose the other
one. "Add a network, wireless or Bluetooth printer", then follow the wizard
that way. You will of course have to enter the UNC, but now you're doing it
as a network resource and not a local port.

 

[JohnA]

Interesting - apparently, the spooler will try and write to the XP host on
startup and if it fails this causes problem.

"The Local Port work around when driver names do not work or when the
devmode structure for the 64bit version of the print driver will not work
with the 32bit OS sharing the device can fail due to security issues when
the server service write fails to the XP machine." Alan Morris, Windows
Printing Team

Source:
http://answers.microsoft.com/en-us/...7/d04e7461-e495-499d-80da-bdc04d5e3167?page=2

I verified that if I do the following:

copy con \\<prtsrv>\print$\w32x86\hewlett_packarddeskj4c9e\foo
test
Access is denied.
0 file(s) copied.
suggesting that the print servers directory is only readable.

I can perform a "dir \\<prtsrv>\print$\w32x86\hewlett_packarddeskj4c9e" with
no problem showing that it is readable

-- John

"Seth" wrote in message

Hi Seth,

I didn't know you had a suggestion that I could use - you said not to use
the UNC name, but if you have an alternative that works, that would be
great. As I said, Network printer and the HP Universal Printer don't work
and are not alternatives that are viable.

I said don't set it up as a local port. That would mean when you get to the
page in the wizard where local port is one of the choices, choose the other
one. "Add a network, wireless or Bluetooth printer", then follow the wizard
that way. You will of course have to enter the UNC, but now you're doing it
as a network resource and not a local port.

 

[JohnA]

Update: Without changing anything on the Windows 7 box, I moved the Windows
XP system with the printer to another hardware platform performing an
identical installation (using PC Move). Printer setup was the same with the
HP DeskJet on LPT1: . Now Windows 7 could connect properly as a network
printer and the problem is solved!

However, the problem remains on Windows 7 that any local printer port that
is added (whether through the print manager, adding a local port, or program
installation), even FILE: or NUL: disappear on reboot or spooler restart
although they are there in the registry. I wonder if someone who has a
Windows 7 64 bit platform could try adding a local port (e.g. Print Server
Properties/Ports), reboot and see if it's still there.

"JohnA" wrote in message

I'm running Windows 7 Ultimate SP1 64 bit - I have a local printer (DB25 to
USB) that runs just fine. But when I try and add a printer connected to a
Windows XP system, every time I restart the spooler or reboot, the printer
goes offline and the port vanishes (although it's still in the registry just
fine). To get it back, I need to remove the printer and add it back.
Here's what I do:

1) Click "Add printer"
2) Pick local port
3) Pick new
4) Type \\prtsrv\prtname for the name
5) Pick the appropriate device driver

Everything looks fine, the printer is attached to a port with the UNC name,
the printer is in the "Ready" state and I can print just fine.

However, when I restart the print spooler or reboot, the following happens

1) The printer is now offline
2) Print jobs just stay in the queue (not surprising)
3) An examinations of the port tab shows the port is missing and no port is
selected
4) An examination of the registry shows the port is present the same way as
before (I could find no difference). The port is defined and the printer
has the port in its definition.
5) If I try and add the port back in manually, I get a "Port already exists"
error, not surprisingly.

Rebooting multiple times has no affect. The only way I know of to get the
printer back is to delete it and add it back in.

I would be so grateful for any tips in addressing this problem - this is
very frustrating.