
Forums (http://www.elitetrader.com/vb/index.php)
- Backup and Security (http://www.elitetrader.com/vb/forumdisplay.php?forumid=52)
-- Looking for a connection monitor that tells you if your internet died (http://www.elitetrader.com/vb/showthread.php?threadid=213932)
Looking for a connection monitor that tells you if your internet died
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
u could try some sort of online game. those things are very sensitive to changes in connection.
1 sec give me a break
Listen to online radio.
It needs to be something passive that I just check the logs after. I will have to monitor everyday all day so any active solution is not optimal
Quote tracker will tell you when you've lost the connection to your broker for whatever reason.
Quote from Arthur Deco:
Listen to online radio.
http://www.connectionmonitor.net/
http://www.pingdom.com/services/
The easiest way is to open the black command prompt window and type "ping myfavouritewebsite.com -t". You will immediately see the output format changing when connection drops. (The output doesn't keep a timestamp. So, you need something m,ore sophisticated if you want to see when connection dropped in the past.)
I am unclear if you are looking for a GUI software to confirm what you are already seeing, or if you are looking for an SNMP/WMI programmatic indicator. As it happens, there are even events that ones program can subscribe to which identify losing and regaining local connectivity. In general, routers/teaming technologies commonly use a consensus of ping results from a variety of ping targets to determine which paths are functional.
I use 'NetWorx': http://www.softperfect.com/products/networx/
go to Settings/Notifications
and use this sound: http://soundbible.com/843-Intruder-Alert.html
Ping Plotter standard / Pro or Multiping. http://www.nessoft.com/products.html
Re: Looking for a connection monitor that tells you if your internet died
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
Re: Re: Looking for a connection monitor that tells you if your internet died
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.
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
Re: Re: Re: Looking for a connection monitor that tells you if your internet died
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.
Re: Re: Re: Re: Looking for a connection monitor that tells you if your internet died
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
Re: Re: Re: Re: Re: Looking for a connection monitor that tells you if your internet died
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.
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
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?
Quote from Daal:
I'm buying a good wireless antenna and will use that instead of the built-in one
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
Quote from LeeD:
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?
Quote from fullautotrading:
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;
}
}
I had the same issue - I have several computers that needs to communicate to a host Server. So I wrote a cmd file which uses the ping -t and tracert (if wanted) and captures the results to a txt file with date and time. I wanted to be able to run the capture from the host server for all my computers, and forget it. I downloaded forfiles.exe from the windows resource kit (google forfiles.exe download), and added a line in the script that deletes old logs to prevent the hard drive from filling up down the road. I've been running this script for several months and works like a champ.
To create the cmd file. Copy and paste the below script into notepad, and save it any name you want, with a .cmd ext. (example is Ping_Capture.cmd). Make a folder C:\Ping_Test and save the file there (unless you modify the script to run from a different folder)
A couple of things to look for. Make sure forfiles.exe is your path (I copied it to the windows\system32 folder), and make sure the cmd file ends with .cmd and not .txt. I had to go to a command window and rename it.
Doubleclick the script and it prompt for
- the IP address or Host name you want to ping (google.com)
- folder name (don't put in a path - just the name (Google)
- how many days to keep the logs
- include Traceert in the logs (Y/N)
Then a screen will show the details about the running script. Go to the log files and open them up in notepad.
----------------
@echo off
Rem This script needs to be ran from C:\Ping_Test, unless the script is modified.
Rem The script does a tracert, 500 pings and everyday deletes old log files.
Rem Creates a new log file every hour, in a date folder
Cls
Echo.
Echo.
Setlocal
Set _IP_Address=
Set _Fld_Name=
Set _Log_Limit=
Set _Tracert=
set _tr=
:IP
Set /P _IP_Address=Enter IP address or Host Name:
IF ERRORLEVEL 1 GOTO IP
:Fdr
Set /P _Fld_Name=Enter Folder Name:
IF ERRORLEVEL 1 GOTO Fdr
:log
Set /P _Log_Limit=Enter how many days to keep logs:
IF ERRORLEVEL 1 GOTO Log
:Trc
Set /P _Tracert=Inclued Tracert in Logs (Y/N) :
IF ERRORLEVEL 1 GOTO Trc
Set _logpath=c:\ping_test\Logs\%_Fld_Name%
echo %_Tracert%| find /i "Y" >NUL && set _tr=is
echo %_Tracert%| find /i "N" >NUL && set _tr=is not
if "%_tr%" == "" (set _tr=is not)
if not %_log_Limit% LEQ 100 set _log_Limit=1
for /F "tokens=2-4 delims=/- " %%c in ('date/T') do set _today=%%c-%%d-%%e
cls
Echo.
Echo.
Echo ******************************************************************
Echo.
Echo. Script started on %_today% at %Time%
Echo. Ping Capture for %_IP_Address%
Echo. Logs are located at c:\ping_test\Logs\%_Fld_Name%
Echo. Logs will be kept for %_Log_Limit% Day(s)
Echo. Trace Route %_tr% included in the logs
Echo.
Echo. CTL-C to stop the script
Echo.
Echo ******************************************************************
:Start
for /F %%a in ('Date /t') do (For /F "delims=/" %%b in ("%%a") do set _pday=%%b)
for /F "tokens=2-4 delims=/- " %%c in ('date/T') do set _today=%%c-%%d-%%e
for /F "tokens=1 delims=:" %%h in ('time /t') do set _Hour=%%h
for /F "tokens=2 delims=:" %%m in ('time /t') do set _min=%%m
echo %_min%| find /i "AM" >NUL && set _AmPm=AM
echo %_min%| find /i "PM" >NUL && set _AmPm=PM
if not exist "%_logpath%\%_today% %_pday%" md "%_logpath%\%_today% %_pday%"
Set _logfile="%_logpath%\%_today% %_pday%\%_Fld_Name%-%_hour%-%_AmPm%.txt"
Set _D=Date: %_today%
Set _T=Time: %Time%
echo %_D% >> %_logfile%
echo %_T% >> %_logfile%
If /i NOT %_Tracert% == Y goto :Ping
tracert %_IP_Address% >> %_logfile%
:Ping
ping %_IP_Address% -n 500 >> %_logfile%
echo ----------------------------------------------------------- >> %_logfile%
for /F "tokens=2-4 delims=/- " %%c in ('date/T') do set _date=%%c-%%d-%%e
If NOT ("%_today%") == ("%_Date%") goto Cleanup
:Cleanup
ForFiles /P "%_logpath%" /d -%_Log_Limit% /C "CMD /C if @isdir==TRUE /Q /S @FILE &RD /Q /S @FILE" 2>Nul
goto start
Nothing against, good old cmd or powershell, but I usually write such maintenance scripts in Perl or VBScript(cscript). Perl makes it very easy to do list and date comparisons. VBScript is good if you want to get at performance metrics.
All times are GMT. The time now is 11:12 AM.