Question regarding connecting Fuji and PacsOne

[nikj_dk]

Am I correct, when I assume that to connect modalities, I need AE Title, ip and portnumber.

If these parameters are correct, and there still is a problem, I will have to look elsewhere, ie. networking?

And modalities will have to have a list of other modalities which they need to communicate with?

Regards,
nikj_dk

[pacsone]

Yes, for two Dicom AEs to communicate, you need to configure the AE Title, IP address/hostname, and port number on both AE for the other AE, these are the equivalents of person name, address and telephone number in the human world.

If there's a problem after configuring the Fuji AE in the Application Entity page of PacsOne (and vice versa), you can click on the Dicom Ping link displayed on the row for the Fuji AE. This will send a Dicom C-ECHO command to the Fuji AE, and check if you get a successful echo back.

If the problem is with the other direction, i.e., Fuji to PacsOne, you can have the Fuji AE run a Dicom ping to PacsOne, then check the PacsOne Server logs to see if PacsOne has actually received the Dicom ping from Fuji. If not, you should check the IP address/port number configured for PacsOne on the Fuji AE, also check if there's any firewall blocking inbound packets to the TCP port number configured for PacsOne.

Am I correct, when I assume that to connect modalities, I need AE Title, ip and portnumber.

If these parameters are correct, and there still is a problem, I will have to look elsewhere, ie. networking?

And modalities will have to have a list of other modalities which they need to communicate with?

Regards,
nikj_dk

[nikj_dk]

Ping from PacsOne gives this, it´s in danish:

fsockopen() failed: Et forbindelsesforsøg mislykkedes, fordi den, der tilsluttede, ikke svarede korrekt efter en periode, eller forbindelsen mislykkedes, fordi den tilsluttede vært ikke svarede. (10060)

The Fuji application can ping and communicate with PacsOne.

The Fuji pc was set up by other technician, and that pc is not in the same Workgroup/Domain as computersystem.

I will change that, to see if it make a difference.

Regards,
nikj

[pacsone]

fsockopen() failed: Et forbindelsesforsøg mislykkedes, fordi den, der tilsluttede, ikke svarede korrekt efter en periode, eller forbindelsen mislykkedes, fordi den tilsluttede vært ikke svarede. (10060)

The 10060 Winsock error code means that PacsOne has timed out when trying to establish the connection to the TCP port/IP address configured for the Fuji AE. So you should make sure the IP address and TCP port number are correct.

You can also use the Telnet command to check the IP address/port number of the Fuji AE from a command shell:

Code: Select all

C:\>telnet $ipAddr $port

where $ipAdd is the IP address configured for the Fuji AE, and $port is the TCP port number configured for that AE.

If Telnet also times out when trying to establish connection to the configured IP address/port number, chances are either the IP address/port number is invalid, or there's no application accepting connection there, or there's a firewall blocking inbound packets to that IP addr/port number.

[nikj_dk]

There is a sligth problem, the PacsOne server does not connect with telnet ip portnumber from another computer on same network.

When I run netstat -o, I cannot see the PacsOne port number.

I have restarted the pacsone service, but that did not help.

Any suggestions?

Regards,
nikj_dk

[nikj_dk]

When AE is configured, this option is available:

Enter Preferred Transfer Syntax When PacsOne Server Send Images to This AE.

If this parameter is wrong, what happens?

Is this about conformance?

Regards,
nikj_dk

[pacsone]

There is a sligth problem, the PacsOne server does not connect with telnet ip portnumber from another computer on same network.

When I run netstat -o, I cannot see the PacsOne port number.

It appears that PacsOne Server was not running on your server.

Check if you see both PacsOneSrv.exe and PacsOne.exe running from the process list on your server:

1. If you're running Windows, press CTL-ALT-DLT, Task Manager->Process List->Show All Processes

2. If you're running Linux, type:

# ps -ef|grep PacsOne

If you do not see both executables running, then your trial license is either missing or invalid. If this is the case, you can send it to mailto:pacsone@pacsone.net and we'll check it out.