About mweasner

ftp still hit-n-miss on 25 April and 26 April. ... View more

Those 60s and 30s settings worked fine until mid-December 2018. ... View more

Both client apps I use on the desktop do have timeout settings.  They were 60 seconds on one and 30 seconds on the other.  I have set both to 120 seconds.  Will see what happens. ... View more

My last ftp session was on Thursday, 18 April, beginning at 0725 MST.  Over the next 30 minutes I experienced ftp failures.  If I could get logged in to my server I could not get a directory listing.  If I could get a directory listing I could not upload a 10 KB text file.  It took multiple reconnections before I was successful.  So, yes, the problem still seems to be occurring. ... View more

Sorry for the delay in updating on the ftp issue.  After changing the DNS setting on the modem on Thursday, 21 March, it appeared that the ftp connection issue might have been resolved, at least for the Ethernet connected computers.  I made several ftp connections on Thursday and Friday from multiple computers with different OS versions and they connected without any problems.  Saturday morning, 23 March, I connected OK from one computer, however Saturday afternoon the connection from the same computer to the same ftp server failed.  Over these same three days Wi-Fi connected handheld devices were hit-and-miss with ftp connections whether on 2 GHz or 5 GHz.  The Wi-Fi handheld devices did connect via the AT&T LTE network however using the same software.   Sunday morning, 24 March, I cycled the power on the modem.  Computer connections via Ethernet were OK. Wi-Fi ftp connection worked from one device but failed on another device.  Monday morning, an Ethernet computer connected OK, but the same computer and a Wi-Fi device failed to connect to the ftp server that evening.     Tuesday morning, 26 March, at 0650 MST: I tested the ftp connection from one of the Ethernet connected computers; it worked.  However at 0705 MST the same connection failed.  I don't have any way to detect packet loss but did run a traceroute from the computer that failed to connect.  It failed to complete the trace: traceroute to www.weasner.com (206.188.193.186), 64 hops max, 72 byte packets 1 192.168.42.1 (192.168.42.1) 0.469 ms 0.232 ms 0.197 ms 2 100.67.112.193 (100.67.112.193) 0.424 ms 0.357 ms 0.256 ms 3 host1743300129217.direcway.com (174.33.217.129) 590.670 ms 566.960 ms 589.957 ms 4 host17433004221.direcway.com (174.33.221.4) 599.858 ms 637.780 ms 599.531 ms 5 ae3-651.bar2.sanfrancisco1.level3.net (4.14.107.209) 619.946 ms 597.855 ms 609.841 ms 6 * * * 7 sjo-b21-link.telia.net (80.239.195.62) 602.075 ms 627.716 ms 639.845 ms 8 defensenet-ic-302038-sjo-b21.c.telia.net (62.115.35.134) 609.946 ms 637.273 ms 589.843 ms 9 * * * 10 107.162.79.2 (107.162.79.2) 590.229 ms 596.803 ms 609.822 ms 11 * * *   I realize (like most technical people) that Internet routing is a mess.  But it does seem strange that the routing via the HughesNet network connection is hit-n-miss but that it always works via the AT&T LTE network.  At this point I'm not certain how to proceed. ... View more

Update after 24 hours with the different DNS and bandwidth settings.  Ethernet connected computers have always connected to the ftp server on multiple tries over the past 24 hours.  Wi-Fi connected devices had success once but have failed multiple times over the past 24 hours.  I have not yet rebooted the modem; waiting to see if the Ethernet connected computers (which are primary for ftp access) lose their ftp access. Have also noticed that loading of web pages in the web browser is much snappier than it has been for weeks. Not ready to declare success yet but looking more hopeful, thanks to the settings changes that the Home Technical Support rep made yesterday. ... View more

Per a private message from Jay, I called HughesNet this morning. I had to re-explain the issue to the Customer Service rep even though she could see the referenced case# that Jay gave me with instructions for me to talk to the Home Technical Support team. That seemed to be a waste of my and her time. Since I was directed to call HN and use the case# to be connected to the Home Technical Support Team, she should have immediately connected me to that department. It took 10 minutes before she connected me to that department. Once I got to Brett at Home Technical Support I had to re-explain the issues.  Unfortunately he could not do much since it wasn't his job (he is a contractor for HughesNet).  However, he did have me do some things that no one else at HughesNet had ever suggested.  He had me change the modem/router DNS settings, the Wi-Fi bandwidth, and update the time settings. Now to see if these changes solved the issues I've been experiencing since 15 December 2018.  Stay tuned... ... View more

