cancel
Showing results for 
Search instead for 
Did you mean: 
  • ×
    Information
    Fix Windows 10 Update Issues

    Resolve Windows 10 or update issues on HP computer or printer– Click Here

  • post a message
  • ×
    Information
    Fix Windows 10 Update Issues

    Resolve Windows 10 or update issues on HP computer or printer– Click Here

  • post a message
This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
Highlighted
Level 1
2 1 1 1
Message 1 of 4
2,345
Flag Post

Solved!

Web JetAdmin does not discover my printers

HP Recommended
Color LaserJet M553
Other

Hi everyone,

I just installed HP Web JetAdmin on my Windows 2012R2 Server in our network. (Version 10.4_SR1 Build 10.4.99821)

Now I try to discover printers but Web JetAdmin does not find any printers at all!

Message is always: Device not found!

I tried with IP, Hostname etc. All no success. I reinstalled Web JetAdmin, no success.

Local Firewall on server is disabled. The printer is in a different subnet and there are a few firewalls between.

But all necessary ports are open and I see a connection to the printer over port 161.

Do I need to change something on my printer HP Color LaserJet M553? Firmware Version 3.5 (2305076_518484)

Printer is setup for SNMPv1/v2 and password is set.

I set the same passwort in the settings on the Web Jetadmin, but still no success. As well when I make the discovery over with credentials and set the SNMP Password, still no success!

 

I am at the end of what else I could try!

Does anyone has an idea?

Update Firmware on Printer?

 

Any help would be appreciated

Thanks

Andre

 

0 Kudos
3 REPLIES 3
Highlighted
Level 1
5 3 1 0
Message 2 of 4
Flag Post
HP Recommended

Hi Andre,

 

I had the same issue at first and then rechecked the firewall. One of them didn't have the rule set up properly. I would check that first.

 

Are you using IP4 or IP6?

 

I added our subnets starting with XXX.XXX.XXX.1 to XXX.XXX.XXX.254 and ran discovery. It worked perfectly. 

 

Good luck! 

0 Kudos
Highlighted
Author
Level 1
2 1 1 1
Message 3 of 4
Flag Post
HP Recommended

Hi all,

Not sure why it took more than three months till my post finally got live.

In the meantime I was able to solve the issue by my self.

 

It was one Firewall (which was not in our monitoring) which blocked the access to the printers. After we opend as well the ports there, all communication was working just fine.

 

Have all a nice day

Andre

Highlighted
Level 1
5 3 1 0
Message 4 of 4
Flag Post
HP Recommended

Congratulations! Great job! 

0 Kudos
This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation