All,

I use the SocketOpen, SocketSend, SocketRecv, SocketShutdown & SocketClose 
functions from the ASINet library to communicate from workstations to a 
server application running on a server.  The IP Address that the 
workstations are connecting to is an internal address of the 192.x.x.x 
scheme.  The LAN is connected to the Internet via a Sonic Firewall.  While 
the Lan is connected to the Internet via the firewall the transactions from 
the workstations to the server take about 1/2 second to complete.  When the 
ISP/Internet connection went down yesterday for 4 hours, the transactions 
from the workstations to the server took about 15 seconds to complete!  This 
does not make any sense?  The communications are on the LAN using 192.x.x.x 
addresses directly requiring no DNS resolution etc...

So my question is:  I have narrowed it down to the SocketOpen command as 
being responsible for the 15 second wait. Why would the Internet connection 
being down affect these SocketOpen commands.  There must be some type of 
waiting going on down in the WinSock that is caused by the Internet being 
down.  I would like to find some way to eliminate this problem because it 
really causes big trouble with my application if/when this happens.

Any help or insight would be appreciated.

TIA,

Jim Graham