Friday, 15 March 2019, at 0720 MST, ftp was totally dead.  I rebooted the modem 0723 MST.  But when the modem came back online it had lots of errors, mostly related to Web Acceleration (which had been ON before the reboot).  The Internet connection (all protocols) was dead.  I reset the Web Acceleration MBX but that didn't help; still no Internet connection at all.  I then disabled Web Acceleration.  The Internet connection returned.  AND ftp worked this time.  I assume that rebooting the modem is not supposed to kill Internet connectivity.  Perhaps this morning's episode is another clue in the long list of clues about why my HughesNet connection is so flakey.  Replacing the modem in January didn't help.  Disabling web acceleration in the past didn't help with the ftp connections, so I doubt it has any bearing on why ftp worked after disabling it following this morning's flawed reboot.  And so the saga continues... ... View more

Ah, CenturyLink.  We had their DSL.  But after a few years their service deteriorated too.  It got to the point that about once a month I had to call them about the download speed dropping to 0.3 Mbps (from its normal of 1.2 Mbps).  Their solution was to reboot a server on their end.  That solved the problem for about 30 days, then I had to call them again and they had to reboot their server again.  After a few months I got tired of dealing with the hassle and switched to HughesNet.  That was in 2013.  All was well until December 2018.  Now it seems that HughesNet might be suffering from the same type of service deterioration (for whatever reason).  Perhaps the solution needs to be the same: reboot some server on their end every month.  Worked for CenturyLink.  Worked for me until I got tired of it. ... View more

A thought has occurred to me about a possible cause for the deterioration of my HughesNet service.  When the technician came in January 2019  to troubleshoot the ftp issue he said he saw high error rates.  He replaced the modem and the dish electronics.  Of course, that hasn't solved the issue.  What was not replaced was the coax cable run from the dish to the modem.  About 40 feet of that cable has been exposed to the harsh weather here (Sun, hail) and possibly birds pecking at it since the system was installed in 2013.  The cable just lays on the Sun-facing side of the roof and runs down the east side of the house.  It was not installed in a conduit to protect it.  If the cable shield has been damaged (hail, birds) perhaps that could be the cause of all the ftp, http, https, and imap issues I've been seeing.  Comments anyone? ... View more

Thank you for the update.  It is still hit-n-miss with multiple apps, multiple computers, multiple handheld devices, and with and without passive enabled.  I've tried all that since the problem first started in December 2018.  Prior to December 2018 there were NO ftp access issues.  The only way I can get consistent ftp access is via the AT&T LTE network on my handheld devices.  I do continue to see what looks like worsening IMAP and http download speeds.  Sometimes the various speed test sites and iOS apps fail to even start due to horrendous (0 Mbps) download speeds.  Perhaps the HughesNet system has overreached its user capacity. ... View more

Thank you. Unfortunately there has been no obvious pattern to the hits and misses.  Most of my ftp connection attempts occur 0730-0750 MST and 1800-2100 MST.  I see successes and failures during these times as well as at other times during the day and night.  It just seems so odd that these issues started in December 2018 with no additions or deletions in the devices connected to my local network. ... View more

Here's more information on this failed ftp situation with HughesNet. As has been the case since December of last year, ftp connections continue to be hit and miss from multiple computers and handheld devices.  Many times the initial connection to the ftp server will fail, only to work a few minutes or hours later. Other times the connection will work, only to fail a few minutes later. It has even failed in the middle of uploading a small TEXT or JPEG file (10-200 KB) to the ftp server. To make matters even worse, other connections are becoming unreliable.  I am seeing increasing random failures getting email (IMAP), web pages (HTTP), and even software updates (OS, applications). The frustrations continue to build...     ... View more

ftp connections are still hit and miss.  Supposedly HughesNet was going to try an alternate beam but I never received a confirmation of that. ... View more

ftp problems via HughesNet continue hit and miss.  Saturday night (MST) could not connect to my ftp server through HughesNet, but could using the AT&T cell network.  Sunday morning (MST) an ftp connection was made but then it dropped.  I reconnected and managed to get the small HTML and JPEG files uploaded.  I'm on the top tier service for residential.  So whatever problem that started on 15 December 2018 is continuing. ... View more

Thanks!  I've had fun over the many years.   As to the ftp issue, still can't declare success.  Didn't work Wednesday night.  Two hours later still didn't work.  Two minutes after that it did work.  Worked this morning too.  So still hit and miss. ... View more

Thanks.  The URL is www.weasner.com.     I'm not ready to declare ftp success yet but yesterday morning, last night, and this morning ftp worked fine.  That's the longest period of time since this problem started on 15 December 2018 without ftp connection issues.  (And no, the Mac and iOS updates that Apple released on Tuesday do not factor in.  I have not yet done any of those updates.) ... View more

