Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : KITCO - Gold discussion -- Ignore unavailable to you. Want to Upgrade?

To: Andrew who wrote (291)	9/25/1999 3:11:00 PM
From: ali	Respond to of 989

Hi kitco friends ('n nuts:-)here is what bart had to say: Date: Sat Sep 25 1999 11:43 Bart Kitner (Kitco) (If you can read this, then you don't need to.) ID#259199: Copyright © 1999 Bart Kitner (Kitco)/Kitco Inc. All rights reserved But pass it on to others who are having problems accessing our site. I don't have posting access at SI, so if someone would post it on the Kitco Backup Discussion site there it would also be much appreciated. After reading the text that follows, if any technical people have any ideas for our service provider send them to support@videotron.net>support@videotron.net referring to ticket#1999-1995. Thanks Bart TEXT FROM OUR ISP REQUESTING ASSISTANCE: "Mr Kitner, numerous clients have reported a similar problem. We are currently investigating the phenomenon and I must say that we are mystified. As a matter of fact, we are looking for "a few good people" that could help us troubleshoot the problem. Many of those reporting the problem also report that ping and traceroute do work. This is the tricky part: ping and traceroute work, but not http. We can test connectivity using traceroute gateway and looking glasses all over the world. This probleme is higher up the OSI model stack. You seem to be offering your cooperation in this matter. It would greatly help us if those people that reported an access problem could: a ) ping and traceroute your site ( Click on the attachment for a three-line explanation of how to do a traceroute ) b ) try to access www.videotron.net, www.infiniT.net c ) if http access fails, if they could traceroute, and send it to us, referring to ticket #1999-1995, it would help us. Also, if a few of them were available for us to call them to have them try a few thing to help us pinpoint the problem or at least where it seems to occur, it would be great. If they are available, they could include their name and phone number. thank you. we'll keep you posted. support@videotron.net ------------------------------------------------------------------- Pierre Nepveu tel: +1 800 368-9314 Network Administrator / DNSMaster Return to Kitco Homepage

To: Andrew who wrote (291)	9/25/1999 7:33:00 PM
From: dynamitehandler	Read Replies (1) \| Respond to of 989

I'm finding similar results with TRACERT, although I am getting into the Kitco site alright. ========================== 4 188 ms 165 ms 169 ms 205.162.192.33 5 206 ms 236 ms 199 ms sl-gw1-che-1-0-T1.sprintlink.net [144.224.13.17] 6 265 ms 289 ms 299 ms sl-bb1-che-1-0.sprintlink.net [144.224.10.1] 7 279 ms 213 ms 226 ms sl-bb10-che-0-1.sprintlink.net [144.232.6.197] 8 208 ms 248 ms 249 ms sl-bb10-stk-0-0.sprintlink.net [144.232.8.30] 9 280 ms 319 ms 289 ms sl-bb10-pen-6-0.sprintlink.net [144.232.8.177] 10 325 ms 279 ms 309 ms sl-gw16-pen-8-0-0.sprintlink.net [144.232.5.98] 11 294 ms 289 ms 288 ms sl-teleglob-3-0-0.sprintlink.net [144.228.164.62] 12 285 ms 289 ms 309 ms if-3-2.core1.NewYork.Teleglobe.net [207.45.223.166] 13 455 ms 469 ms 449 ms if-1-1.core1.Montreal.Teleglobe.net [207.45.223.61] 14 535 ms 449 ms 449 ms cust-gw.Teleglobe.net [207.45.204.2] 15 524 ms 529 ms 449 ms ia-piex-gw03-fe5-0-0.videotron.net [207.253.253.51] 16 391 ms 465 ms 369 ms ia-piex-gw03-s3-1-cr150.videotron.net [207.253.240.150] 17 424 ms 408 ms 404 ms www.kitcomm.com [207.96.251.137] Trace complete. ============================== The slow-up seems to begin at Montreal.Teleglobe