Google 網路論壇不再支援新的 Usenet 貼文或訂閱項目,但過往內容仍可供查看。

Cannot create Standard TCP/IP port (2003)

瀏覽次數:1,048 次
跳到第一則未讀訊息

Canuck geoff

未讀,
2004年10月26日 上午10:47:032004/10/26
收件者:
Hi all:

Sorry couldn't find a 2003 print queue.

We had a problem in which our spooler got corrupted. Eventually we used
cleansp from the 2003 resource kit to fix the corruption problem which it
did. The server was converted out of being a print server and when we
reconfigured it for that we are able to add local printers.

Unfortunately the Standard TCP/IP port selection is gone, and that is the
port type we need. If i try to add a new port type the machine wants me to
browse to set up files. I have had no luck in finding out where those files
are.

Does anyone have an idea where i can find the files to reinstall Standard
TCP/IP port as an option

gt

Felix Maxa [MSFT]

未讀,
2004年10月26日 下午2:41:132004/10/26
收件者:
The files should be still there. Can you please check?
dir %windir%\system32\tcpmon*
dir %windir%\system32\tcpmib*

You should see the following files: tcpmon.dll tcpmon.ini tcpmonui.dll
tcpmib.dll. Let me know if they're not there. If they are, please copy the
lines below to a file with the extension *reg. (name doesn't matter). launch
it and it will re-add the monitor entries to the registry. "net stop
spooler" then "net start spooler" then you should be able to add standard
tcp/ip ports again.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard
TCP/IP Port]
"Driver"="tcpmon.dll"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard
TCP/IP Port\Ports]
"LprAckTimeout"=dword:000000b4
"StatusUpdateInterval"=dword:0000000a
"StatusUpdateEnabled"=dword:00000001


--
Felix Maxa
Microsoft Printing, Imaging and Fax Team

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Canuck geoff" <Canuc...@discussions.microsoft.com> wrote in message
news:B793ED7C-03FD-4817...@microsoft.com...

Canuck geoff

未讀,
2004年10月27日 上午9:49:162004/10/27
收件者:
Hi Felix. This is very helpful but hasn't taken me all the way. I am
working on a test box that I intentionally clobbered with the same problem as
i am remote from the site and only see it about once a week.

All the files existed as you said. I created the .reg file, backed up the
system state and ran the reg file. Despite being told the keys were added,
when i look in the registry they are not there. I have a feeling i'm just
running into 2003 .dll rollback protection, so i'm off looking at that.

gt

Alan Morris(MSFT)

未讀,
2004年10月27日 下午3:17:472004/10/27
收件者:
This worked for Tony the Tiger

> > the three files you need still exist in system32 ( tcpmon.dll,
tcpmib.dll,
> > and tcpmonui.dll ) you can edit your registry entry and add the monitor
back
> > (cleanspl basically just deletes the reg entries ).
> >
> > If you have any Win2k or greater system handy you can export the
Standard
> > TCP/IP Port key and import to the other machine. Even if you do not
export
> > this key if you can look at this key for guidance when adding back the
entry
> > it is helpful.
> > stop and start spooler
> >
> >
> > if not, locate
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitor\
> >
> > Add key
> > Standard TCP/IP Port
> > Add String Value; value name=Driver; value data=tcpmon.dll
> >
> > under Standard TCP/IP Port
> > Add Key
> > Ports
> > Add three Dwords in Ports (I am listing the value data in
decimal)
> > LprAckTimeout value data= 180
> > StatusUpdateEnabled value data= 1
> > StatusUpdateInterval value data= 10
> >
> > stop and start spooler
> >
> > --
> > 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.
> >

> > "Tony the Tiger" <rob_1...@yahoo.co.uk> wrote in message
> > news:7f1d5f65.04090...@posting.google.com...
> > > I've had a problem with the print spooler on a windows 2003 server.
> > > I used the cleanspl.exe utility to clear everthing out and it worked,
> > > except I cleared out the tcp/ip standard printer port also (careless),
> > > now when I go in to create a new standard tcp/ip printer port it is
> > > greyed out. Does anyone know how to undo the damage done by the
> > > cleanspl.exe utility. How to you actually re-install all components
> > > accociated with tcp/ip printing. If anyone knows a solution to this I
> > > will be impressed ?
> > >
> > > Any suggestions much appreciated.
>
>
>
> Excellent all is working thanks very much Alan.


--
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.

"Canuck geoff" <Canuc...@discussions.microsoft.com> wrote in message
news:F7AB23A5-F4A0-4CFE...@microsoft.com...

Canuck geoff

未讀,
2004年10月28日 上午10:17:222004/10/28
收件者:
Thanks Alan. Last night I figured out what was wrong with the code Felix had
sent me. It wrapped in my browser and regedit did not like the carriage
returrns in the key path. Once i realized that i was able to import and
voila ports available. Now on to the production system.

Your idea about stealling from another box is also a good one.

Thanks to both you and Felix

Koehler@discussions.microsoft.com B Koehler

未讀,
2005年9月29日 下午3:21:022005/9/29
收件者:
Looks like this is a very old post but I have the same problem. When I edit
the register and make the addtions, the spooler fails again. Does anyone
else have a suggestion for me?

Brian

Alan Morris

未讀,
2005年9月30日 下午3:51:162005/9/30
收件者:
are the tcpmon files still in \windows\system32? Also verify that there are
no snmp or winsock files sitting in \windows that are duplicates of the MS
files in \windows\system32.

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

"B Koehler" <B Koe...@discussions.microsoft.com> wrote in message
news:6BD39270-8420-407B...@microsoft.com...

0 則新訊息