TCP/IP ports missing after reboot

[Guest]

Of the 17 DC's in my Windows 2000 domain, there are a few that when rebooted
will lose some of the TCP/IP printing ports setup for network printing.
Variety of printer models - does not seem to matter - installed as Standard
TCP/IP ports and will work fine without problems until the server is
rebooted. DC's are Windows 2000 w/SP4 with updates current.

Anyone had encountered this? If so, any solutions for how to fix?

 

[Alan Morris\(MSFT\)]

I have seen this occur if one of the registry entries is corrupted. You add
ports after the reboot and they work until the spooler shuts down and
reinitializes the port list from the registry.

The port information is stored in
HKLM\System\CurrentControlSet\Control\Print\Monitor\Standard TCP/IP
Port\Ports\

When some of the ports remain after the reboot look for the last port in the
list in the registry. The next port is most likely the issue as the spooler
reads the ports list during initialization and stops when it thinks it has
come to the last in the list due to corruption.

Look at the information in the previous ports. I just remove the offending
key rather than attempt to make the correction in regedit.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Alan, thanks for the info. I looked in the registry and did notice that
there were old ports listed. I have removed those ports no longer in use and
will see what happens. Thanks for your assistance.

I have seen this occur if one of the registry entries is corrupted. You add
ports after the reboot and they work until the spooler shuts down and
reinitializes the port list from the registry.

The port information is stored in
HKLM\System\CurrentControlSet\Control\Print\Monitor\Standard TCP/IP
Port\Ports\

When some of the ports remain after the reboot look for the last port in the
list in the registry. The next port is most likely the issue as the spooler
reads the ports list during initialization and stops when it thinks it has
come to the last in the list due to corruption.

Look at the information in the previous ports. I just remove the offending
key rather than attempt to make the correction in regedit.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

Of the 17 DC's in my Windows 2000 domain, there are a few that when rebooted
will lose some of the TCP/IP printing ports setup for network printing.
Variety of printer models - does not seem to matter - installed as Standard
TCP/IP ports and will work fine without problems until the server is
rebooted. DC's are Windows 2000 w/SP4 with updates current.

Anyone had encountered this? If so, any solutions for how to fix?