Looking for a connection monitor that tells you if your internet died

[Wallace]

I use 'NetWorx': http://www.softperfect.com/products/networx/
go to Settings/Notifications
and use this sound: http://soundbible.com/843-Intruder-Alert.html

 

[Bernard111]

Ping Plotter standard / Pro or Multiping. http://www.nessoft.com/products.html

 

[fullautotrading]

Quote from Daal:

I tried a few connections monitors out there and they are graph based which doesn't help me much. I need to be able to tell if that internet went down(even if for only 1sec, if I'm reading I can't tell), in the graphs you cant distinguish between inactivity and periods where the connection died

If you download either vb.net express or c#express, it takes about 10 seconds to do that.

Any winform application has infact , within the application events, built in, disconnect/reconnect event handler which is called on these events. There you can put simple code to do anything you like.

Tom

 

[LeeD]

Quote from fullautotrading:

If you download either vb.net express or c#express, it takes about 10 seconds to do that.

Any winform application has infact , within the application events, built in, disconnect/reconnect event handler which is called on these events. There you can put simple code to do anything you like.

Tom

Except I understand it tracks LAN (or USB modem) connection. If you have a modem-router, there is no way the PC will know the cable from the modem-router to the the telephone exchange got cut... unless the PC constantly sends some requests that require such a connection.

 

[fullautotrading]

Quote from LeeD:

Except I understand it tracks LAN (or USB modem) connection. If you have a modem-router, there is no way the PC will know the cable from the modem-router to the the telephone exchange got cut... unless the PC constantly sends some requests that require such a connection.

hmmm, i am not sure what you mean. It seems to me that it correctly monitors any internet disconnection, reconnection...

You find it in: Application Properties > Wiew Application Events

Event: NetworkAvailabilityChanged
Property: e.IsNetworkAvailable

Tom

 

[Steven.Davis]

Quote from fullautotrading:

hmmm, i am not sure what you mean. It seems to me that it correctly monitors any internet disconnection, reconnection...

You find it in: Application Properties > Wiew Application Events

Event: NetworkAvailabilityChanged
Property: e.IsNetworkAvailable

Tom

I have done extensive network redundancy testing for our colocation environment. This included Windows 7 and Windows 2008. For both of these environments, the NetworkAvailabilityChanged event will fire on a failure in the cable or first switch. Failure of any switch or connection passed this point do not fire the NetworkAvailabilityChanged event. I have only ever seen Windows realize that there was a problem upstream if there was an actual TCP session running/opening. There is multi-gateway logic in Windows 2008 (7 as well I think), but the failover logic depends upon failed TCP connections. We had to use ICMP-ping packets and custom logic.

 

[fullautotrading]

Quote from Steven.Davis:

I have done extensive network redundancy testing for our colocation environment. This included Windows 7 and Windows 2008. For both of these environments, the NetworkAvailabilityChanged event will fire on a failure in the cable or first switch. Failure of any switch or connection passed this point do not fire the NetworkAvailabilityChanged event. I have only ever seen Windows realize that there was a problem upstream if there was an actual TCP session running/opening. There is multi-gateway logic in Windows 2008 (7 as well I think), but the failover logic depends upon failed TCP connections. We had to use ICMP-ping packets and custom logic.

Thanks, that is good to know. I guess that for the use the OP intended it could be fine. Or else, there are other instruments within the language which can be useful. For instance:

My.Computer.Network.Ping() and many others ...

I guess for more complex checks one could create create a simple monitor which fired every whatever interval ... it's a just a very few lines of code.

Tom

 

[Daal]

I'm using the cmd ping utility from windows, its not capturing the internet fluctuation that was the problem, guess my internet never died, it just fluctuates like crazy. The main problem is me missing hands from the pokerstars client when my internet goes idle for a while.

I'm buying a good wireless antenna and will use that instead of the built-in one

 

[LeeD]

Quote from Daal:

I'm buying a good wireless antenna and will use that instead of the built-in one

wireless is not super-stable by design. a neighbour switches on a microwave and you may loose connection for fraction of a second. have you tried ethernet cable instead?

 

[fullautotrading]

Quote from Daal:

I'm using the cmd ping utility from windows, its not capturing the internet fluctuation that was the problem, guess my internet never died, it just fluctuates like crazy. The main problem is me missing hands from the pokerstars client when my internet goes idle for a while.

I'm buying a good wireless antenna and will use that instead of the built-in one

that's another matter. Consider changing provider ;-))

Anyway in theme of checks, whenever ping might not work (it might), i have seen recommending on the web also these approaches:

{
System.Net.IPHostEntry objIPHE = System.Net.Dns.GetHostEntry("www.google.com");
}
catch
{
MessageBox.Show ("...No Conn...");
}



bool ConnectionExists()
{
try
{
System.Net.Sockets.TcpClient clnt=new System.Net.Sockets.TcpClient("www.google.com",80);
clnt.Close();
return true;
}
catch(System.Exception ex)
{
return false;
}
}


might give them a try ... let us know in case ...


Tom