"Standard TCP/IP port" option missing when adding printer
dclist
"Standard TCP/IP port" option in the drop-down list when adding
printer via local port. I have no idea why this is missing on this
machine. Is it a driver? How can I restore it?
SC Tom
"dclist" <dcl...@gmail.com> wrote in message
news:6a59691a-5012-400a...@o15g2000vbb.googlegroups.com...
Try here first:
How to ask a question http://support.microsoft.com/kb/555375
Check your BIOS settings to see what it's set to. Without more info, I
can't go much farther than that.
--
SC Tom
dclist
What? In what way is my question deficient or unclear? What does this
have to do with the BIOS?
Shenan Stanley
> I want to add a TCP/IP printer but I am seem to be missing the
> "Standard TCP/IP port" option in the drop-down list when adding
> printer via local port. I have no idea why this is missing on this
> machine. Is it a driver? How can I restore it?
SC Tom wrote:
> Try here first:
> How to ask a question http://support.microsoft.com/kb/555375
>
> Check your BIOS settings to see what it's set to. Without more
> info, I can't go much farther than that.
dclist wrote:
> What? In what way is my question deficient or unclear? What does
> this have to do with the BIOS?
- Windows XP ______ Edition with Service Pack _, __-bit?
- Stand-alone PC or a member of some domain?
- Logging in with a local administrative account when attempting to do this?
- What printer(s), if any, are currently installed ont he machine and how
are these printer(s) connected to the PC?
- What antivirus software do you use and is it up to date? (Suggest: Avira
AntiVir - freeware.)
- What antispyware/antimalware software do/have you used? Have you used it
lately? (Suggest: MalwareBytes and SuperAntiSpyware - freeware.)
- Did this ever work on this machine to your knowledge?
- If so - what changes have occurred between it working and it now not
working?
- Has so much time passed that a System Restore is out of the question?
- What type of and frequency of a backup regime do you follow?
- What do your Internet searches turn up and/or what have you tried to do in
order to remedy your situation on your own?
( Suggest: http://tinyurl.com/25h54jk which could lead you to:
http://groups.google.com/group/microsoft.public.win2000.printing/msg/d2d3a8ee883e1fd0 )
Come back - let everyone know if any of this helped you out (and be sure to
answer all the questions - as those are things that you could have given
initially that would have sped up your likelyhood in receiving directed
answers toward your issue.)
Why come back? It is here indefinitely, so if you don't come back and let
everyone know if something helped, they may not be as apt to try what you
know works.
See what I mean?
http://groups.google.com/group/microsoft.public.windowsxp.help_and_support/browse_frm/thread/aaf1798ef985876e/
Good Luck!
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
Jose
Look in the registry on a working machine and the afflicted machine.
Before making any changes to your registry, back it up with this
popular free tool:
http://www.larshederer.homepage.t-online.de/erunt/
If you have a working XP machine you can look at it and export this
registry key or create one just like it on your afflicted machine:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\
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 values data in decimal)
LprAckTimeout value data= 180
StatusUpdateEnabled value data= 1
StatusUpdateInterval value data= 10
Stop and start the Print Spooler Service
Here is what mine looks like (watch the line wraps):
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]
"StatusUpdateInterval"=dword:0000000a
"StatusUpdateEnabled"=dword:00000001
"LprAckTimeout"=dword:000000b4
dclist
Thanks but changing the registry to match (I only had to add the lpr
timeout) does not help. I will see if I can figure out if tcpmon.dll
is corrupt.
dclist
information you are asking for is extraneous.
Nonetheless, see my responses inline.
On May 23, 6:42 pm, "Shenan Stanley" <newshel...@gmail.com> wrote:
> dclist wrote:
> > I want to add a TCP/IP printer but I am seem to be missing the
> > "Standard TCP/IP port" option in the drop-down list when adding
> > printer via local port. I have no idea why this is missing on this
> > machine. Is it a driver? How can I restore it?
> SC Tom wrote:
> > Try here first:
> > How to ask a question http://support.microsoft.com/kb/555375
>
> > Check your BIOS settings to see what it's set to. Without more
> > info, I can't go much farther than that.
> dclist wrote:
> > What? In what way is my question deficient or unclear? What does
> > this have to do with the BIOS?
>
> - Windows XP ______ Edition with Service Pack _, __-bit?
Home edition with SP3, 32-bit
> - Stand-alone PC or a member of some domain?
Stand alone
> - Logging in with a local administrative account when attempting to do this?
Yes
> - What printer(s), if any, are currently installed ont he machine and how
> are these printer(s) connected to the PC?
One other inkjet connected via USB
> - What antivirus software do you use and is it up to date? (Suggest: Avira
> AntiVir - freeware.)
Avast
> - What antispyware/antimalware software do/have you used? Have you used it
> lately? (Suggest: MalwareBytes and SuperAntiSpyware - freeware.)
None
> - Did this ever work on this machine to your knowledge?
> - If so - what changes have occurred between it working and it now not
> working?
> - Has so much time passed that a System Restore is out of the question?
I have not tried it before on this machine
> - What type of and frequency of a backup regime do you follow?
Minimal manual backups of documents.
> - What do your Internet searches turn up and/or what have you tried to do in
> order to remedy your situation on your own?
I did do google searches with terms like "Standard TCP/IP port"
microsoft windows xp adding; but I did not see anything relevant.
"missing" was a keyword that would have helped as you pointed out but
that is only obvious in retrospect.
> ( Suggest:http://tinyurl.com/25h54jkwhich could lead you to:http://groups.google.com/group/microsoft.public.win2000.printing/msg/...)
Thanks, that last link is somewhat helpful.
> Come back - let everyone know if any of this helped you out (and be sure to
> answer all the questions - as those are things that you could have given
> initially that would have sped up your likelyhood in receiving directed
> answers toward your issue.)
>
> Why come back? It is here indefinitely, so if you don't come back and let
> everyone know if something helped, they may not be as apt to try what you
> know works.
>
> See what I mean?http://groups.google.com/group/microsoft.public.windowsxp.help_and_su...
>
> Good Luck!
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Wayhttp://www.catb.org/~esr/faqs/smart-questions.html
As per my response to Jose verifying the registry entries did nothing.
I will try to verify if those dlls are corrupt.
Jose
Well, poop.
Here are the c:\windows\system32 files that you need to verify:
tcpmib.dll
tcpmon.dll
tcpmonui.dll
tcpmon.ini
The DLLS are Windows File Protected files, so they should not be
missing - if they are missing something else may be wrong.
If you are suspicious of the DLLs, stop the Print Spooler and delete
the 3 DLL files. WFP should quickly and silently replace them with
good copies (in a few seconds). If that does not happen you have
another problem.
You can copy the tcpmon.ini from a working system - it is not a WFP
protected file.
If you just add the files or make the registry change and don't
restart the Print Spooler (or reboot) you will not see any difference,
so be sure to restart the Print Spooler.
dclist
I replaced the aforementioned files using the DLL cache and it seems
to be working correctly now. Thanks!
Jose
Duly noted.