Page 1 of 1

Dicom send from Ultrasound machine

Posted: Tue Oct 14, 2014 12:24 pm
by mindi2210
Friday one of our locations was able to send to the OnePACS Gateway (ONEPACS) from both Ultrasound machines with no issue. Yesterday they started to get an error on both mcahines. I can ping the Gateway computer from the US mcahine but when it I try to "verify" the OnePACS Gateway from the US machine it is unable to verify. I can ping the ultrasound machine from the Gateway computer but when I add the US machine into the Gateway admin page and try and echo it it can not echo it. They say nothing has changed on thier end. We double checked IP,AE etc..all the same. We unistalled and reinstalled the Gateway (I know that usually is not the best trouble shooting advice, but we have tried everything.) I feel like it may be something on the clinics side but they say nothing has changed in their seciruty etc. Any suggestions?

Re: Dicom send from Ultrasound machine

Posted: Tue Oct 14, 2014 1:09 pm
by jeremy
Hello -
If you have already uninstalled an reinstalled the Gateway, I would double check that a firewall or antivirus application isn't blocking the traffic to a specific port or blocking the flagging the application. Ping (ICMP) might be configured to be allowed, but other TCP/IP traffic to a specified port may be blocked. You may try to use telnet to the Gateway IP address and the configured port from the US machine. You would get a blank telnet screen if the connection succeeded and a connection error if it does not. Depending on the version of the Gateway, you may also want to check the Windows firewall exceptions (on the Gateway computer) if they have recently changed their router or Internet connection types on any of the related computers (public, private, and domain network) as they can all have different firewall rules in Windows. Adding the modality information in the Gateway generally isn't required as the images should transmit from the modality to the Gateway and the OnePacs Gateway listens promiscuously. In this case, it tends to lend more evidence that something is blocking network traffic. You can also look at the logs in C:\onepacs\gateway\server\default\log\server.log and look if any DICOM network connections are actually being made (or if there are other errors in those logs).
Regards