Go Back   Cyber Tech Help Support Forums > Hardware > Networking
Reload this Page Constantly losing internet
Register FAQ Calendar Today's Active Topics Search

Notices

Networking Use this board for problem solving and the discussion of Networking, router, and Wi-Fi issues

Reply
 
Topic Tools
  #1  
Old March 21st, 2009, 05:53 PM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
Constantly losing internet
I can't take it anymore. I know I have an old modem, SB3100, but I doubt it is my problem! I don't want to replace my modem, router and then be told they aren't the problem, not everyone has money to throw out. I am constantly losing packets and I can't take it anymore! I hate waiting to connect to the internet, I hate it all.

Look at my problem!


Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Xeno>ping -t google.com

Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=84ms TTL=242
Reply from 209.85.171.100: bytes=32 time=90ms TTL=242
Reply from 209.85.171.100: bytes=32 time=88ms TTL=242
Reply from 209.85.171.100: bytes=32 time=88ms TTL=242
Reply from 209.85.171.100: bytes=32 time=85ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=89ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=85ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=88ms TTL=242
Reply from 209.85.171.100: bytes=32 time=89ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=85ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=84ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=99ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=85ms TTL=242
Reply from 209.85.171.100: bytes=32 time=91ms TTL=242
Request timed out.
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.171.100: bytes=32 time=98ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=88ms TTL=242
Reply from 209.85.171.100: bytes=32 time=83ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=83ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=87ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242
Reply from 209.85.171.100: bytes=32 time=86ms TTL=242

Ping statistics for 209.85.171.100:
Packets: Sent = 58, Received = 48, Lost = 10 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 99ms, Average = 87ms
Control-C
^C

There's my problem. I can't stay connected to the internet and I don't know where to start before dishing out money. If I am told "Receiving problem is the router" I'll go buy a new one. or "Receiving problem is modem" I'll replace it! But I need to know the problem before replacing my entire house and be told something just needs to be updated, screwed in tightly or blown in. PLEASE help me.
Only sometimes I get a stray lost packet, but it is usually after so many sent. Please help me.
Reply With Quote
  #2  