Could be latency.  BUT I never had this problem until 15 December 2018.  I've been on HughesNet since 2013 and Gen5 since 2017.  And I still see about 700ms pings, which has been consistent since 2013. ... View more

I use several ftp apps.  On the Macs I use CaptainFTP and Cyberduck.  On the iPhone and iPad I use EasyFTP Pro.  On one of the Macs I also use a CURL ftp terminal command at times to upload a single char file.  Sometimes these all work fine.  Other times they all fail.  Sometimes one will work when the others fail.  But there is no consistency as to what works when.  There seems to be no pattern with the failures.  Time of day doesn't matter.  Happens with multiple computers and handheld devices.  BUT doesn't happen when I use the AT&T LTE cell network from the handheld devices. ... View more

ftp is still hit-and-miss via HughesNet.  Had a lot of problems Monday morning.  Would get a connection to the ftp server and a directory listing.  Uploaded some small files (HTML and JPEG) successfully.  Then a few seconds later upload aborted mid-upload.  Had a lot of problems getting reconnected.  Had to give up.   This morning connected to the ftp server and uploaded several small files.  No issues.   Since my modem and dish electronics have been replaced (and my local devices rebooted many times since 15 December 2018), maybe the Gateway needs to be rebooted. ... View more

I'm on the same gateway.  The plot thickens... ... View more

Again, I spoke too soon about ftp working.  It worked all day every time I tried after the tech left.  Then worked once at night.  Then 3 hours later it stopped working.  Will see what happens on Wednesday.  Looks like I may have to consider Viasat (formerly Exede). ... View more

HughesNet technician came today.  He was awesome (even though he didn't know what ftp was).  He saw errors on both the modem AND the dish.  He replaced both and now my ftp access is working again.  (Hope I'm not speaking too soon again.)  For what it is worth, this is my 4th Gen5 modem.  The previous ones were each replaced for different problems. ... View more

I called back to the Tier 4 advanced support Monday morning.  The "advanced" support person I spoke with did NOT understand what ftp is.  I had to explain it to him.  He then reported that speed was OK and explained to me about the number of device limitations with their service.  When I asked where that was documented for customers, he could not give me any specifics other than to check the HN legal web pages.  He did say that he was seeing a large number of packet errors (which do not show up in the modem web page on my end).  He decided that it would be best to send a technician out to physically check the system. That tech should come on Wednesday, 9 January.  I hope that technician understands about ftp... ... View more

Today (Saturday) I got a phone call from HughesNet Technical Support.  Unfortunately, their call was to be made to me on a business day.  Unfortunately, the call was flagged as a "Telemarketer" by AT&T, so I didn't answer it.  The caller did leave a voicemail message with a callback number and pin to use.  However, the pin was not valid.  I also tried calling the phone number that was used by the caller.  It was disconnected after two rings.  Too bad that HughesNet doesn't use a valid caller ID when returning phone calls.  Now I have to call Tech Support on Monday and probably start all over again. ... View more

I spoke too soon about the ftp issue being fixed.  ftp became totally dead last week.  I contacted the host provider; no issues on their end.  I called HughesNet Tech Support this morning.  The rep tried a few things, but nothing worked.  Still no ftp access via HughesNet.  Other Internet protocols (http, https, LDAP, IMAP, DNS) still work fine.  She has elevated the call to their advanced technical suppport.  Unfortunately, she said it could be 2-3 days before they reach out to me. ... View more

That's true.  Anywhere along the line that HN uses which could be different than AT&T or a cable provider.  But a search for "ftp" in this HN user forum does show a lot of problem reports with failed ftp connections over the years.  Might be a pattern there...   I do have to wonder about HN for business users.  For their modem/router to not have a configuration backup/restore capability should be a killer for businesses who require reliable services.  I reported this concern directly to HughesNet over a year ago.  Still nothing. ... View more

ftp working again.  I tried multiple times every day since 15 December.   It wasn't until 26 December that I had reliable connections.  Wonder what was wrong.  Certainly not my ftp server as it was accessible via AT&T LTE and another user who was on a cable Internet system.  The only culprit could have been HughesNet or the HN Gen5 modem/router. ... View more

HN Gen5 modem/router was rebooted Saturday, 22 Dec.  Problem is still occurring.  ftp connections are unreliable, but only through the HN modem.  ftp via a cell network connection work fine.  Definitely a HughesNet problem. ... View more