Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have an multi-tier application that lets our clients connect through the internet to us and have run into an interesting problem recently. From some client locations, User A will attempt to connect to our service and get error 10049 (cannot find address), while user B will attempt to connect using the same application, public IP, and settings and get through just fine. Normally, the client application is run from inside an internal network local to the client. Any suggestions on how I can troubleshoot this? Thanks.

share|improve this question
up vote 0 down vote accepted

Ok, I got the answer this morning. Apparently, the powers that be decided to switch off our old T1 connection last week and switch on the new cable connection for users to connect. Because of this, the users who had newer versions of the client application were able to connect just fine, while the users who had older versions were not able to connect. I maintain connection information historically so if one address fails, then another gets tried, and the new IP wasn't set up until recently, so the older versions didn't get it. The bottom line is that the older versions didn't know about the new IP so were not able to connect.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.