I have an xray machine that I want to send dicom images to pacsone server.
I already had the machine set to dump dicom to a different computer that was using KPACS, but that is not pro grade and was only meant to be temporary.
I am having trouble getting the machine to verify a connection to PacsOne. The machine can verify a connection to the other computer just fine.
I have enabled promiscuous mode just in case, but still no success.
The log file tells me this:
Sat Sep 01 09:47:12 2012 INFO - Session: <2> started from SCU: 192.168.1.113
Sat Sep 01 09:47:12 2012 INFO - <2> Receiving A-ASSOCIATE-RQ PDU
Sat Sep 01 09:47:12 2012 INFO - <2> A-ASSOCIATE-RQ received successfully
Sat Sep 01 09:47:12 2012 INFO - <2> Sending A-ASSOCIATE-AC PDU
Sat Sep 01 09:47:12 2012 INFO - <2> A-ASSOCIATE-AC PDU sent successfully
Sat Sep 01 09:47:12 2012 INFO - <2> Receiving P-DATA-TF PDU
Sat Sep 01 09:48:12 2012 ERROR - Session: <2> timed out for client: 192.168.1.113, aborting
Sat Sep 01 09:48:12 2012 INFO - Session: <2> disconnected for client: 192.168.1.113
I suspect that there might be a port conflict. I tried to change the port for PacsOne server in the registry, but when I login to the server, the Dicom AE section is still telling me that my settings are as follows:
Application Entity Title: PACS
Hostname: localhost
TCP Port Number: 1234
I wanted to change the port to 4321, but I don't know if its actually changing.
Do you have any suggestions?
dicom server problems
1. To check if you have a conflict over the TCP port assigned to PacsOne Server, you can stop PacsOne Server first, then run the netstat -aon -p tcp command from a local shell, and check if you see the port number assigned to PacsOne Server is listed at the 2nd column of the command output. For example, if you've assigned port 1234 to PacsOne Server, and you see 0.0.0.0:1234 listed at the 2nd column of the above command, then that port is already in use by another application. If so, the 5th column of the command output shows the process ID (PID) of that application which is currently listening to that port.
2. Here's the procedure to change the TCP port assigned to PacsOne:
2.1. Stop PacsOne Server.
2.2. Run Windows Registry Editor, and change the following DWORD value to the new TCP port number:
HKEY_LOCAL_MACHINE\Software\RainbowFish Software\PacsOne\${AeTitle}\ServerPortNumber
2.3. Change the following Registry DWORD value to the new TCP port:
2.4. Run the following query from a MySQL shell, after logging into the PacsOne Server database as the Administrator:
mysql>update config set port=$newPort;
where:
$newPort is the new TCP port assigned to PacsOne.
2.5. Start PacsOne Server.
2. Here's the procedure to change the TCP port assigned to PacsOne:
2.1. Stop PacsOne Server.
2.2. Run Windows Registry Editor, and change the following DWORD value to the new TCP port number:
HKEY_LOCAL_MACHINE\Software\RainbowFish Software\PacsOne\${AeTitle}\ServerPortNumber
2.3. Change the following Registry DWORD value to the new TCP port:
Code: Select all
HKEY_LOCAL_MACHINE\Software\RainbowFish Software\PacsOne\${AeTitle}
mysql>update config set port=$newPort;
where:
$newPort is the new TCP port assigned to PacsOne.
2.5. Start PacsOne Server.
I changed the port, and I think it is really changed, since netstat says pacsone.exe is using the new port (4321), but in the web browser I am still seeing this in the Dicom AE section-
Current PacsOne Server Configurations:
Application Entity Title: PACS
Hostname: localhost
TCP Port Number: 1234
Is this just cosmetic? Or do I need to change something in an .ini file somewhere?
Current PacsOne Server Configurations:
Application Entity Title: PACS
Hostname: localhost
TCP Port Number: 1234
Is this just cosmetic? Or do I need to change something in an .ini file somewhere?