also @ TechSpot: OCZ Vertex 450 SSD Review

Randomly laggy DSL

Discussion in 'Storage and Networking' started by carolinaboy, May 30, 2011.

Post New Reply
  1. carolinaboy Newcomer, in training

    well i didn't configure that much less know how so :| ill work on that asap
  2. jobeard TS Ambassador Posts: 12,227   +121

    First get email access to the help desk.
    then copy the tracert in post#1, #15, #18

    I wanted the ipconfig /all when directly connected to the modem as it would disclose the ISP configuration instead of that for your router.
  3. carolinaboy Newcomer, in training

    Okay, i just disabled IPv6 and restarted my computer, and ill get that ipconfig for you asap.

    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : wilkes.net

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . : wilkes.net
    Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
    Physical Address. . . . . . . . . : 00-21-9B-0B-12-02
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 137.118.217.116(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    Lease Obtained. . . . . . . . . . : Tuesday, May 31, 2011 3:24:04 PM
    Lease Expires . . . . . . . . . . : Wednesday, June 01, 2011 3:24:04 PM
    Default Gateway . . . . . . . . . : 137.118.216.1
    DHCP Server . . . . . . . . . . . : 137.118.136.10
    DNS Servers . . . . . . . . . . . : 137.118.136.10
    137.118.1.32
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.wilkes.net
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:86a:b6b:7689:268b(Prefer
    red)
    Link-local IPv6 Address . . . . . : fe80::86a:b6b:7689:268b%10(Preferred)
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 11:

    Connection-specific DNS Suffix . : wilkes.net
    Description . . . . . . . . . . . : isatap.wilkes.net
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::200:5efe:137.118.217.116%13(Preferr
    ed)
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 137.118.136.10
    137.118.1.32
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 12:

    Connection-specific DNS Suffix . : wilkes.net
    Description . . . . . . . . . . . : Microsoft 6to4 Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2002:8976:d974::8976:d974(Preferred)
    Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
    DNS Servers . . . . . . . . . . . : 137.118.136.10
    137.118.1.32
    NetBIOS over Tcpip. . . . . . . . : Disabled
  4. carolinaboy Newcomer, in training

    Tracing route to 137-118-216-1.wilkes.net [137.118.216.1]
    over a maximum of 30 hops:

    1 * * 101 ms 137-118-216-1.wilkes.net [137.118.216.1]

    Trace complete.


    Tracing route to 137-118-216-1.wilkes.net [137.118.216.1]
    over a maximum of 30 hops:

    1 102 ms * * 137-118-216-1.wilkes.net [137.118.216.1]
    2 37 ms 36 ms 35 ms 137-118-216-1.wilkes.net [137.118.216.1]

    Trace complete.


    Tracing route to 137-118-216-1.wilkes.net [137.118.216.1]
    over a maximum of 30 hops:

    1 2 ms 2 ms 2 ms 137-118-216-1.wilkes.net [137.118.216.1]
    2 * 103 ms * 137-118-216-1.wilkes.net [137.118.216.1]
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * 100 ms 137-118-216-1.wilkes.net [137.118.216.1]

    Trace complete.







    Pinging 137.118.216.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 137.118.216.1: bytes=32 time=437ms TTL=64
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 137.118.216.1:
    Packets: Sent = 11, Received = 1, Lost = 10 (90% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 437ms, Maximum = 437ms, Average = 437ms
  5. carolinaboy Newcomer, in training

    did you give up on me? =(
  6. jobeard TS Ambassador Posts: 12,227   +121

    No, but all the evidence in this thread point to either
    1. your Modem/router or
    2. your ISP
    IMO, You need onsite, hands-on service.
     
  7. jobeard TS Ambassador Posts: 12,227   +121

    I notice that ping -l 732 137.118.216.1 works well
    while ping -l 800 137.118.216.1 fails

    suggest you change the MTU on your system to 732

    here's how
    If you set the MTU size for a network interface manually, this setting overrides the default MTU for the network interface. The MTU size is the maximum packet size in bytes that the transport will transmit over the underlying network.

    This method affects packets sent to all destinations and may significantly affect the performance, depending on the MTU size that you set.

    To set the MTU size for the network interface, follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<ID for network interface>
    3. On the Edit menu, point to New, and then click DWORD Value.
    4. Type MTU, and then press ENTER.
    5. On the Edit menu, click Modify.
    6. In the Value data box, type the value of the MTU size, and then click OK.
    7. Quit Registry Editor, and then restart the computer.
  8. carolinaboy Newcomer, in training

    Done! thanks for all your help, much appreciated ill let you know if this MTU helps any.

    Quick question, Does that MTU change work with a router, and if it does do they need to change there MTU settings for it to change for them?
  9. jobeard TS Ambassador Posts: 12,227   +121

    yes, setting the MTU in the router enforces a common MTU to the whole lan - -
    but try it out first one one system
  10. carolinaboy Newcomer, in training

    Iv done it, Didn't help at all im going to give my ISP a call now since they won't answer my emails thanks for all your help.
  11. Tmagic650 TS Ambassador Posts: 18,749   +62

    Be sure to tell them all the things you tried and about Jobeard's tips. Just because they gave you a new modem, it doesn't mean that it is good. Have them swap it out again