Identifying Servers.

[Dave Skram]

Jay,

I've been having connection and dropped bar problems all day. Can you tell me how to identify what server I'm receiving data from? 5.1 displays the server straight away but I can't find that information in 6.0 or the Data Manager. Must be missing something here. Thanks for your help.

-Dave

[Larry Marchman]

Hi Dave,

One way is to use the Netstat command to get an IP# to traceRT, or even better to use in PingPlotter utility.

Here's an article detailing the eSignal remote Port assignments and the types of data associated with each.
http://kb.esignalcentral.com/article...ticle=1327&p=1

Here's a partial paste from the aforementioned article.
Port 2189 - Connection Manager and Financial Quotes Server (required)
Port 2190 - News Server (required for News access)
Port 2192 - Intraday History Server (required for intraday and tick data)
Port 2193 - International Tick Server (required for International Intraday history data)
Port 2194 - Daily History Server (required for daily historical data)
Port 2196 - Market Depth Server (required for Market Depth data)

The 2189 Port is the one the Data Manager (winros.exe) uses.
The others are used directly by QCharts.

--------- Example of Netstat with -N for numerical IP# ------------------
C:\Documents and Settings\Larry Marchman>netstat -n
Active Connections
Proto Local Address Foreign Address State
TCP 127.0.0.1:2189 127.0.0.1:2744 ESTABLISHED
TCP 127.0.0.1:2744 127.0.0.1:2189 ESTABLISHED
TCP 192.168.0.2:1034 64.14.72.53:80 CLOSE_WAIT
TCP 192.168.0.2:1563 216.52.236.18:5030 ESTABLISHED
TCP 192.168.0.2:1564 64.93.81.10:5020 ESTABLISHED
TCP 192.168.0.2:1565 216.52.236.141:7000 ESTABLISHED
TCP 192.168.0.2:1628 209.202.214.28:23100 ESTABLISHED
TCP 192.168.0.2:2740 216.23.232.185:2189 ESTABLISHED
TCP 192.168.0.2:2746 216.23.225.112:2192 ESTABLISHED
TCP 192.168.0.2:2747 216.23.232.235:2194 ESTABLISHED
TCP 192.168.0.2:2748 216.23.224.132:2193 ESTABLISHED
TCP 192.168.0.2:2750 216.23.226.166:2196 ESTABLISHED
TCP 192.168.0.2:2752 216.23.226.208:23100 ESTABLISHED
TCP 192.168.0.2:3073 208.65.168.3:80 ESTABLISHED
TCP 192.168.0.2:3131 209.86.93.210:110 TIME_WAIT
---------------------------------------------------------------------------------------

Users of the TaskInfo system monitor have this info supplied in the Connections tab. I use and can't live without TaskInfo ($hareware)
http://www.iarsn.com/taskinfo.html

There are freebie Active Port utilities out there.
Here's one that works fine. Look for Active Ports on the page.
http://www.devicelock.com/freeware.html

LAM

[Dave Skram]

Larry,

Thank you for responding with such an exhaustive explanation. I guess I must have been unclear in my question. What I wanted to know was how to identify which server my QCharts 6 is receiving data from. The attached graphic shows QCharts 5.1.0.1, QCharts 6.0.1.2 and QLink v1.0 b2 as they run on my system every day. As you can see 5.1 is being fed from cc-12.sc8.finance.lycos.com (209.202.214.32) and Qlink is being fed from 216.23.226.208 (cc12-hwd.esignal.com). What I was interested in was how to find out where in QCharts 6 it says where it was being fed from. Now, <Ctrl><Alt> “N” in QCharts 6 does pull up the Router List dialog which does show the IPs, Servers and Ping status. I guess I could assume that the router at the top of the list (213.23.226,193, cc07-hwd.signal.com as it happens at the time of this screen capture) is the current “logged” router but I could not find confirmation of that in any of the documentation. All I need to know is if that assumption (about the Router Dialog) is correct or if it is not, then how do I go about finding the router information. Regarding the connection issue, at the time the problems occur I am generally running all three applications with QCharts 5 and Qlink 1 happily feeding data and QCharts 6 saying that it can not connect and or dropping bars. Eventually, (with enough closing and reopening of the application) the problem seems to vanish and both QCharts 6 and the Data Manager say that the “Connection is Excellent!” All my port forwarding, etc. is correct and for the most part QCharts 6 runs acceptably. It’s just that every so often it does not connect and at other times whole sections of bars just vanish from the middle of a chart. Any thoughts?

-Dave

[Larry Marchman]

What I wanted to know was how to identify which server my QCharts 6 is receiving data from. ~Dave

That's the thing...it's not a single server.
The quote data comes from one server, the intraday bars from another, the daily bars from yet another.
Take another look at my post.
The server IP# next to the Netstat data with port 2189 is the server the quotes are coming from.
Port 2192 server IP# is the machine where the intraday bars come from.
So forth and so on...

What I was interested in was how to find out where in QCharts 6 it says where it was being fed from.. ~Dave

That's the thing...QC6 doesn't provide the eSignal serverS IP#s or DNS Names info.

All that stuff you see in the Router List in a 6.0 ctrl-alt-N is the 5.1 continuum feed info. Remember, with 6.0, it still connects to 5.1 continuum machines for the QC: stuff...ya know, the Breadthalyzer data, and the HotLists list of symbols.

So, one has to do the Netstat or have a utility to know what eSignal servers QCharts 6.0 is getting it's data from.

And yep, it would be a simple thing for 6.0 to display it's connections to the various eSignal servers.

It’s just that every so often it does not connect.. ~Dave

See the posts from today in the thread "login problems...please stand by"
http://forum.esignalcentral.com/show...threadid=25646
QFAI is still needed to insure a full list of continuum servers is there at login, since 6.0 does have to connect to the continuum servers in addition to all the eSignal servers.

and at other times whole sections of bars just vanish from the middle of a chart... ~Dave

Methinks that's just yer common variety bug in 6.0, worthy of a separate post to get feedback from others and Jay.

HTH,

LAM

[Dave Skram]

Larry,

Boy, talk about getting your big ‘ol nasty shoehorn out to wedge your QCharts foot into your eSignal shoe. Yikes! Anyway, thanks much. Now I can post the errors I’m getting with the server references necessary to actually sort the problems. Seems like that simple listing of server connections from within in the software (Jay!) would accelerate the QC process a bit… but that’s just me. Top of the evening to you!

-Dave

[Larry Marchman]

Okeydokie, Dave. Thanks for the thanks.

There's a whole 'nuther consideration on monitoring the I'Net path health given that the eSignal servers are not enabled for ICMP ping echos. But that's a different post for another day.

Good Luck,

LAM