SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Gold/Mining/Energy : Daytrading Canadian stocks in Realtime

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: StockPro who wrote (5167)3/29/1999 7:57:00 PM
From: StockPro  Read Replies (1) of 62347
 
Here's a copy of the e-mail I just sent to the webmaster at CSW ...


To Whom It May Concern,

While particpating in a day-trading thread today at Silicon Investors, it became
apparent that many users of real-time services of Canada StockWatch were
experiencing severe slow-down and packet losses when accessing your web-site.

Upon further collective investigation by a number of members in the discussion
forum it became apparent that the "suspected" source of the problem was an
unknown and/or unidentifiable node/router between BC Tel [207.174.67.49]
and yourselves [207.102.62.61].

A copy of the results of a "tracert" from my Win95 (ver B) clone (running
Netscape Navigator v4.50 as the browser) are pasted below ...

Tracing route to web.canada-stockwatch.com [207.102.62.30]
over a maximum of 30 hops:

1 32 ms 22 ms 37 ms 24.64.88.1
2 30 ms 11 ms 24 ms 24.64.3.3
3 22 ms 36 ms 39 ms cgcore1-f1-0-0.cg.sfl.net [204.209.214.10]
4 32 ms 19 ms 47 ms clgr01-shaw01-fe0-0.tac.net [207.229.15.253]
5 29 ms 33 ms 24 ms 207.229.15.9
6 79 ms 36 ms 44 ms REGIONAL2-fe1-0-0.tac.net [205.233.111.3]
7 148 ms 64 ms 59 ms inetgw1-tac-reg2.bctel.net [204.174.67.214]
8 113 ms 58 ms 80 ms reg4-1.bctel.net [204.174.67.49]
9 * * * Request timed out.
10 69 ms 110 ms 65 ms m61.canada-stockwatch.com [207.102.62.61]
11 104 ms 68 ms 72 ms web.canada-stockwatch.com [207.102.62.30]

Trace complete.

The results for "hop #9" in the above output are very consistent ... the router
always is reported as timing out. These results were obtained from a tracert
command issued from a DOS screen running under Win95.

After further investigation, it turns out that (apparently) for various
Windows O/S machines the router is always unidentifiable due to "time-out".
However, when running a tracert command from a Unix/Linux box, the router will
respond and identify itself as [207.194.239.161]. After further investigation
it turns out that this router belongs to BC Tel.

Could you please contact the appropriate people at BC Tel and ask them to investigate
this situation. And if in fact there is a problem found I urge you to DEMAND that
they rectify the situation as soon as possible.

Sincerely,
Richard Dunhill
Calgary, Alberta

Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext