- HughesNet Community
- :
- About arceus213
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About arceus213
since
09-02-2015
07-14-2019
arceus213
Sophomore
32
Posts
3
Kudos
1
Solution
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-14-2019
11:52 PM
|
07-13-2019
08:27 PM
Okay, the status code changed to 11.2.1, I was concerned that the 2.2.1 status code was permanent.
... View more
07-13-2019
08:22 PM
Thought I might show this since this started happening a little bit ago. I did check Tucson's location, and it is raining currently. Does this status code go away, or no? Also, tried unplugging the modem and plugging it in, and it didn't work. Edit: Replaced the photo to comment out the SANs.
... View more
Labels:
07-16-2018
07:38 PM
@JorgeYeah. I looked at the weather there and I do see rain around there. Also, since Saturday, I haven't experienced the 12.7.1 error at all. It's like that the error magically went away. And Dad didn't even have to cut trees at all.
... View more
07-12-2018
11:51 PM
@MarkJFineI didn't really hear him say much about the trees being the cause. If I'm not mistaken, he asked after he was done when the problems started occuring. And I told him when the rain came by Tuesday morning. He then thought that the storms were the cause of our problems. Still, once Dad gets better, he plans to cut at least two trees. Hopefully by then, we'll stop getting the 12.7.1 status code. Thought I'd show the current hour history. The good news is that we're not having a lot of problems like we did early tonight, although that could change probably in the future maybe.
... View more
07-12-2018
10:35 PM
I was going to post an update tomorrow. However, the fact that we're having more problems than yesterday and the day before is making me post this now. Tech came over Monday, and replaced the transponder on the satellite as well as realigned the satellite. I was still getting the 12.7.1 error before today though, but it wasn't as bad as tonight. Tonight is really bad though, as we're getting more errors on the uplink than usual. I did check Tucson, Arizona's weather and I did see rain where the gateway is. Whether or not these errors are being caused by rain or not remains to be seen. The second screenshot is the most recent current hour history screenshot. I've seen that while the system light is off on the modem, the transmit light, instead of blinking normally, will flash on and off repeatably. Tonight, I've also seen that the transmit light and receive light won't blink at all when the system light is off as well, although that may or may not have been caused by rain at the gateway. @MarkJFineDo you think part of the problems we're still having are still being caused by trees? Dad was planning to cut at least two of them when he gets better, as he's still recovering from injuries, which I really won't go into much detail at all. P.S. The main good thing about the tech visit is that I've seen the signal go up over 110 more commonly. Though right now, it's currently under that.
... View more
07-06-2018
11:26 AM
@MarkJFineThe roof is fine. There's no damage with it whatsoever. The latter part of what you said is a possibility though. I have to disagree with what you're saying about the trees though. The problem that we're having literally started happening this week after rain came by. It didn't occur at all last week. Had trees been an issue, we would have had issues before this week. That's why I don't think trees are what's causing the issue. I literally think that the rain that came by Tuesday Morning is what's causing the problem that we're having. And on top of that, I already said that the trees aren't even near the satellite at all. And finally, my parents (yes, I'm the son that's posting this issue), also agree that trees aren't what's causing the issue here. I guess I could show what's hopefully a better picture of the satellite: And finally, I should post the current state code history: Ignore the 11.2.2 error. That's when rain this morning recently came by. And also ignore the recent 11.3.1 state code that happened again, as that ended around the time the 11.2.2 error ended. And yes, as you can see, I got more 12.7.1 errors.
... View more
07-05-2018
09:06 AM
I guess I should show where the satellite is. The satellite is on the Garage. And here's the thing. When the installer installed it there back in 2013, he said that we had a clear line of view to the gateway. So unless the trees are blocking it (which they aren't even near the satellite, unless I'm wrong), we don't see trees being the cause. It's however unusual that we started seeing the errors after the rain that came by early Tuesday morning.
... View more
07-04-2018
11:17 AM
Well, I'm here to report another status code I got (it was only ten seconds): Yup, I got 11.3.1, and that was when the signal got extremely low it seems.
... View more
07-04-2018
10:27 AM
@MarkJFineI see. Also I would like to report another status code that I'm getting. Yes, as you can see, I'm currently getting the 12.1.12 status code, or I was. Now it's back to being normal again. And while I'm at it, I might as well show the current hour history, hourly history, and current state code monitor:
... View more
07-04-2018
01:11 AM
@GabeU I'm on the EchoStar-XVII satellite. The Beam ID is 17. I also should should show the hourly history. I haven't had any problems since 6 hours ago it seems. The diagnostic code currently is 0000-0000-0000-0005.
... View more
07-03-2018
07:48 PM
Since after rain came in our area early this morning, we're commonly getting the 12.7.1 error message. I tried rebooting the modem, as well as unplugging the modem and plugging it in, but the error still commonly appears. This is the current hour history. As you can see, the Uplink is having issues. Whenever the uplink is having issues, the 12.7.1 status code appears. This is the hourly history. The Xs are when I was sleeping, so the 12.7.1 error must have happened when I was sleeping. As you can see in the System State Code monitor, the 12.7.1 error message is happening commonly. And this is the diagnostic code history. The current diagnostic code is 0000-0000-0000-0005. However there are two diagnostic codes that occured before I got that code. As you can see. the 12.7.1 error message is causing problems for us. If someone can help us with this, that would be appreciated. Edit: I forgot to say. The current satellite signal is at 104-106.
... View more
Labels:
12-28-2017
04:28 AM
https://testmy.net/db/7VtfuD91r Just an update, I'm not really experiencing a problem with the upload speeds at the moment. I'm not having problems with uploading to sites like Youtube for example. As you can see in the current hour history, My uplink is doing ok right now. If I have any more issues with it and the upload speeds I'll be sure to update you all later.
... View more
12-27-2017
09:44 PM
Just did a recent connectivity test and it showed 50% packet loss. I did another test after that, and it showed extremely high ping. Again, I'm not sure if this matters since it's 9:43PM where we live, but I'm putting both screenshots here in case it does matter.
... View more
12-27-2017
08:43 PM
I'm posting the most recent currently hourly history screenshot, the uplink is still giving out problems. And I'm getting the 12.1.12 error code again currently.
... View more
12-27-2017
08:18 PM
So we're having an issue, where we're unable to upload anything due to the uplink giving out errors, we're getting the 12.1.12 error code, and finally, we're getting multiple diagnostic codes. As you can see, the 12.1.12 error appeared, and the signal strength is good, so we shouldn't be getting this error. As you can see in the above screenshot, we got 5 Xs in the uplink, likely due to the 12.1.12 error. Even if the error didn't appear, we're still having trouble uploading to sites like youtube and mega due to the uplink errors. I did a connectivity test today, and it reported 60% packet loss. This is the hourly history, for some reason, we're also having problems with the DNS Acceleration[N]. Finally, This is the various diagnostic codes we are getting, and yes the recent diagnostic code currently is 0000-0000-0400-0041 . If someone could help us with this, this would be appreciated. Edit: I should show my testmy upload test: https://testmy.net/db/meJz6p3AZ. I don't know if this matters or not since it's 8:36 PM where we live, but I'm doing it anyways. Update: I've decided to do another upload test, this one having the computer directly connected to the modem: https://testmy.net/db/oDWLUyJG8. Again, don't know if this matters or not, since it's 10:44PM currently where we live, but I decided to put it here anyway.
... View more
Labels:
08-21-2017
09:05 AM
Actually, it seems the Receive Data updated. So does this mean, we don't have to worry about the Unreturned equipment charge now?
... View more
08-20-2017
10:46 PM
1 Kudo
@GabeU wrote: @arceus213 wrote: Tracking number: 1Z6W37599008376937 RMA Number: 302463439 So we have another problem similar to this thread: community.hughesnet.com/t5/myAccount-and-Billing/Received-an-email-about-RMA-equipment-not-received/td-p/79067 where Hughes is emailing us saying they haven't received the Modem, even though the tracking number shows that it has delivered to you guys. The main difference is that we didn't need to use packing tape because the UPS guy that delivered something to our house said that they had it, so we gave him the package. We understand that it hasn't been 5 days since you guys haven't processed the return, but we're starting to get worried because rmastatus hasn't updated still and we'll have to pay the unreturned equipment fee. If you can get this matter solved, that would be helpful. I hope you know your UPS guy well enough to trust him. But, just for reference, you should make sure that anything you ship in the future you tape shut yourself before it leaves your eyes. Yeah, we'll have to remember to do that in the future from now on.
... View more
08-20-2017
06:34 PM
Tracking number: 1Z6W37599008376937 RMA Number: 302463439 So we have another problem similar to this thread: community.hughesnet.com/t5/myAccount-and-Billing/Received-an-email-about-RMA-equipment-not-received/td-p/79067 where Hughes is emailing us saying they haven't received the Modem, even though the tracking number shows that it has delivered to you guys. The main difference is that we didn't need to use packing tape because the UPS guy that delivered something to our house said that they had it, so we gave him the package. We understand that it hasn't been 5 days since you guys haven't processed the return, but we're starting to get worried because rmastatus hasn't updated still and we'll have to pay the unreturned equipment fee. If you can get this matter solved, that would be helpful.
... View more
Labels:
08-06-2017
06:32 PM
1 Kudo
@Aedan wrote: Good Morning all and thanks for posting! Gabe, there was a technical issue at your gateway that affected your beam on 7/28. Arceus213, your beam was affected by severe weather on 7/28 and 7/29. Arceus213, I also pulled up your account to troubleshoot. Your system is showing state code 13.2.2. Please verify that the LAN cable on one end is connected to the LAN port on the back of the modem and the other end to your computer. Thanks. Actually, the ethernet cable is connected from the Hughesnet HT1100 Modem to the Linksys E2500 wireless modem. Unfortunately, I wasn't at my home during the week, so there was no computer turned on at the time. Other than that, the internet is working fine right now.
... View more
07-28-2017
07:46 PM
So we had got the modem either Tuesday or Wednesday. All was fine most of the week, until the low signal issue happened again a little bit ago. The only difference is that it occured for almost an hour. This was the downlink state code before it changed to 11.2.1 as shown in this picture: The uplink state code was 12.2.1. I had reset the modem to see if the problem was solved, but it still occured as shown in this picture: The current diagnostic code is 0000-0000-0000-0027 . P.S. Forgot to say that the Modem's serial number is B3 0010751134 A3.
... View more
07-23-2017
12:23 AM
Will a technician come and replace the modem that we're currently currently using with a newer one? I just want to make sure on this.
... View more
07-22-2017
11:33 PM
Unfortunately, I didn't write down the state code at the time. I can however, show the state code monitor in the following pictures: Nevermind the 30.2.2 state code. The reason it's there is because I have problems downloading from sites such as Mediafire when web acceleration is enabled, so I keep it disabled. And the outage wasn't too long, although I forgot how much time it was approximately for. Currently the signal is back to normal as shown in this picture: This is the current association status (mine didn't have J1 or J2): Finally, the diagnostic code changed, it is now 0000-0000-0216-3842, in case you wanted to know.
... View more
07-22-2017
10:14 PM
Serial Number: B1-0005494030-A4 So we have another problem where the signal goes down very low. This has happened two days this week, during the night time hours. It is clear outside currently. Right now, I'm able to access the internet, but the signal could go low again. The current diagnostic code is 0000-0000-0000-0027.
... View more
Labels:
Latest Tags
No tags yet
