Skip to content
Michealm's profile

New Contributor

 • 

15 Messages

Tuesday, February 18th, 2014 4:00 PM

Connection Issues (Spokane Washington)

I have been having constant connection issues for over a month now, I have been having to constantly reboot my modem and router in order to get my service back and running. I have already tried having a PC hooked directly to hte modem and the issue still happens, I cannot check signal levels as my SMC D3G is in bridged mode. 

 

The following is a screen capture showing the most recent from my Atlas Probe.

(Also note the latency with it as well.)

 

ripe packet loss.PNG

New Contributor

 • 

15 Messages

11 years ago

Just ran a ping to yahoo.com .... this is what I am getting:

 

C:\Users\Micheal>ping -t yahoo.com

Pinging yahoo.com [98.139.183.24] with 32 bytes of data:
Reply from 98.139.183.24: bytes=32 time=133ms TTL=50
Reply from 98.139.183.24: bytes=32 time=202ms TTL=48
Reply from 98.139.183.24: bytes=32 time=131ms TTL=48
Reply from 98.139.183.24: bytes=32 time=127ms TTL=48
Reply from 98.139.183.24: bytes=32 time=129ms TTL=48
Reply from 98.139.183.24: bytes=32 time=147ms TTL=50
Reply from 98.139.183.24: bytes=32 time=104ms TTL=50
Reply from 98.139.183.24: bytes=32 time=115ms TTL=50
Reply from 98.139.183.24: bytes=32 time=114ms TTL=50
Reply from 98.139.183.24: bytes=32 time=126ms TTL=50
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.139.183.24:
    Packets: Sent = 20, Received = 10, Lost = 10 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 104ms, Maximum = 202ms, Average = 132ms

 What the heck is going on, I can't even keep a stable connection to Yahoo!!

Advocate

 • 

1.4K Messages

11 years ago

Hello Michealm,

 

So being in DHCP disabled (or pseudo-bridge mode),  I presume you are using a firewall or controlling router device, correct?  One method to isolate the root cause of this issue would be to enable the SMC DHCP server and program the DNSs, connect a computer to one of the 4 LanPorts, then see if you get the same 50% ping loss on a consistent basis from the SMC DHCP connected computer. Before you do this aforementioned test, make sure you still have internet access via you firewall or controlling router device.

 

After you do the ping test mentioned above, if you do not the same 50%-ish ping test loss, this points to your firewall or controlling router (FCR) device interconnectivity and try the following:

1. find out what the FCR port specification speed is then log into the SMC Lan - Ports and disable auto-negotiate and set the speed to the spec value.

 

2. make absolutely sure you FCR's staticIP network configuration has the standard Comcast DNSs programmed within.

3. If you have a FCR that provides load balancing, try disabling this

 

Lastly, contact your Comcast technical support rep and ask him to validate you WAN staticIP DNSs are programmed with the lastest.

 

Hope any of the above helps you out because it has helped me.