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.

SI - Site Forums : Silicon Investor - Welcome New SI Members! -- Ignore unavailable to you. Want to Upgrade?

To: justaninvestor who wrote (2225)	8/25/1998 8:55:00 PM
From: Jeffrey S. Mitchell	Read Replies (2) \| Respond to of 32883

Re: To empty your disk cache in MS IE3 1. Click on View 2. Highlight and click on Options 3. Click on the Advanced tab 4. Click on the Settings button 5. Click on Empty Folder Ping SI now and try again at 3am. At least you'll know if it's degradation because of traffic or because of the route being taken to get you there. - Jeff

To: justaninvestor who wrote (2225)	8/25/1998 10:01:00 PM
From: David Lawrence	Respond to of 32883

Try doing a traceroute from DOS. If you can, post it here or in a PM (in fixed font) It should look like this: C:\WINDOWS>tracert techstocks.com Tracing route to techstocks.com [207.178.55.5] over a maximum of 30 hops: 1 140 ms 136 ms 143 ms 32.96.116.110 2 113 ms 125 ms 145 ms 165.87.105.46 3 136 ms 147 ms 137 ms dal31-64-br2.tx.us.ibm.net [165.87.31.66] 4 142 ms 137 ms 164 ms 165.87.230.21 5 168 ms 171 ms 146 ms 165.87.30.36 6 133 ms 171 ms 150 ms 165.87.100.97 7 147 ms 253 ms 305 ms sl-bb11-atl-1-1.sprintlink.net [144.232.3.141] 8 193 ms 198 ms 212 ms sl-bb11-fw-4-0.sprintlink.net [144.232.8.98] 9 222 ms 193 ms 193 ms sl-bb10-sea-0-0.sprintlink.net [144.232.8.54] 10 283 ms 264 ms 239 ms sl-bb3-sea-0-0-0.sprintlink.net [144.232.6.18] 11 244 ms 222 ms 206 ms sl-gw2-sea-0-0.sprintlink.net [144.228.90.4] 12 354 ms 220 ms 315 ms sl-wolfe-1-1-0-T3.sprintlink.net [144.228.94.6] 13 263 ms 243 ms 264 ms sea3.wolfe.net [207.66.130.30] 14 228 ms 194 ms 197 ms go2net-gw.wolfe.net [207.66.142.94] 15 209 ms 210 ms 196 ms techstocks.com [207.178.55.5] Trace complete. C:\WINDOWS> We'll take a look at it and see if the problem is obvious.

To: justaninvestor who wrote (2225)	8/25/1998 10:12:00 PM
From: David Lawrence	Read Replies (1) \| Respond to of 32883

Also, let's take a look at some ping statistics. Modify your command line to send more packets, because default is often for only 4 packets. C:\WINDOWS>ping -n 30 techstocks.com Pinging techstocks.com [207.178.55.5] with 32 bytes of data: Reply from 207.178.55.5: bytes=32 time=279ms TTL=239 Reply from 207.178.55.5: bytes=32 time=193ms TTL=239 Reply from 207.178.55.5: bytes=32 time=186ms TTL=239 Reply from 207.178.55.5: bytes=32 time=233ms TTL=239 Reply from 207.178.55.5: bytes=32 time=186ms TTL=239 . . . Reply from 207.178.55.5: bytes=32 time=205ms TTL=239 Reply from 207.178.55.5: bytes=32 time=189ms TTL=239 Reply from 207.178.55.5: bytes=32 time=186ms TTL=239 Reply from 207.178.55.5: bytes=32 time=227ms TTL=239 C:\WINDOWS> We may have to get you a better ping utility that summarizes lost packet counts. Try your default DOS ping utility first.