Aqua, thanks for the reply and input. Our system admin would swore that none has changed since time immemorial, I'll just double check with them, just in case they miss out small details.
For now, it seems that the problem has gone away after we restarted the app. There was another issue that appeared after restarting, which I mistakenly thought as the same as the issue in question, so I proceeded with the question anyway. Now that we are quite clear that the issue is no longer there, I'll just hold out for another 1-2 days before accepting your answer.
Main Topics
Browse All Topics
by: aqua9880Posted on 2008-09-08 at 07:20:06ID: 22417596
First and foremost I would check to make sure no recent windows updates effected the firewall or security settings. Those will always screwup socket based applications. The next thing I would double check is make sure that none of your TCP settings were changed, this can sometimes happen when windows decides to take a mental day on you.
The final thing to look at, any new applications or processes started or installed on either PC. Socket connections can be fickle when playing nicely with other applications.
Because your application was working for 4 months, unless someone recompiled and changed your program, shouldn't be the issue. You need to be looking for anything on your system that changed in the background.
~Aqua