win32_tcpipprinterport

Hi,

A student has a bunch of HP network printers that got installed using
default printer names. She wants to write a script that will correct them.
Other references indicate that we should be able to use the
win32_tcpipprinterport object to do this with a WMI script. However, some
question arrises as to whether this will work with HP tcp/ip addresses due
to the software used to configure the printers on the server. I'm convinced
it should be a scriptable fix even though they'r running windows 2000 rather
than server 2003.

In testing, we run into two problems:

1. the win32_tcpipprinterport object isn't showing up on some servers even
though they have tcp/ip ports employed.

2. on servers that do have the object showing up, it doesn't show TCP/IP
port properties.

Any suggestions or thought will be appreciated.

J B. Fields
--
J Burford Fields
Wyoming wisdom: Good judgment comes from experience, and a lotta that comes
from bad judgment.

Søren
Thu Dec 02 16:56:34 CST 2004

Just guessing as i have no HP printerports at hand...

Could the missing object on some servers be caused by using HP port drivers,
instead of Windows standard IP printer port drivers?

Regards

Søren Lassen

"JB Fields" <jbfields@msn.com> wrote in message
news:e$kCflL2EHA.3500@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> A student has a bunch of HP network printers that got installed using
> default printer names. She wants to write a script that will correct
> them.
> Other references indicate that we should be able to use the
> win32_tcpipprinterport object to do this with a WMI script. However, some
> question arrises as to whether this will work with HP tcp/ip addresses due
> to the software used to configure the printers on the server. I'm
> convinced
> it should be a scriptable fix even though they'r running windows 2000
> rather
> than server 2003.
>
> In testing, we run into two problems:
>
> 1. the win32_tcpipprinterport object isn't showing up on some servers
> even
> though they have tcp/ip ports employed.
>
> 2. on servers that do have the object showing up, it doesn't show TCP/IP
> port properties.
>
> Any suggestions or thought will be appreciated.
>
> J B. Fields
> --
> J Burford Fields
> Wyoming wisdom: Good judgment comes from experience, and a lotta that
> comes
> from bad judgment.
>
>
>

JB
Fri Dec 03 08:17:04 CST 2004

In the end, that may be a problem, but I'm trying to just get a regular
TCP/IP port configuration and even with prnadmin.dll it is not as straight
forward as the documentation.... well, the documentation isn't all that
clear either :)
--
J Burford Fields
Wyoming wisdom: Good judgment comes from experience, and a lotta that comes
from bad judgment."Søren Lassen" <TAKETHISAWAYslazzen@hotmail.com> wrote in
message news:%23rYmqIM2EHA.804@TK2MSFTNGP12.phx.gbl...
> Just guessing as i have no HP printerports at hand...
>
> Could the missing object on some servers be caused by using HP port
> drivers, instead of Windows standard IP printer port drivers?
>
> Regards
>
> Søren Lassen
>
> "JB Fields" <jbfields@msn.com> wrote in message
> news:e$kCflL2EHA.3500@TK2MSFTNGP09.phx.gbl...
>> Hi,
>>
>> A student has a bunch of HP network printers that got installed using
>> default printer names. She wants to write a script that will correct
>> them.
>> Other references indicate that we should be able to use the
>> win32_tcpipprinterport object to do this with a WMI script. However,
>> some
>> question arrises as to whether this will work with HP tcp/ip addresses
>> due
>> to the software used to configure the printers on the server. I'm
>> convinced
>> it should be a scriptable fix even though they'r running windows 2000
>> rather
>> than server 2003.
>>
>> In testing, we run into two problems:
>>
>> 1. the win32_tcpipprinterport object isn't showing up on some servers
>> even
>> though they have tcp/ip ports employed.
>>
>> 2. on servers that do have the object showing up, it doesn't show TCP/IP
>> port properties.
>>
>> Any suggestions or thought will be appreciated.
>>
>> J B. Fields
>> --
>> J Burford Fields
>> Wyoming wisdom: Good judgment comes from experience, and a lotta that
>> comes
>> from bad judgment.
>>
>>
>>
>
>