Old March 21st, 2009, 06:12 PM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
  • A clear explanation of the problem you are having
    • What doesn't work
    My internet is constantly losing packets, disabling me from having a constant connection. (Playing game
    • What does works
    The internet works when not downtime. Speed is just as good as it ever was. Activity on the modem is not the usual, and on the router, the light hooked up to my computer stays constant when timing out.
    • What you've tried
    I have tried blowing in the ports, I had them unhooked overnight, unhooking EVERYTHING. Bypassing the splitter, going straight from modem to computer(Didn't work). I diagnosed it, repaired it, tried static IP address... Switched the blue cables around.. Unplugged extra junk on the thingie with all the plugs available.
  • A description of your network
    • Whether its dialup, cable, dsl,...
    Cable
    • Make and model of your modem
    SB3100
    • Whether you have a router (If you do then include the what make & model)
    Netgear WGT624
    • Do you have multiple PCs networked
    Yes, but the other is off while I try just this one.
    • Is it wireless or not (If wireless include the make & model of the wireless adapter)
    It is wireless, but I am hooked up to the LAN
    • Are you using Internet Connection Sharing (ICS)
    I'm not sure
  • The OS(s) you are using
    • Windows 98 (SE)
    • Windows XP (SP1, SP2)
    • Windows 2000, 2003
    • Windows Vista
    • linux (redhat, debian,...)
    Vista


  • What do you have for an IP address?
    • Run "cmd /k ipconfig" (either in a DOS command window or using Run... from the Start menu
    • For windows 98 use command instead of cmd
    • A bad IP address is 0.0.0.0 or 169.254.?.?
    • If you have a router, a good IP is usually 192.168.0.? or 192.168.1.?
    192.168.0.3
  • What is your default gateway?
    • Run "cmd /k ipconfig"
    192.168.0.1
  • Can you ping your default gateway?
    • Run "cmd /k ping IP_ADDRESS_OF_DEFAULT_GATEWAY"

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

    Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms


    C:\Users\Xeno>ping 192.168.0.1

    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

    Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

Reply With Quote
  #3  
Old March 21st, 2009, 06:46 PM
z1p's Avatar
z1p z1p is offline
Cyber Tech Help Moderator
  
Join Date: Oct 2004
O/S: Windows Vista 64-bit
Location: Massachusetts
Posts: 6,668
Hi Xeno-Felix,

nailing down an issue like this remotely can be difficult, but lets give it a go.

I need you to run a few more commands.

run ping -t to your default gateway to make sure you don't see any timeouts there, or even a big spike in ping times.

run tracert www.google.com and post the results back. (you may want to run this a few times to see if times varies or if it fails at all)

You said you had aother PCs on your LAN, do they experience problems too?
Reply With Quote
  #4  
Old March 21st, 2009, 09:19 PM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
Thank you for coming to assist me in my need , and with haste.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Xeno>ping -t 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 55, Received = 55, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Control-C
^C


Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Xeno>tracert www.google.com
Unable to resolve target system name www.google.com.

C:\Users\Xeno>tracert www.google.com

Tracing route to www.l.google.com [74.125.95.147]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms ip98-185-130-70.lf.br.cox.net [98.185.130.70]
2 * * * Request timed out.
3 * 16 ms 19 ms wsip-24-249-37-153.br.br.cox.net [24.249.37.153]

4 16 ms 16 ms 19 ms btnrdsrj02-so020.0.br.br.cox.net [24.249.36.189]

5 23 ms 25 ms 23 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
6 24 ms 27 ms 31 ms 66.249.94.94
7 32 ms 34 ms 38 ms 216.239.47.121
8 * * * Request timed out.
9 * 56 ms 65 ms 209.85.241.27
10 79 ms 53 ms 53 ms 209.85.240.49
11 56 ms 56 ms 53 ms iw-in-f147.google.com [74.125.95.147]

Trace complete.

C:\Users\Xeno>tracert www.google.com
Unable to resolve target system name www.google.com.

C:\Users\Xeno>tracert www.google.com

Tracing route to www.l.google.com [64.233.169.103]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms ip98-185-130-70.lf.br.cox.net [98.185.130.70]
2 * * * Request timed out.
3 * * 24 ms wsip-24-249-37-149.br.br.cox.net [24.249.37.149]

4 24 ms 11 ms 11 ms ip24-249-36-193.br.br.cox.net [24.249.36.193]
5 43 ms 21 ms 25 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
6 25 ms 25 ms 23 ms 66.249.94.94
7 63 ms 65 ms 66 ms 72.14.238.243
8 * * * Request timed out.
9 * 75 ms 93 ms 64.233.175.109
10 62 ms 64 ms 63 ms 72.14.232.21
11 61 ms 58 ms 60 ms yo-in-f103.google.com [64.233.169.103]

Trace complete.

C:\Users\Xeno>tracert www.google.com

Tracing route to www.l.google.com [64.233.169.103]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms ip98-185-130-70.lf.br.cox.net [98.185.130.70]
2 * * * Request timed out.
3 25 ms 24 ms 24 ms wsip-24-249-37-149.br.br.cox.net [24.249.37.149]

4 22 ms 19 ms 17 ms ip24-249-36-193.br.br.cox.net [24.249.36.193]
5 27 ms 28 ms 28 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
6 23 ms 23 ms 23 ms 66.249.94.94
7 63 ms 69 ms 63 ms 72.14.238.243
8 * * * Request timed out.
9 * 59 ms 66 ms 64.233.175.219
10 61 ms 60 ms 59 ms 72.14.232.21
11 61 ms 60 ms 62 ms yo-in-f103.google.com [64.233.169.103]

Trace complete.

The other computer does experience that problem. At the time, the user experienced this and I happened to be trying to run many tabs at once with many graphics, so I seen nothing of the slow-appearing internet. I've tried the same on that computer as I did this one(the diagnosing, repairing and such).
Reply With Quote
  #5  
Old March 21st, 2009, 09:57 PM
z1p's Avatar
z1p z1p is offline
Cyber Tech Help Moderator
  
Join Date: Oct 2004
O/S: Windows Vista 64-bit
Location: Massachusetts
Posts: 6,668
Hops 2 and 8 timing out all the time is most likely because the routers at those hops are set not to respond to 'trace' request.

Now hop 3 is a different story, you got a response some of the time, so we know it is setup to respond, now why did you get time outs.

Can you run ping -t to 98.185.130.70 and 24.249.37.149 and see if you hit any time outs.
Reply With Quote
  #6  
Old March 21st, 2009, 10:44 PM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Xeno>ping -t 98.185.130.70

Pinging 98.185.130.70 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 98.185.130.70:
Packets: Sent = 18, Received = 0, Lost = 18 (100% loss),
Control-C
^C

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Xeno>ping -t 24.249.37.149

Pinging 24.249.37.149 with 32 bytes of data:
Reply from 24.249.37.149: bytes=32 time=12ms TTL=253
Reply from 24.249.37.149: bytes=32 time=9ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=11ms TTL=253
Reply from 24.249.37.149: bytes=32 time=9ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=12ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=9ms TTL=253
Reply from 24.249.37.149: bytes=32 time=24ms TTL=253
Reply from 24.249.37.149: bytes=32 time=12ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=20ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Reply from 24.249.37.149: bytes=32 time=11ms TTL=253
Reply from 24.249.37.149: bytes=32 time=22ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=11ms TTL=253
Reply from 24.249.37.149: bytes=32 time=179ms TTL=253
Reply from 24.249.37.149: bytes=32 time=206ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=11ms TTL=253
Reply from 24.249.37.149: bytes=32 time=9ms TTL=253
Reply from 24.249.37.149: bytes=32 time=11ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Reply from 24.249.37.149: bytes=32 time=11ms TTL=253
Reply from 24.249.37.149: bytes=32 time=10ms TTL=253
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.249.37.149:
Packets: Sent = 41, Received = 32, Lost = 9 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 206ms, Average = 22ms
Control-C
^C
C:\Users\Xeno>
Reply With Quote
  #7  
Old March 22nd, 2009, 08:30 PM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
-cough- I said something stupid and edited it.
And I'm going to edit again. I connected it to the modem and figured out how to make the internet work for it. I thought it was interesting when I did tracert google.com. It may be useless though.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Xeno>tracert google.com

Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:

1 * * * Request timed out.
2 9 ms 9 ms 7 ms wsip-24-249-37-149.br.br.cox.net [24.249.37.149]

3 11 ms 10 ms 9 ms ip24-249-36-193.br.br.cox.net [24.249.36.193]
4 20 ms 23 ms 20 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
5 21 ms 23 ms 22 ms 66.249.94.94
6 * * * Request timed out.
7 72 ms 58 ms 82 ms 72.14.232.213
8 56 ms 63 ms 58 ms 209.85.253.137
9 58 ms 55 ms 59 ms yx-in-f100.google.com [74.125.45.100]

Trace complete.

C:\Users\Xeno>tracert google.com

Tracing route to google.com [74.125.45.100]
over a maximum of 30 hops:

1 * * * Request timed out.
2 9 ms 9 ms 9 ms wsip-24-249-37-149.br.br.cox.net [24.249.37.149]

3 12 ms 13 ms 11 ms ip24-249-36-193.br.br.cox.net [24.249.36.193]
4 22 ms 19 ms 19 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
5 22 ms 33 ms 21 ms 66.249.94.94
6 * * * Request timed out.
7 59 ms 57 ms 61 ms 72.14.232.213
8 65 ms 62 ms 80 ms 209.85.253.137
9 60 ms 60 ms 57 ms yx-in-f100.google.com [74.125.45.100]

Trace complete.

C:\Users\Xeno>tracert google.com
Unable to resolve target system name google.com.

C:\Users\Xeno>
Last edited by Xeno-Fenix; March 22nd, 2009 at 08:40 PM. Reason: I'm stuppid.
Reply With Quote
  #8  
Old March 23rd, 2009, 07:42 AM
XChadX XChadX is offline
New Member
  
Join Date: Mar 2009
Posts: 7
im having same problem right now u have comcast?
Reply With Quote
  #9  
Old March 23rd, 2009, 12:49 PM
z1p's Avatar
z1p z1p is offline
Cyber Tech Help Moderator
  
Join Date: Oct 2004
O/S: Windows Vista 64-bit
Location: Massachusetts
Posts: 6,668
Xeno-Fenix,

The tracert without the modem show the same hops, denying the tracert request, the numbers are different by one because you took the router out so there is one less hop.

That last failure is interesting as it appears to be a DNS lookup failure. But I guess that could be caused by network timeouts.

Can you look at the section on setting your MTU on this page and give it a try. Lets make sure something as simple as a misconfigured MTU isn't causing you grief.
Reply With Quote
  #10  
Old March 23rd, 2009, 11:11 PM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
I checked in cmd, 1400 worked - so I typed 1400 in the MTU box, pressed save and rebooted. Didn't fix :{

No xChadx, I have cox.
Last edited by Xeno-Fenix; March 23rd, 2009 at 11:13 PM. Reason: Responding to XchadX
Reply With Quote
  #11  
Old March 24th, 2009, 12:11 AM
z1p's Avatar
z1p z1p is offline
Cyber Tech Help Moderator
  
Join Date: Oct 2004
O/S: Windows Vista 64-bit
Location: Massachusetts
Posts: 6,668
Did you run for a while with just the modem? If so did you experience drops still?
Reply With Quote
  #12  
Old March 24th, 2009, 01:40 AM
Xeno-Fenix Xeno-Fenix is offline
Senior Member
  
Join Date: Jun 2004
Posts: 157
Yep, still drops :[
Reply With Quote
  #13  
Old March 24th, 2009, 05:35 PM
XChadX XChadX is offline
New Member
  
Join Date: Mar 2009
Posts: 7
fenix idk if this is any help too u but. comcast came out today and fixed my drop issues by replacing a line in my wall. its was over 40 years old. turns out in summer time i never get drops but when it got cold in winter my connection would be horrible.

anyways that was my problem good luck with yours
Reply With Quote
  #14  
Old March 25th, 2009, 06:00 PM
z1p's Avatar
z1p z1p is offline
Cyber Tech Help Moderator
  
Join Date: Oct 2004
O/S: Windows Vista 64-bit
Location: Massachusetts
Posts: 6,668
Xeno-Fenix,

XChadX makes a good point. The drops could be due to the quality of the cable coming to your house. It could be your modem or a dozen other things. It does not looks like a software or configuration issue.

Contacting your ISP and tellingthem that this is not acceptable seems to be the way to go.
Reply With Quote
Reply

Bookmarks

« Previous Topic | Next Topic »

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Topics
Topic Topic Starter Forum Replies Last Post
I keep Losing my Internet Turkey Loaf Networking 1 January 13th, 2007 03:21 PM
Constantly losing Internet connection STLCards002 Internet / Browsers 0 November 11th, 2006 11:39 PM
I keep losing my Internet jkaspick Internet / Browsers 1 April 18th, 2006 10:22 AM
losing internet connection simplepawn Windows XP 5 October 8th, 2005 12:22 AM
I keep losing my internet connection lcyber Windows NT, 2000, 2003, 2008, 2012 3 January 15th, 2004 01:34 AM


All times are GMT +1. The time now is 06:40 AM.