[Patricia Smith]

After months of troubleshooting we finally found the problem…it was on the third party’s side.  We put sniffers on both sides and found that our Engine Windows Operating systems was trying to send on a closed port on their Operating System…Their application failed to send a “Change Port” message…They made the change on their end and things have been working alot better.  Thanks for everyone’s help.

[Patricia Smith]

I’ll try it out,

Thanks,

John

[Patricia Smith]

Rick,

This is John Calhoun at Owensboro Medical Health System.  We’re having the same problem that I think you had.  We have a thread that we are sending ADT and Orders to over a TCP/IP VPN connection.  I’m getting the WSAEWOULDBLOCK and WSAEALREADY errors and the thread loses connection.  Did you ever find a solution to your problem?  If so, I would like to know what you did to fix it.

Thanks again,

John Calhoun

270-852-8562

jcalhoun@omhs.org

[Patricia Smith]

I was able to solve my problem with the advice given. Thanks again to all who helped!

[Author]

Replies