Test device before connect()

I am using Scott Klement's socket programs to get weights from scales.
This has been running fine for over a year (thanks Scott).

Ever since the network replaced its wireless controller early this week, the
wireless connection drops at times.
(I'm already in touch with Lantronix)

When it drops, the connect() hangs for 3 to 5 minutes trying to make a
connection.
(I would like that to be a few seconds, but there are no time out values
that I can see.)
This hangs the 5250 manifest station for minutes before I can issue an error
message.

I have temporarily put a Ping in to the device before I create a socket to
the IP and port and try the connect().
Is there a way to shorten the time outs during the connect()?
The problem with the ping is it sometimes activates right after the ping.
I'm thinking if the connect() was 5 - 10 seconds, I could get good weights
most of the time.
I'm also thinking the Cisco controller is not configured properly, but
getting the network people to verify this is a nightmare.

Thanks,

Craig