Network connection troubleshooting
If the program cannot communicate with other DICOM nodes or it cannot transfer files from other
DICOM nodes, please check the following checklist:
- Ensure that the port of the program is not used by any other program.
- Ensure that the port of the program is not blocked from a firewall or an antivirus.
When the program starts it asks for to be added in firewall exception list. If you
answered no you must add it manually.
If the two nodes (server and client) belong to different subnetworks,
ensure that the port of the program is forwarded by the router.
If the program can "ECHO" the other node (client/server) but it cannot transfer files: Both machines (server and client)
must know each other. You must insert the AE Title, IP address and port of the application into "Known DICOM Nodes" list
of the other node (client/server). Without this information the client/server does not know where to send the files.
The IP Address that the program displays is the IP Address of the system, it is indicated by OS and the program cannot change it.
If the system has many network interfaces (physical or virtual network cards), it is possible the program to display a
wrong IP address, although it opens its port in all the available network interfaces and not only in the indicated IP address.
In cases like that, you can use the netstat utility to check if the port of the program is opened and at which IP address.
Use the menu command:
C:\>netstat -ano -p tcp |find "11122"
to check if the port 11122 of the program is opened and at which IP Address. The last number that the program prints is the PID of the
application that has opened the port. You can use the menu command:
C:\>tasklist |find "16832"
to find which is this application.