>>
>>Aside from the messages that might come back that don't include 'timeout', like destination host unreachable, it involves running an external app, and really doesn't give you the details on what state your IP connection is in; more of a problem for people not using DUN to reach the Internet, going through a proxy of some sort. You can make the same test using WInsock and get a whole lot more internal functionality.
>>>Wayne
>
> Can you give me some example of how to do it with Winsock? I may need it some day.

Sorry, I don't have any VFP code to give you for it. The VB samples in the MSDN are pretty clear about how to set up the control, though, and the syntax isn't that far from VFP.

> I have worked with the wininet.dll to connect users to our corporate LAN through DUN and the Internet, but not winsock.
>

I don't have code to give you, but as mentioned, there's sample VB code in the MSDN documentation (see my original message for exactly where). If you don't have the MSDN yourself, you can access the content through msdn.microsoft.com

There's sample Winsock code for a number of things here in the Files Section or FAQ; you might want to do a search there if you need it and can't/won't play with translating the VB sample code.