Weird Errors with Winsock and Borland Builder TClientSocket

Posted on 2001-06-30
Last Modified: 2012-06-21

I have created a few applications using Borland C++ Builder 5.0. I code on a Win 98 SE box running Winsock 2.2. I have no problems running my program.

Also, a lot of people who downloaded my programs have absolutely no problem running them. These programs use TClientSocket for http analysis (get a webpage and analyze it). However, quite a few people are unable to use my programs.

Although they use the identical servers, the identical urls, all they get is a bunch of Winsock Async 11001 DNS lookup failures, and Winsock 10049 (Socket already in use) errors. They are using the correct settings, its not a question of their settings.

I asked them to check their OS/dlls, they are also running Win98SE with Winsock 2.2. They are not running the program from behind a firewall which performs NAT. Other normal Winsock programs run fine.

Any idea WHY this could be happening ? Its very frustrating.

Question by:bluezen
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 86

Expert Comment

ID: 6240810
It could simply be possible that the DNS server your users are querying does not know (temporarily) how to resolve the URL. This happens from time to time with dialup providers, when either their zome files are not correctly updated or the DNS server is clogged up ...

Author Comment

ID: 6241469
It could simply be possible that the DNS server your users are querying does not know (temporarily)
how to resolve the URL. This happens from time to time with dialup providers, when either their zome
files are not correctly updated or the DNS server is clogged up ...

Yes I thought of that. However, they get errors 10049 and 10061 too...which are pretty inappropriate. They get flooded with errors, even though they are able to visit the SAME site in their browser at that moment.

LVL 86

Expert Comment

ID: 6241471
Well, a quick workaround would be to place an entry in the 'hosts' file (<tab>123.456.789.0)- if the error is remedied, you found the culprit...
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

LVL 14

Expert Comment

ID: 6241804
Check viruses in such computers.
LVL 32

Expert Comment

ID: 6242167
So you are saying that the ONLY place you are seeing this is with WIN98SE and WINSOCK 2.2?  (Of course, WIN98SE comes with WINSOCK 2.2).  

I'd be interested in testing a Win95 system with WINSOCK 2.2 installed to see if you problem is specific to Win98 or to WINSOCK 2.2.  Yes, Windows NT4 and W2K have WINSOCK 2.2 but it appears to be a completely different implementation than the Win9x one.

Have you tried testing this yourself on a Win98SE system?  I've written many WINSOCK apps and have never seen a specific problem on this setup but I'm not very familiar with the Borland TClientSocket library.  

Author Comment

ID: 6243362
Well thats an obvious thing to try. I tried putting in an ip address instead of the hostname, to avoid dns lookup failures, and it still didnt work.

Basically I run a Win98SE system myself and have no problems whatever...its running Winsock 2.2.

People with Win95 systems have the same problem even after installing the Winsock update for Win95.

People with Win98 and Winsock 2.2 have the same problems.

People with Win2k dont seem to have problems.

The 11001 errors cause the 10049 errors as the socket is attempted to be used though the error occurs (Im not trapping the 11001 error).

LVL 11

Expert Comment

ID: 6820132
I think you forgot this question. I will ask Community Support to close it unless you finalize it within 7 days. Unless there is objection or further activity,  I will suggest to refund the points and PAQ at zero points since nobody had a solution for you.

The link to the Community Support area is:



Accepted Solution

ComTech earned 0 total points
ID: 6837802
Question will be placed in PAQ.


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Errors will happen. It is a fact of life for the programmer. How and when errors are detected have a great impact on quality and cost of a product. It is better to detect errors at compile time, when possible and practical. Errors that make their wa…
Article by: SunnyDark
This article's goal is to present you with an easy to use XML wrapper for C++ and also present some interesting techniques that you might use with MS C++. The reason I built this class is to ease the pain of using XML files with C++, since there is…
The viewer will learn how to pass data into a function in C++. This is one step further in using functions. Instead of only printing text onto the console, the function will be able to perform calculations with argumentents given by the user.
The viewer will learn how to clear a vector as well as how to detect empty vectors in C++.

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question