Contributor
•
3 Messages
Outlook access to email.comcast.net from AT&T Network
Using Outlook, I am currently unable to access mail.comcast.net or pop3.comcast.net while on the AT&T network. I can access smtp.comcast.net and send email fine, but the receive function errors out saying that it can not find the mail.comcast.net server. All functions work when I am on the Comcast (Xfinity) network.
I also can send/ receive my AT&T email on this computer.
_xyzzy_
Expert
•
15K Messages
5 years ago
Should work since you are only using your att service as a pipe to the internet. I use another email service just fine from my Thunderbird client (not comcast's though). Does comcast have any restrictions on their POP/IMAP servers accessing them from outside their network? Or alternatively, after looking at this comcast page, how can mail.comcast.net work if they don't even list it as one of their servers? That page says imap.comcast.net is their IMAP server and pop3.comcast.net their POP3 server.
0
0
ahuberty
Contributor
•
3 Messages
5 years ago
Thanks for your response. Same result with pop3.comcast.net. I found
that previously I had to us the IP address instead of the mail.comcast.net
which led me to believe that AT&T couldn't resolve the name, but if the ping
resolved it, then I'm at a loss. I was able to come up with the IPV4 IP
address by using ping -4 mail.comcast.net. I'll give that address a try and
see if it works. My DNS settings are set up for auto-configure. I'm
wondering if IPV4 vs. IPV6 comes into play at all. I'm grasping at straws.
I'm frustrated when things that were working just quit with no reason
stated. Oh well, who isn't..
Al in Michigan
0
0
_xyzzy_
Expert
•
15K Messages
5 years ago
Couldn't hurt to try turning off IPv6 in the gateway.
Also I suggest trying DNS settings like OpenDNS (208.67.222.222, 208.67.220.220) or google DNS (8.8.8.8, 8.8.4.4).
0
0
ahuberty
Contributor
•
3 Messages
5 years ago
ping -4 mail.comcast.net as the incoming server. That generated a
"certificate warning" when I did a send/receive, but I was able to receive
my email. It will take someone more knowledgeable than I to determine
exactly what the problem is. Basically Comcast changed the IP address of
the server and since I had the problem before with name resolution, I was
using the hard IP address so Outlook couldn't find it. There is something
going on inside the AT&T network from what I can tell, but I have no clue
what it is. I don't think it's my DNS configuration since the "ping" was
able to resolve the mail.comcast.net. Of course the ping failed for
security reasons, but at least it gave me the IP address.
0
0