Oct. 20, 2018, 05:03:22 PM
+-

Random Image

 
Beta Shot
 Views: 648
Posted by Thor
Jan 13, 2009
in Lord of the Rings Online

Author Topic: A Serious problem of mine...  (Read 2200 times)

0 Members and 1 Guest are viewing this topic.

Offline GodsFury

  • Friend
  • *
  • Posts: 3,543
  • Karma: +0/-0
A Serious problem of mine...
« on: Nov. 28, 2002, 05:13:32 PM »
Ok, its been a week and i'm still having the same problem.
This problem is with my internet connection. Im running a DLS/Cable router for my home network. Its been running smoothly and great, well, untill last week. I've lost my connection time and time again having to wait 15-30 minutes for it to come back up. AT first i thought this would be my ISP but, im starting to think otherwise. The internet works fine for my sister and my dad, and Myself untill i start playing MOH:AA. Thats then the trouble begins. I get in servers fine, but after a while, i'll time out and lose total connection to the server and my connection. and this only happens while i play mohaa.

Might this be the cause of a bad set DSL/CABLE router?
This really sucks. last night i really didn't think i'd make it back for the match either.

Just wondering if anyone knew anything about DSL/Cable router's?

Offline DaiShan

  • Posts: 115
  • Karma: +0/-0
A Serious problem of mine...
« Reply #1 on: Nov. 29, 2002, 12:55:00 PM »
Traceroute
The traceroute tool is a valuable aid to network troubleshooting. It also is the most commonly misinterpreted diagnostic tool, capable of raising false alarms when nothing is wrong, and equally capable of showing no problems when quite a lot is wrong.

Before using traceroute, ensure that your network connection is idle (no download or upload), and that there is no background activity which might put traffic on your network connection. Any network traffic on a rate-capped service such as a cable modem will cause spuriously slow timings in traceroute.

To use the traceroute tool in Windows, open a permanent command-line window. In Windows 9x/ME, make the window 50 lines high by giving the command mode con co80,50. In Windows 2K/XP, stretch the window by dragging its bottom margin. Now give the command tracert followed by the DNS name or IP number of the host to which you wish to discover the route. Here is an example:


Code: [Select]
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>tracert 208.254.41.156

Tracing route to 208.254.41.156 over a maximum of 30 hops

  1    12 ms    17 ms    15 ms  10.92.16.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     9 ms     8 ms     9 ms  68.80.0.234
  5    13 ms    13 ms    13 ms  sl-gw37-pen-7-1.sprintlink.net [144.223.44.9]
  6    44 ms    15 ms    19 ms  sl-bb20-pen-5-3.sprintlink.net [144.232.5.41]
  7    15 ms    14 ms    13 ms  sl-bb24-pen-8-0.sprintlink.net [144.232.5.166]
  8    13 ms    14 ms    22 ms  sl-bb26-rly-0-0.sprintlink.net [144.232.20.111]

  9    12 ms    16 ms    14 ms  sl-bb22-rly-9-0.sprintlink.net [144.232.14.173]

 10    14 ms    13 ms    18 ms  POS1-2.BR4.DCA6.ALTER.NET [204.255.169.129]
 11    14 ms    25 ms    16 ms  0.so-1-0-0.XL2.DCA6.ALTER.NET [152.63.41.234]
 12    15 ms    14 ms    38 ms  0.so-0-0-0.TL2.DCA6.ALTER.NET [152.63.38.73]
 13    17 ms    18 ms    20 ms  0.so-1-2-0.TL2.NYC8.ALTER.NET [152.63.3.178]
 14    25 ms    26 ms    31 ms  0.so-6-1-0.XL2.BOS4.ALTER.NET [152.63.21.73]
 15    70 ms    30 ms    27 ms  0.so-7-0-0.XR2.BOS4.ALTER.NET [152.63.16.134]
 16    30 ms    43 ms    28 ms  0.so-7-0-0.WR2.BOS6.ALTER.NET [152.63.29.221]
 17     *        *        *     Request timed out.
 18    25 ms    31 ms    29 ms  208.254.32.2
 19    28 ms    33 ms    72 ms  208.254.41.156

Trace complete.

 

thats mine. You can see that 3 time I have 100% packet loss. Not a bad thing but it slows me down thats for sure.
img]http://www.midwestdomination.com/screeni/Dai1.jpg[/img]

 

Powered by EzPortal