HP MFP Digital Sending Software 5.0 Manuel d'utilisateur télécharger pdf (Page 4)

If a bidi test fails there will be a message presented to the user on the DSS server display, as well as an

error entered into the DSS log which can be viewed on the log tab of the DSS service in the

Configuration Utility.

Pre-FutureSmart Devices

Every pre-FutureSmart had an automatic bidi test done when it is added to DSS. This has always been

the case with DSS 5 but the reporting was poor. If the test fails now an error is entered into the DSS log

which can be viewed on the log tab of the DSS service in the Configuration Utility.

Possible Causes of Bidi Problems and Debugging Tips

There are two primary known causes for bidi problems:

- Blocked TCP ports in the communication channel

- Errors on the device validating the DSS certificate

Blocked TCP Ports:

The most common cause of communication problems are blocked ports somewhere in the

infrastructure. This is most common with FS devices since port 7627 is a well-known port for web

services communication. It is also possible for port 1783 to be blocked, but since this is not a widely

used port it is less common.

It is very common in today’s security conscious world that IT administrators block ports by default and

only open what they need. When opening these ports for DSS use the administrator must know that

they have to be opened bi-directionally and not just out from the DSS server. The most common

problem occurs with port 7627 open from the DSS server out, but closed from the outside world into the

DSS server.

The ports can be blocked in many places in the infrastructure. Many times there will be a firewall on the

DSS server itself which will block the ports, but port blocking can also occur on other network devices

such as routers and switches.

1 2 3 4 5

Pas de commentaire

HP MFP Digital Sending Software 5.0 Manuel d'utilisateur Page 4