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)
I want to test my ping to the CME and my Broker using command prompt. Anyone know the commands?
I recently got my dedicated server and wanted to go to speedtest.net but Internet Explorer Enhanced Security Configuration on Windows Server 2008 is on. I disabled it and went back a message popped up saying you need to enable javascript. Is it save to do this? And can i install google chrome on the dedicated server ?
Thanks
Can you help answer these questions from other members on NexusFi?
First, install Google Chrome, and use it instead of IE, which is very (too) secured by default on 2008.
You can't ping "the CME", you can only ping your brokers's gateway servers. And in fact you can't really ping most of them, so you may try a "tracert" to the last accessible router.
To find which are the good addresses to ping, you'll have to try some "netstat" while disconnected, and then connected to your data feed, and find which are the new addresses displayed. Then try to ping or tracert these addresses.
Good luck!
An easy way to find out the IP adress of the connection to Zen-Fire is to pull up the task manager, go to the 'performance' tab, choose 'Resource monitor' and look at your TCP connections.
There you usually find an IP adress starting with 64..., and the last column on the right side shows the current latency according to that IP adress. This might give you an impression of how long your 'travel time' will be as you can see on the screenshot below, which was actually taken from my machine in Germany.
And here's the result from my VPS in Chicago (0 ms at the moment ):
Good try, but the 64.* is something else, maybe NT license server.
In your case, the good IP to test is 199.30.196.168 (which is not pingable, but have its last router at 1-2 ms).
You may also blur your second screenshot, as we can see your VPS address, and its listening TCP port (TeamViewer, RDP, ...).
Not good for security !!!
Using the resource monitor is nice, of course, but it's only working on Windows Vista or higher, my method is working on every Windows, Linux, MacOS, ...
):
