[baltimorepm] help with Net::HL7::Connection
benparse at yahoo.com
benparse at yahoo.com
Mon Oct 6 07:35:46 PDT 2014
I may not be following this correctly, ... Check control panel->system n security -> windows firewall
If u recvd this box then there maybe configuration item
-----Original Message-----
From: "Bernie Simon" <bsimon at stsci.edu>
Sent: 10/6/2014 10:13
To: "Baltimore Perl Mongers" <baltimore-pm at pm.org>
Subject: Re: [baltimorepm] help with Net::HL7::Connection
The standard command to check for open ports is
netstat -en
More information can be found on the web. Don’t know how this stuff in configured under Windows.
From: Dawn Wallis <wallisds at gmail.com>
Reply-To: Baltimore Perl Mongers <baltimore-pm at pm.org>
Date: Monday, October 6, 2014 at 9:48 AM
To: "baltimore-pm at pm.org" <baltimore-pm at pm.org>
Subject: [baltimorepm] help with Net::HL7::Connection
At work we had a Windows XP computer setup to collect lab results from Quest. That data was parsed and transferred to our mysql database (on a CentOS server) using Net::HL7::Connection. Recently we had to upgrade to Windows 7 for the capturing computer. So I'm using Windows 7 to collect blood work data from Quest.
The scripts that were on the XP machine seem to work pretty well on the 7 box too, so I am able to get the data parsed and ready for transport to my mysql database server, but it doesn't send.
I am getting a "Could not connect. No connection could be made because the target machine actively refused it" error.
Net::HL7::Connection takes a host and port but no password or anything. I figure I'm supposed to open a port on the db server to allow this incoming connection, but I'm having trouble figuring that part out. I don't know where to look on the centos server to see if a port is open for the other xp computer, what file to edit... etc.
Any suggestions?
Thanks,
Dawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/baltimore-pm/attachments/20141006/13111fb9/attachment-0001.html>
More information about the Baltimore-pm
mailing list