Forum Discussion
Thanks for the quick replies and ideas.
"I think when OP said modem they meant Panoramic gateway, which DOES have a firewall and NAT."
Yes, it is a Panoramic WiFi modem, CGM414X, and the previous model was CGM4141.
"That's assuming the PC having issues can connect via ethernet."
It was tried on a desktop PC running Linux and on a laptop running Windows 10, both using WiFi. The desktop is not close enough to try ethernet but the laptop could.
The firewall was set to minimal while this was happening, and I just tried the custom setting of disabled and it is the same. All of Thunderbird, Claws Mail, and Vivaldi browser's builtin client were previously working fine and the settings had not been changed: IMAP port 993, SMTP port 465, using SSL. All of the Yahoo, GMail and Vivaldi mail accounts use the same ports and SSL, but only Yahoo has the problem, and only on this WiFi network. The error is always a timeout connecting to imap.mail.yahoo.com
Edit: Just tried with the laptop plugged into the modem via ethernet, same thing timing out connecting to Yahoo while GMail still works.
With a new modem, you get a different IP address. Yahoo may actually be blocking your new address, go to www.whatismyip.com. get your new WAN IP, and contact Yahoo and ensure they don't have a block on it.
Also, you can do a ping to imap.mail.yahoo.com as well as a tracert imap.mail.yahoo.com
I verified both respond to ping and tracert, and was able to tun both without issue. The tracert should give you an idea where the failure is,
5 16 ms 14 ms 14 ms ashbbprj02-ae2.0.rd.as.cox.net [68.1.4.139]
6 15 ms 14 ms 12 ms 68.105.30.110
7 20 ms 20 ms 20 ms ae-0.pat2.nyc.yahoo.com [209.191.64.21]
8 34 ms 34 ms 33 ms ae-1.pat2.bfw.yahoo.com [209.191.64.165]
9 29 ms 30 ms 29 ms unknown.yahoo.com [74.6.227.47]
10 49 ms 57 ms 40 ms et-11-1-1.clr2-a-gdc.bf1.yahoo.com [98.137.192.185]
11 33 ms 32 ms 31 ms lo0.fab3-2-gdc.bf1.yahoo.com [74.6.123.226]
12 29 ms 31 ms 28 ms lo0.usw2-1-lbc.bf1.yahoo.com [98.137.192.177]
13 30 ms 32 ms 31 ms jimap400-3.mail.vip.bf1.yahoo.com [67.195.176.151]
- JeanneO2 years agoNew Contributor
Thanks, Darkatt. I recall that around the beginning of the year the WAN IP had changed, but none of our software or devices was affected. I've already tried some pings but not a tracert. Pinging www.yahoo.com was successful but pinging imap.mail.yahoo.com returned the message "Destination host unreachable"
I will check later what the new WAN IP is and compare a tracert with yours
- WiderMouthOpen2 years agoEsteemed Contributor II
Pinging www.yahoo.com was successful but pinging imap.mail.yahoo.com returned the message "Destination host unreachable"
Can you paste the whole thing? What IP did it resolve to? Here is mine for comparison.
Pinging jimapinternal.imap.mail.g03.yahoodns.net [67.195.176.151] with 32 bytes of data:
Reply from 67.195.176.151: bytes=32 time=21ms TTL=54
Reply from 67.195.176.151: bytes=32 time=20ms TTL=53
Reply from 67.195.176.151: bytes=32 time=21ms TTL=54
Reply from 67.195.176.151: bytes=32 time=21ms TTL=53Ping statistics for 67.195.176.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 21ms, Average = 20msMaybe your DNS is not working correctly. If you get a different IP try changing to google DNS (8.8.8.8/8.8.4.4) or Cloudflare(1.1.1.1). If you need help setting up static DNS on one PC, let me know what Linux distro. you have. Here are some instructions for Windows 10.
- Bruce2 years agoHonored Contributor III
You'd assume the Store would reset these devices to factory defaults. I wouldn't think a Cox DNS wouldn't have an entry for imap.yahoo. Maybe.
Related Content
- 3 months ago
- 2 years ago
- 10 years ago