Re: HP JetAdmin JetDirect

On May 14, 2:38 pm, Parvardigar <parvardi...@xxxxxxxxx> wrote:
Hello

If I need to post to another group, let me know.

I bought a new printer. During the HP Printer software install, the
install failed at 2%. I needed HP support on the P1205x network
printer. I phoned into HP. We did a cold reset. We couldn’t do a
‘route add 169.254.76.255 192.168.253.45.’  HP couldn’t assist. I said
is it the subnet mask? The cold reset shows 255.255.0.0 and our
network segment it is 255.255.255.0. Hp indicated that "route add'
isn’t effected by a subnet mask.

I got to thinking why not use the JetAdmin utility already on the
server? We are simply replacing the older HP2100. And that software
utility is on the server.

The JetAdmin interface was able to discover/ detect the HP2015
printer. That is good news.

Under Device Management/ Management Settings/ Discovery/ Discovery
Result -there are five hardware addresses listed. The HP2015 hardware
address is listed: 0017087F460D –along with the other printers on this
segment.

If JetAdmin can detect the hardware I maybe able to configure the
printer, but I don’t know how.
I did click on "Specified Addresses"  The "Add Device to Host File"
and several other information tabs were available. On Hp's site I
found the JetAdmin download manual. It was –ambiguous.

The HP tech person indicated that to install the HP 2015x software /
drivers I need to add and configure the HP2015 Printer (default) ip
169.254.17.255 mask 255.255.0.0 gateway 169.254.17.255 to our network
segment server ip 192.168.253.45. The final goal is to create a static
ip for the HP 2015 printer as 192.168.253.9.

Additional info:
The HP 2015 hostname: NP17F460D.
I did attempt a few Telnet instructions. Telnet unable to communicate
with the HP 2015 device.
On this segment the company isn’t using DHCP.

I appreciate any advice on how to use the JetAdmin utility.
Thanks
John Marshall

I'll feedback to myself. It's all who you talk to in HP Tech. This one
fellow knew what to do. I was instructed to download the HP2015 PnP
drivers. That fixed the install. To get it on the network because the
printer default is 169.x.x.x. mask 255.255.00 I needed to use the
Embedded Web Interface. This EWI talks to the printer. But you need to
be on the same mask for this to work. I changed a workstation to
169.x.x.x. mask 255.255.0.0. I type into the browser 169.x.x.x. and
there emerged the EWI. I changed the IP conf to Static, 192.168.x.x.
mask 255.255.255.0. I went to the server, added the printer, and now
its on the Network.
.

Relevant Pages

  • Re: HP JETADMIN
    ... Thank you for sharing your success with JETADMIN. ... when a simple IPAddress install to the server meets most Small Business ... >all printers from a single place. ... Share the printers and install them for users in their Windows ...
    (microsoft.public.windows.server.sbs)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)