- HughesNet Community
- :
- About MarkJFine
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About MarkJFine
since
10-29-2012
4 hours ago
MarkJFine
Associate Professor
3006
Posts
1957
Kudos
71
Solutions
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
4 hours ago
|
yesterday
I'm no where near my old 360, but double check the settings on your X. If the UPnP setting is active, consider disabling it on the XBox as well as in the modem's wifi settings. For some reason (likely the lag) it doesn't play well over satellite.
... View more
a week ago
2 Kudos
It could be that the DNS corruption already propagated to whatever you're trying to reach Amazon on. the recommended procedure would then be to: 1. Turn off all devices that are using the internet via the modem in question. 2. Remove power from the modem. 3. Wait 60 seconds, then apply power to the modem again. 4. Wait 5 minutes until the modem is fully activated with all lights on and turn on the devices you turned off in step 1, one by one. This will ensure that every device's cached DNS starts from scratch and can't be re-propagated.
... View more
a week ago
1 Kudo
Cached DNS entry to images-na.ssl-images-amazon.com may be corrupted. Try rebooting the modem and see if it fixes it.
... View more
2 weeks ago
2 Kudos
@CWM030 wrote: @GabeU @@Liz Its weird because I can unplug the modem, wait 30 sec and then plug it back in and everything is fine again without clearing the cache. But, that's precisely the procedure for clearing the modem's DNS cache. It's possible that instead of poor wifi there's a site or some application that's hitting the DNS too fast, and not waiting for it to respond in time before going on to something else. That will confuse it but is kind of a rare situation. I used to see it a lot with the 1100, but not with the 2000-series modem.
... View more
2 weeks ago
Is it the only device connected? Once the DNS is corrupted by any one device, it affects all of the devices connected to it.
... View more
2 weeks ago
1 Kudo
Usually this is a symptom of an erratic wifi connection that has corrupted the DNS, not a problem with HughesNet or the modem. You can solve most of the problem by moving your device closer to the modem or by using a LAN cable.
... View more
3 weeks ago
1 Kudo
Technically, an ethernet cable is going to always provide the widest bandwidth, therefore the greatest thruput, which will always seem faster. Wifi depends upon the protocol used: 802.11ac when using multiple 20MHz channels (up 80MHz wide) will approximate ethernet thruput, whereas 802.11a, b, g using a single channel will not. Data is data and neither uses more than the other, however a wider/faster path will always use data *faster* so people tend to think it's using more data.
... View more
05-13-2021
02:06 PM
One other thing I recently noticed on macOS: There's this process that periodically (and very inefficiently) synchs a lot of data at a 1-2 Mbps rate to your iCloud account. Seems to go on for a very long time, and I've seen it happen twice a day.
... View more
05-13-2021
12:57 PM
iOS and iPadOS updates seem to be monthly. App updates seem to be weekly, minimum.
... View more
04-30-2021
06:09 AM
1 Kudo
Looks like an SSL error, which may mean the DNS cache is corrupted, which happens time to time. Try rebooting the modem to clear the DNS cache. If that doesn't work, it may mean the corrupted DNS entry may have propagated to the device you're trying to reach Podtrac with. In order to fix that, you generally need to refresh your device in a manner that doesn't allow the corrupted entry to re-propagate over the LAN: 1. Turn your device(s) off. 2. Remove from the modem at the wall socket. 3. Wait 60 seconds and re-power the modem. 4. Wait another 60 seconds until the modem has fully rebooted and turn your devices back on.
... View more
04-27-2021
10:57 PM
@maratsade wrote: Enjoy New Jersey! Unfortunately it's not a pleasure trip.
... View more
04-27-2021
04:53 PM
1 Kudo
Needless to say, I get up real early and use Bonus time for all of it. Most of the time it goes pretty fast, at between 25 and 40Mbps. That said, I've been in NJ getting spoiled for the past 2 months. I think Fedora 34 comes out today...
... View more
04-27-2021
08:38 AM
1 Kudo
Good thing you don't develop. Xcode updates every time there's a macOS update, and it's now up to 12GB - and sometimes it fails the first time so it has to be re-downoaded - but that's another story. So there's this machine that would need 18GB, right there, and then another 6GB for my wife's machine = 24GB in one morning, and that's not even a game. I used to be able to capture the maOS updates in the system file structure (before macOS deleted it prior to install), copy it to a USB drive, then install it on my wife's computer. But Apple decided that wasn't safe and prevent you from file operations there anymore.
... View more
04-26-2021
07:22 PM
1 Kudo
I think what he meant was to just post the link to the summary page on TestMy where your results are listed, instead of copying and pasting them in a post here. Part of the issue is it's hard to read, and if the link is posted the admins can see all the tests run, not just the one sample.
... View more
04-26-2021
05:50 PM
1 Kudo
Nothing to fix. The 'limited' thing happens whenever you have anything different from 0% packet loss. In fact a plane going by or a bird circling the area can easily cause 10% packet loss, especially if it's sporadic. You would only see a problem when it goes over 25-30% because of the way redundant forward error checking protocols work. Bottom line: Given the average delay your stats look pretty acceptable. My guess is your speed issue is something else completely, so I would take @maratsade's advice and do some speed tests, if you're not out of data.
... View more
04-24-2021
07:49 AM
2 Kudos
It means the servers that run background applications for everyone are overloaded. Background applications are the things that create data, not necessarily what handles what you see at the user level - those would be front-end servers.
... View more
04-14-2021
08:12 AM
Rebooting resets the DNS cache, which sounds like may have been corrupted on the modem as well as the device having trouble downloading. The DNS information propagates across your entire LAN, but may have not yet corrupted the other devices that are working. In this case, you may want to remove power from the modem, then also reboot the device having trouble. Once the device is up, apply power to the modem again. The reson for this process is to prevent re-corrupting the device in question: The device will wait until the modem is restarted and will get a fresh DNS update once it is. However, if the device is restarted before the modem is turned off, it's just going to pull down the same corrupted DNS information.
... View more
04-13-2021
09:33 PM
Plus, you've run Linux before, so using commands in the terminal window should be second nature on a Mini. Virtually anything you can run in Linux, you can rebuild under Darwin (Mac kernel). You can even have a virtual Xserver running if you download XQuartz. And, if you install Homebrew, you can add all sorts of unix/Linux things that have already been rebuilt for Darwin. A good example is Pan, which has always been my newsreader under Linux, and now under Mac.
... View more
04-06-2021
04:36 PM
2 Kudos
Port 53 is used for DNS and it almost seems as if you are tryng to set up a server that may be accessible from outside your home. If that's the case, please understand that Residential installations cannot be accessed from outside your local LAN because the satellite network is protected behind a double-NAT. Only Business installations may be accessed this way. Disregard if you're merely trying to set something up that's accessed within your local LAN.
... View more
03-29-2021
10:37 AM
1 Kudo
Don't be sorry. Good catch.
... View more
03-22-2021
07:46 AM
1 Kudo
Clearly you haven't read everything, because: 1. Not all people have other options for internet access. 2. Not all people use the internet as a means for watching TV.
... View more
03-21-2021
03:11 PM
The 'signal strength' is really an inverse bit error rate on the data stream, which can vary by humidity. Any kind of water in the air at these frequencies will defract (diffuse?) the signal, making it more error prone, although you might not see those errors due to redundancy and forward error correction protocols. A real dry day (~10-20%) could cause a 'strength' of 125, whereas mild humidity (~40-50%) could drop it a bit lower. Both these instances could be bright, shiny days with no rain at all (which of course, would be above 90% humidity).
... View more
03-19-2021
08:19 AM
2 Kudos
Correct. HughesNet already uses an http (web) accelerator as well as a TCPIP accelerator for other protocols. They are already maximizing as much of the downlink channel as possible. Adding another accelerator on top of that won't be beneficial and may even inhibit the ones already in use.
... View more
03-17-2021
08:24 AM
@Landon_Robinson wrote: That is true that the distance will be further since neither I or the gateway are directly on the equator, I live somewhat north of the "45th Parallel", but still the round trip of 89,000 miles is going to be something around half a second, but going back to what I was talking about before... if I can ping my gateway at 0.4xx ms the problems should not be on my end. A ping is essentially a singular event and measures the round trip access time for that one event. Accessing a web site or streaming server just for one access may be several events, depending upon additional content (images, stylesheets, javascript, etc.) and/or secure authentication processes, which in iteself is a multi-access event due to handshaking. So more complex than a ping, and the latency effects are cumulative.
... View more
03-14-2021
03:48 PM
1 Kudo
Unfortunately speed has very little to do with buffering. Buffering is from latency, congestion, and how streaming servers deal with those factors from satellite internet providers (e.g., not very well)
... View more
03-12-2021
10:23 AM
...or not work at all because of it.
... View more
03-07-2021
10:03 AM
I've noticed this happen when the congestion is extrememly high. I assume what's happening is there is a 'heartbeat' connection to the web acceleration server that just times out. It then assumes it's unreachable and automatically disables it. Sometimes rebooting will get you on a better connection, but as you've seen that is not always the case. When the congestion is that high there's a possibility that you're already on the most reliable channel available.
... View more
02-23-2021
06:48 AM
Not necessarily a HughesNet caching issue (actually I don't think they cache at all), but the latency may be playing a part in the browser recognizing the page had changed. Killing the tab, opening a new one, then loading and optionally shift-refreshing the page should update the browser. Also, if your site is cached if it is behind a Content Delivery Network (CDN) like Cloudflare (more like a large network of caches). You may have to purge everything in the CDN's cache before doing the above. Sometimes I even have to purge when making changes to my .htaccess file, not just pages. I seem to go through this all the time regardless of what network I'm using.
... View more
