I use Thunderbird to fetch my mail from six Microsoft accounts (Outlook & Hotmail). Last night I kept getting a "can't connect to pop3 server" error and no mail. No problem connecting to my webmail interfaces or any other site by browser. I rebooted my modem which had been up for 33+ days and the problem resolved. I got my mail.
This morning (8½ hours after reboot of modem) I got the same error and no mail. I tried several different computers on my network with the same result. I connected my phone to a computer using Vz as internet provider and Thunderbird got my mail. No problem. That seemed to confirm the problem is with Hughesnet.
I rebooted the modem again and was able to get mail through my Hughes connection again. Next time it happens I'll screenshot the exact error message but it definitely has to be a conflict between Hughes and M$. This has never happened before. Any ideas?
@GWwrote:Funny, my notifications started up again beginning with your post.
It must be my charm. 😛
I started having issues 5 days ago. My Windows 10 machine using Windows Mail won't sync with Hughes email or Gmail.
Good morning infinitytec,
Thanks for posting. Since both the HughesNet and Gmail accounts are having difficulty with Windows Mail, sounds like Windows Mail isn't playing nicely for whatever reason. Have you tried removing and re-adding the account to see if that makes a difference?
Thanks for getting back to me!
I looked at some support for some other software I use and it appears it is actually a problem caused in an update to that. My phone still gets emails (Gmail and Hughes), as does Thunderbird, so it looks like I am in good shape as soon as I roll back the update. It's not a problem with HN after all.
Thanks again!
You're welcome, glad you figured it out. Thanks for coming back to let the rest of us know what happened!
Interesting. Mine shows up as the router model...
I've personally not had any issues with my MSN mail service, though I'm not presently using Thunderbird. When I did use Thunderbird, it was only for a short time and I only used it for a second Hughes email I set up, but I eventually deleted the email address and uninstalled Thunderbird.
I'm not very versed on email issues, nor the setup of such (the email, not the issues 😛 ), and probably the only things I would have suggested would have been power cycling/restarting the modem and/or trying an alternate DNS server, like Google's, like Amanda mentioned.
Glad it's working again, and I hope it stays that way. 🙂
@GabeUwrote:I've personally not had any issues with my MSN mail service, though I'm not presently using Thunderbird. When I did use Thunderbird, it was only for a short time and I only used it for a second Hughes email I set up, but I eventually deleted the email address and uninstalled Thunderbird.
I'm not very versed on email issues, nor the setup of such (the email, not the issues 😛 ), and probably the only things I would have suggested would have been power cycling/restarting the modem and/or trying an alternate DNS server, like Google's, like Amanda mentioned.
Glad it's working again, and I hope it stays that way. 🙂
Thanks Gabe. I've been using Thunderbird since I quit using Outlook and Outlook Express a very long time ago. It's a great program.
@GW wrote:I use Thunderbird to fetch my mail from six Microsoft accounts (Outlook & Hotmail). Last night I kept getting a "can't connect to pop3 server" error and no mail. No problem connecting to my webmail interfaces or any other site by browser. I rebooted my modem which had been up for 33+ days and the problem resolved. I got my mail.
This morning (8½ hours after reboot of modem) I got the same error and no mail. I tried several different computers on my network with the same result. I connected my phone to a computer using Vz as internet provider and Thunderbird got my mail. No problem. That seemed to confirm the problem is with Hughesnet.
I rebooted the modem again and was able to get mail through my Hughes connection again. Next time it happens I'll screenshot the exact error message but it definitely has to be a conflict between Hughes and M$. This has never happened before. Any ideas?
This just happened again. Reboot fixed it.
Might be the sporadic TLS/SSL error returning. I've been seeing it on J2SDO068.
Rebooting might only seem like it's correcting it since it clears out the DNS, but the issue is inherent in the way packets are actually processed. It happens almost randomly, with no rhyme or reason, but it does seem to be aggravated by evening congestion.
The HughesNet Community is here for you
to find answers and ask fellow HughesNet
subscribers for help. This is a great
opportunity to discuss and share your
expertise to enhance your HughesNet
experience and that of fellow subscribers.
Visit the About the Community board for
information on how to get started with using
this resource.