forum.vdsworld.com

[moke]

I don't think any solution that checks for public and private IPs will work. I am pretty sure that most users that are on a network will have only 1 IP address. The router controlls the public data flow to the internal network and has the only public IP on most networks. You may be able to check the to see if the Gateway is a puiblic IP but even that would be unreliable beacause you can route through private IPs also.

Using any form of ping will rarely work. Many network administrators will not allow internal users to ping (I initially used serveral flavors of ping). The "Ping of Death" virus reaked havoc on many networks so even many web servers can no longer be pinged, try and ping microsoft.com and see what happens.

I believe the only reliable method is to:
a)determine what your app needs to check for. (ie: web pages, mail, FTP etc.)
b) Test that protocol(s) or port using a known public reference point like microsoft or Yahoo.

The example I posted earlier in this thread has been in use for over a year by serveral hundred users. It works reliably to test for access to web pages. If someone has a better way I'd love to hear it, my main application is very dependant on the internet and uses mail, FTP and HTTP.

moke

[Serge]

I too found that the registry entries suggested by mrfloppy weren't there in my registry (running ME) - pity!

I tried the cmdnet.exe file at work (network and permanent ISDN net connection) and found that i got the same IP whether on the net or not (the l switch) and that it was very very slow on the p switch when not connected to the net.

Serge

[Dr. Dread]