K-PACs, DICOM, and firewalls

spiff · Dec 4th 2008

I'm having trouble getting images to transfer (c-move) from our main PACS. I can query the studies by patient ID, modality, etc. But when I try to open a study it fails, with the remote side returning a DICOM error comment: "Error: Unable to Process; Internal Error".

The PACS server technician is unable to get a c-echo response from my KPServer even when my client is up and KPServer is clearly listening with TCP on port 104... but I can get a c-echo response from the PACS.

Could this be a firewall issue on my local machine? (MS Windows XP).

If that's possible, I need to ask our IS Security guys to open ports for me (we can't do it ourselves). What ports should I ask them to open on my local firewall? 104 and... ?

Thanks for the help.

Here is some more snippet from the K-PACS logs on a failed transfer:

Code

[336]        >> : c-move request for sequence 1.3.12.2.1107.5.1.4.49217.30010005121712374332800001335 initiated.
[DICOM SCU]        >> : Connected to: 10.127.16.70:104
[DICOM SCU]        >> : Item Type: 2
[DICOM SCU]        >> : Association Accept::ReadDynamic
[DICOM SCU]        >> : Presentation Context Accept, Transfer Syntax: 1.2.840.10008.1.2
[DICOM SCU]        >> : IWIMAGE030008.5. >> HSM1OSU
[DICOM SCU]        >> : (0000,0000),  4,	UL, "94" - Group Length
[DICOM SCU]        >> : (0000,0002), 28,	UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
[DICOM SCU]        >> : (0000,0100),  2,	US, "33" - Command Field
[DICOM SCU]        >> : (0000,0110),  2,	US, "3" - Message ID
[DICOM SCU]        >> : (0000,0600), 10,	AE, "IWIMAGE03" - Move Destination
[DICOM SCU]        >> : (0000,0700),  2,	US, "0" - Priority
[DICOM SCU]        >> : (0000,0800),  2,	US, "258" - Data Set Type
[DICOM SCU]        >> : 
[DICOM SCU]        >> : IWIMAGE030008.5. >> HSM1OSU
[DICOM SCU]        >> : (0008,0021),  0,	DA, "" - Series Date
[DICOM SCU]        >> : (0008,0031),  0,	TM, "" - Series Time
[DICOM SCU]        >> : (0008,0052),  6,	CS, "SERIES" - Query/Retrieve Level
[DICOM SCU]        >> : (0008,0060),  0,	CS, "" - Modality
[DICOM SCU]        >> : (0008,103E),  0,	LO, "" - Series Description
[DICOM SCU]        >> : (0018,0015),  0,	CS, "" - Body Part Examined
[DICOM SCU]        >> : (0018,1030),  0,	LO, "" - Protocol Name
[DICOM SCU]        >> : (0018,5100),  0,	CS, "" - Patient Position
[DICOM SCU]        >> : (0020,000D), 48,	UI, "1.2.840.113745.101000.1035000.38701.3495.6371667" - Study Instance UID
[DICOM SCU]        >> : (0020,000E), 56,	UI, "1.3.12.2.1107.5.1.4.49217.30010005121712374332800001335" - Series Instance UID
[DICOM SCU]        >> : (0020,0011),  0,	IS, "" - Series Number
[DICOM SCU]        >> : 
[DICOM SCU]        >> : IWIMAGE030008.5. << HSM1OSU
[DICOM SCU]        >> : (0000,0000),  4,	UL, "124" - Group Length
[DICOM SCU]        >> : (0000,0002), 28,	UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
[DICOM SCU]        >> : (0000,0100),  2,	US, "32801" - Command Field
[DICOM SCU]        >> : (0000,0120),  2,	US, "3" - Message ID Being Responded To
[DICOM SCU]        >> : (0000,0800),  2,	US, "257" - Data Set Type
[DICOM SCU]        >> : (0000,0900),  2,	US, "49153" - Status
[DICOM SCU]        >> : (0000,0902), 40,	LO, "Error: Unable to Process; Internal Error" - Error Comment
[DICOM SCU]        >> : 
[336]        >> : Error: retreive failed for XXXXXXX, XXXXXXX, X, , , , Study: CT HEAD W/O CONTRAST=H, Sequence: 2 
*******************************************************
12/4/2008 1:21:04 PM ThreadID[336] : Closed.


Task processed with errors
*******************************************************

Display More

My local AET is IWIMAGE03 but in the log entries above, the local side is identified as IWIMAGE0300008.5. ... I assume that's normal behavior?

Yves Neumann · Dec 5th 2008

Here a little list of steps:
1. CMD-shell command "netstat -ano": the port 104 is in LISTENING mode for your KPSERVER
2. compare the PID of the netstat commad output with the PID in the task manager's process list to identify the process bound to the port is KPSERVER (maybe you need to add the PID column in your task manger view settings)
3. Check with CMD-shell command "PING _your_ip_" from the PACS that the network route is working
4. Run KPSERVER in "verbose mode" (KPACS>local settings>Server admin tool) and see if anything arrives, e.g. the C-ECHO request of your PACS.

When port 104 is LISTENING for KPSERVER and nothing shows up in the verbose output window it leads to firewall/network issues. You then need to get your IT guys in and get the 104 port open on your system and (if network wide controlled) also on any firewall on the way from the PACS. But your IT guys should know how to make your application on a specific port be able receiving incoming traffic :).

BTW, the KPSERVER only uses one (1) TCP port.

spiff · Dec 8th 2008

Quote from spiff

Could this be a firewall issue on my local machine? (MS Windows XP).

If that's possible, I need to ask our IS Security guys to open ports for me (we can't do it ourselves). What ports should I ask them to open on my local firewall? 104 and... ?

Ok, this WAS a firewall issue on my local machine (Windows XP firewall). I opened port 104 TCP to the PACS and this enabled the images to transfer.

-s

seraulu1 · Mar 22nd 2010

Quote from spiff

Ok, this WAS a firewall issue on my local machine (Windows XP firewall). I opened port 104 TCP to the PACS and this enabled the images to transfer.

-s

Thanks for that information,that's very helpful!!!!how to hypnotize someone

K-PACs, DICOM, and firewalls

Participate now!

Share