Hughesnet Community

Repeated uplink outages

cancel
Showing results for 
Search instead for 
Did you mean: 
wade_bear
Sophomore

Repeated uplink outages

This is our current hour history today:

errors1-17-18.pngSomebody please help.  I can't stay on line.

13 REPLIES 13
wade_bear
Sophomore

Oh, I guess I should mention... We brushed the snow off the dish and we have clear skys.  This has also been happening on a regular basis, but usually only in the evening hours between 5:30 and 11:30 PM Central time.

GabeU
Distinguished Professor IV

@wade_bear

 

A couple of things to try.  If you have the modem plugged into a power strip or surge protector please plug it directly into an outlet to see if this helps.  Power strips and surge protectors can cause issues with the power throughput.  Also, make sure that the plug going into the back of the modem is not loose.  Please be careful with it, as it's delicate, but just make sure that it's in all the way and not loose.  Lastly, please make sure that the coax connector at the back of the modem is finger tight.  It doesn't need to be any tighter than this, but it shouldn't be loose.  

 

If you don't already, please be sure to leave the modem plugged in so that the reps can run remote diagnostics on your HughesNet equipment if they deem it necessary.  

 

The reps are on M-F from approximately 8AM to 5PM EST, though it may take them a day or two to reply.  I don't even know why I'm telling you this part.  You've been on the HughesNet Community quite a bit longer than I have and I'm sure you already know that.  😛

 

I'll tag Liz and Amanda so that they will be sure to see your post.  

 

@Liz

@Amanda

Hi wade_bear,

 

Thanks for posting and sharing the screenshot. Please follow Gabe's instructions, in the meantime I'm running remote diagnostics on your site. I'll post back once I have news or questions for you.

 

Your cooperation, patience, and understanding are much appreciated.

 

If you have a tech or billing question and need help, please start a new thread in the appropriate board. Unsolicited Private Messages may not get replies.

Slow performance? Click me!

The situation is a little bit better today, but we're still having problems.  Here's a screenshot from about 9 PM on the 18th:

 

errors 1-18-18.png

Hi wade_bear,

 

Thanks for the update. I've escalated your case to our engineers for their assistance, I'll post back once I have any news or additional instructions for you.

 

 

If you have a tech or billing question and need help, please start a new thread in the appropriate board. Unsolicited Private Messages may not get replies.

Slow performance? Click me!

Well, it was better, but now it's worse again.  My latest screenshot from a few minutes ago:

 

1-21-18 7:15 PM1-21-18 7:15 PM

And here are today's stats.  I'm including the 24 hour report as well:  These are from 3 PM Central time:

 

 errors 1-22-18.pngdaily errors 1-22-18.png

Hi wade_bear,

 

Thank you for the screenshots, these help. Engineering has some code pending to address this, once we find out when this has been rolled out, we'll let you know. Your cooperation, patience, and understanding are much appreciated.

 

 

If you have a tech or billing question and need help, please start a new thread in the appropriate board. Unsolicited Private Messages may not get replies.

Slow performance? Click me!

Now it's getting worse.  Our connection has been going out every few minutes since about 1 AM (while I was trying to use it).  At one point I just gave up and power cycled the modem because it had been out for over 10 minutes.hourly errors 1-29-18.png

Hi wade_bear,

 

Thank you for the update. As far I as I can see, there have been no reports that would indicate any outages or other occurrence that could cause this. I've inquired about your site with an engineer. I'll let you know once I hear back.

 

Your patience and understanding are much appreciated.

 

 

If you have a tech or billing question and need help, please start a new thread in the appropriate board. Unsolicited Private Messages may not get replies.

Slow performance? Click me!

So it occurred to me to check the router logs.  Could any of this have something to do with our problems?  I replace our actual ip address with (our ip):

 

