Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Anybody having problems w/ AMP/CQG loss off connection
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!
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 64.208.51.245 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: 64.125.30.142. 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): 64.208.51.245
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.
I think micro futures for eurousd are crap. Just looked once, maybe I am wrong.
You should think trade spot, you can manage your risk much better than trading futures.
Looks like it may have been an id10t error. my cable wasnt securely plugged in and I was running off wireless. I'll report back if I have any problems.
