twenty seconds timeout in UPD driver because of port 3910

[vogt1]

Hello,

I have a windows print server which serves the same UPD driver to all HP printers.

The older cm6030f are printing fast, the newer e87640 have a timeout of twenty seconds,

before the printjob is send to the print server.

The Timeout:

If I click in notepad,word or in acrobad on "print" the GUI hangs. Word is writing "Word not responding"

and writing "Word is preparing a background print job". After ~20 seconds the job is send.

The Analysis:

I have analysed it with procman.exe. The trace shows that the UPD driver on the client is

connectings "e87640.printers.mynet.de" on port 3910.

This blocks for 20 seconds, after 20 second procman "continues" with logging.

The trace for the cm6030 does not show this TCP connect.

The network

The printer is in its own subnet and cannot be reached directly.

Any attempt to connect to the printer is silently dropped by the firewall, this explains the timeout.

The Question:

How can I disable the TCP connection to  e87640.printers.mynet.de:3910 in the printer driver?

Most likely it must be configured on the printer, because the cm6030f does not show the

behaviour with the same UPD driver and Print server as the e87640.

Edit: fixed wrong ports and typos

[vogt1]

The printer driver should not try to contact the printer, or at least this should be configurable.

It's port 3910, screenshot of procmon:

According to:

https://support.hp.com/vn-en/document/c05996543

3910, 3911 TCP:

"WS Discovery: HP Web Jetadmin uses this port to retrieve details about the device Web Services during a discovery. HP Web Jetadmin uses these details to establish the WS communication paths that it needs to manage devices.

HP Web Jetadmin uses port 3910 to retrieve print requests and uses port 3911 to retrieve the printer status."

[vogt1]

I have now installed a host in the printer network, which prints over the printserver, thus the printer is accessible from the subnet. The result ist:

- TCP lookup still happens

- it only takes ~ 1 sec

[vogt1]

I have two printservers with different  HP UPD Driver Versions:

- wps1 : 61.196.1.22169

- wps2:  61.225.1.23989

- If a client prints over wps1, there is no TCP connection

- If a client prints over wps2, there is  a TCP connection

Thus the TCP connection (direct connection to the printer) was added between :

- 61.196.1.22169 ... 61.225.1.23989

[vogt1]

The solution to the problem is to disable first Web Service Print on the printer and then

add the Printer on the Printserver.

If Autodetect is used and WS Print is enabled, Windows will somehow detect port 3910, because its lower than 9100

and somehow stores this information.

The Windows "port dialog" does not show this, its shows "lpr printing port 9100", but as said, somehow the UPD Driver

now knows that WS Print was enabled during port creation and uses this later and the timeout occurs.

Only disabling the WS Print feature, after the port was added, does not work too, the printqueue must be added

after WS Print is disabled.