Jump to content

TCPConnect Timeout

Recommended Posts

I have created a program which sends out a message via TCPSend to every computer in the building. If the computer has the client application running which listens to a specific port, everything works great. However, if a computer does not have the client running, the TCPConnect takes 20 seconds before it fails. I have about 300 computers I need to connect to with this program so 20 seconds for each failed computer is a long time to wait. (This application is meant to send emergency notifications)

Is there a way to change the timeout period for TCPConnect, or any way to skip a computer if it is not listening to that particular port? Opt(TCPTimeout) is already set for 100 milliseconds by default (and I have adjusted it lower) so I am not sure how to make the TCPConnect fail faster if it cannot send to that port. Obviously, if the client is running on each and every computer, this would not be a problem; however, even just 10 computers without the client running could really slow things down.

Any ideas?

Link to comment
Share on other sites

Thanks for the reply. I suppose I could have figured out there was a bug in the TCPConnect had a done a search. :oops:

I guess I will have to find some way around it, or even use another method to get the message sent.

Thanks again.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...