Jan 29 23:27:18    DHCP request success (our ip)
Jan 29 23:27:03    Per-source ACK Flood Attack Detect (ip=54.86.67.11) Packet Dropped
Jan 29 23:27:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:26:18    DHCP request success (our ip)
Jan 29 23:26:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:25:18    DHCP request success (our ip)
Jan 29 23:25:03    Per-source ACK Flood Attack Detect (ip=54.86.67.11) Packet Dropped
Jan 29 23:25:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:24:18    DHCP request success (our ip)
Jan 29 23:24:03    Per-source ACK Flood Attack Detect (ip=64.233.180.188) Packet Dropped
Jan 29 23:24:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:23:18    DHCP request success (our ip)
Jan 29 23:23:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:23:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:22:18    DHCP request success (our ip)
Jan 29 23:22:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:22:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:21:18    DHCP request success (our ip)
Jan 29 23:21:03    Port Scan Attack Detect (ip=54.231.177.8) Packet Dropped
Jan 29 23:21:03    Per-source ACK Flood Attack Detect (ip=54.231.177.8) Packet Dropped
Jan 29 23:21:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:20:18    DHCP request success (our ip)
Jan 29 23:20:03    Per-source ACK Flood Attack Detect (ip=172.217.12.36) Packet Dropped
Jan 29 23:20:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:19:18    DHCP request success (our ip)
Jan 29 23:19:03    Per-source ACK Flood Attack Detect (ip=172.217.12.36) Packet Dropped
Jan 29 23:19:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:18:18    DHCP request success (our ip)
Jan 29 23:18:03    Per-source ACK Flood Attack Detect (ip=54.86.67.11) Packet Dropped
Jan 29 23:18:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:17:18    DHCP request success (our ip)
Jan 29 23:17:03    Per-source ACK Flood Attack Detect (ip=216.58.218.130) Packet Dropped
Jan 29 23:17:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:16:18    DHCP request success (our ip)
Jan 29 23:16:03    Per-source ACK Flood Attack Detect (ip=65.36.0.154) Packet Dropped
Jan 29 23:16:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:15:18    DHCP request success (our ip)
Jan 29 23:15:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:15:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:14:18    DHCP request success (our ip)
Jan 29 23:14:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:14:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:13:18    DHCP request success (our ip)
Jan 29 23:13:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:13:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:12:18    DHCP request success (our ip)
Jan 29 23:12:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:12:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:11:18    DHCP request success (our ip)
Jan 29 23:11:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:11:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:10:18    DHCP request success (our ip)
Jan 29 23:10:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:10:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:09:18    DHCP request success (our ip)
Jan 29 23:09:03    Per-source ACK Flood Attack Detect (ip=66.82.21.21) Packet Dropped
Jan 29 23:09:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:08:17    DHCP request success (our ip)
Jan 29 23:08:03    Per-source ACK Flood Attack Detect (ip=172.217.6.131) Packet Dropped
Jan 29 23:08:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:07:17    DHCP request success (our ip)
Jan 29 23:07:03    Per-source ACK Flood Attack Detect (ip=66.82.21.21) Packet Dropped
Jan 29 23:07:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:06:17    DHCP request success (our ip)
Jan 29 23:06:03    Per-source ACK Flood Attack Detect (ip=66.82.21.21) Packet Dropped
Jan 29 23:06:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:05:17    DHCP request success (our ip)
Jan 29 23:05:03    Per-source ACK Flood Attack Detect (ip=169.54.129.18) Packet Dropped
Jan 29 23:05:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:04:17    DHCP request success (our ip)
Jan 29 23:04:03    Per-source ACK Flood Attack Detect (ip=169.54.129.18) Packet Dropped
Jan 29 23:04:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:03:17    DHCP request success (our ip)
Jan 29 23:02:17    DHCP request success (our ip)
Jan 29 23:02:03    Per-source ACK Flood Attack Detect (ip=54.193.41.31) Packet Dropped
Jan 29 23:02:03    Whole System ACK Flood Attack from WAN Rule:Default deny
Jan 29 23:01:17    DHCP request success (our ip)
Jan 29 23:01:13    Remote management is disabled.
Jan 29 23:01:13    Anti-spoofing enabled.
Jan 29 23:01:13    Block WAN PING enabled.

Well things have definitely been better the last couple of days.  I just hope they stay that way. Smiley Frustrated

Good morning wade_bear,

 

That does sound good... I haven't heard back from engineering regarding that specifically, but once I do I'll let you know.

 

If you have a tech or billing question and need help, please start a new thread in the appropriate board. Unsolicited Private Messages may not get replies.

Slow performance? Click me!