I use to have the same problem - downloaded the latest version of ninjatrader and switched to verizon from brighthouse and hardwired my computers for more reliability - so far no more disconnects - I am holding my breath HA!
The following user says Thank You to Moore1937 for this post:
unfortunately no, maybe google search would reveal some software packages for this. However you can run 3 windows of Start->Run-> cmd with ping -t <IP=see below> in the background and see what they show during NT7 disconnect. As I told earlier, first run tracert 126.96.36.199 to see your path to NT/CQG servers.
Nearest IP to check on first cmd window: just first or second IP OUTSIDE of your home router's external IP (usually appears in 3rd row of tracert if you are behind natted router/firewall, or on 2nd of tracert row if your PC has public IP). That is nearest gateway of your ISP provider on their side. Loss of ping to this one indicates your connection problem between you and ISP.
Middle traceroute IP to check: 188.8.131.52. Loss of ping to this indicates that probably whole carrier netblock of *.above.net become unreachable, thus network where dataserver sits is unreachable. Cause - BGP routing problems, cables, etc.
Last CQG tick data server IP is (as far as I see on my machine, I am in Europe, this is where my NT4 connects): 184.108.40.206
Process described above is only ping response, reach ability check, but ping can't check service/application layer disruption problems on server. Also please be aware that techniques such as traffic shaping could potentially filter our ICMP echo request/reply packets that ping program generates what can give false failures, while TCP/IP still holds SYN/ACK states (btw. some stupid ISPs filter out ICMP completely for 'security' resons, so tracert/ping gives nothing=* * *) . But still process described above should be good to check against 95% percent of cases.
Hope this helps.
Last edited by andrewtrader; September 18th, 2011 at 07:43 PM.