jkovba
asked on
Comcast/Outlook Issue - The specified server was found, but there was no response...
I've been using Outlook 2003 without issue for more than 2 years now, and recently, I've lost the ability to send mail out through Comcast SMTP. I was using port 110 for inbound mail, and 25 for outbound. I called and found out that port 25 had been blocked on their end from me, and this is evidenced by the fact that I cannot telnet to their port 25; I don't get a response. I've been through the anti-virus, the SSL, the port, and any other settings I can think of, but I can still only send and not receive. There is a ton of documentation about this online, and I've been through most of what's relevant, but haven't found any fixes yet, so I am turning to the experts for help.
Last Comment
Change to port 587 for SMTP. Comcast is forcing users to make the switch as part of their poor scheme to thwart mailer trojans that default to using port 25 to send spam from infected customer hosts. Alternatively, and if you want to use SSL on SMTP, use port 465 (and enable SSL). Comcast is making the change but not notifying their customers (and apparently their 1st-level call reps are also not being educated regarding the change).
Go to http://tinyurl.com/5dswr9, click "Outlook", click "How to configure Outlook 2003 to use port 587 for sending e-mail".
Go to http://tinyurl.com/5dswr9, click "Outlook", click "How to configure Outlook 2003 to use port 587 for sending e-mail".
ASKER
I have tried these settings already, and they still do not permit me to send email through Comcast unfrotunately.
What does the error say in the progress dialog for the failed send operation?
ASKER
Here is the error message that is thrown:
(0x80042109) : 'Outlook is unable to connect to your outgoing (SMTP) e-mail server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'
(0x80042109) : 'Outlook is unable to connect to your outgoing (SMTP) e-mail server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'
You mentioned the antivirus program but not what you did with it. Did you disable e-mail scanning in the antivirus software? Sometimes that is not sufficient. E-mail traffic may still pass through their proxy but no longer get interogated. If their proxy is dead, you can't get through it. So try uninstalling the antivirus software and retest.
You mention that they (Comcast) knows that they are blocking you on port 25. They do that when you exceed their anti-spam or anti-abuse quotas. You may have to argue with them as to why they won't let you send outbound e-mails because it appears they decided you can't do that anymore. Since you can't send on port 587, too, it appears they won't allow any outbound e-mails from your host on any port. So they blocked port 25 on their end. They would do that for a reason.
You mention that they (Comcast) knows that they are blocking you on port 25. They do that when you exceed their anti-spam or anti-abuse quotas. You may have to argue with them as to why they won't let you send outbound e-mails because it appears they decided you can't do that anymore. Since you can't send on port 587, too, it appears they won't allow any outbound e-mails from your host on any port. So they blocked port 25 on their end. They would do that for a reason.
ASKER
Norton's was uninstalled completely, and when I called for support, no one (including an engineer) mentioned anything being blocked other than port 25. However, there might still be something to what you've mentioned, because from another Comcast network, I was able to configure that same account to both send/receive email correctly. Comcast's first level support is just childish though, and I can't find out anything from them that I don't already know, so I'm not sure how to go get the help I actually need, which is frustrating. This problem is actually happening on my dad's home PC, and of course they claim the problem is with Outlook, so I will upgrade him to Office 2007 athough I don't think that will help. I will keep you posted, thanks.
Have you yet tried using port 465 with SSL to see if that works?
If you need to find out why port 25 has been deliberately blocked by Comcast, you need to force the issue with the 1st-level call tech by demanding they open a trouble ticket so you can talk to a higher up tech that can actually tell you why they are blocking that port (and apparently also port 587 since that also doesn't work for you).
Rather than spending money to get a later version of Outlook, just start testing with a simpler client, like Outlook Express. Turn on its troubleshooting logging and then send an e-mail, exit OE, and take a look at the logfile (same folder as where are the .dbx files for OE and called pop3.log and smtp.log).
If you need to find out why port 25 has been deliberately blocked by Comcast, you need to force the issue with the 1st-level call tech by demanding they open a trouble ticket so you can talk to a higher up tech that can actually tell you why they are blocking that port (and apparently also port 587 since that also doesn't work for you).
Rather than spending money to get a later version of Outlook, just start testing with a simpler client, like Outlook Express. Turn on its troubleshooting logging and then send an e-mail, exit OE, and take a look at the logfile (same folder as where are the .dbx files for OE and called pop3.log and smtp.log).
Did you ever try using Outlook Express to see if that e-mail client works with the default settings (or using 587 for SMTP instead of 25)? The error message you said that OL2003 showed is incomplete. The error message in OE will show more information, plus OE's troubleshooting log is easier to understand (I don't know if Microsoft improved the logfile records after OL2002).
You could also telnet into their SMTP mail host to see if you can get to it and if it begins a mail session (which you won't use but just to see if you can start one). In a DOS shell, run:
telnet smtp.comcast.net 25
See if they connect and show you their welcome line. If that doesn't work, change 25 to 587. To exit the telnet session, use the bye command.
You mentioned being able to send e-mail when on a "different Comcast network". I don't know if that means you used another host at the same location as the problematic host (i.e., your working host is on the same intranet as the problematic host) or if you went to some other physical location and used a completely separate Comcast account to test for e-mail operation. If Dad's home doesn't work and you tested it at your home, the different computers that are configured different for hardware and software along with the entirely different dynamic IP address and possibly using a different Comcast account (which hasn't been barred from SMTP traffic by Comcast) doesn't really help in solving the problem with the non-working host. It may not be a problem with the e-mail account but that blocking was established on SMTP traffic on a particular IP address (actually the provisioned MAC address that represents the location or customer that they are blocking that traffic). If you were using a different host and network to test on the same account, well, that only shows the account itself is functional and the problem lies back with blocking on the IP address on the non-working network, hardware config problem, like in a router there, or software config problem on the host that has only been tested in that same problematic location.
Where were you when you had problems with sending e-mails? For the "from another Comcast network, I was able to configure that same account to both send/receive email correctly", did you move the problematic host from the non-working network to a physically different network where it then worked, like move Dad's computer from his home to your home?
You could also telnet into their SMTP mail host to see if you can get to it and if it begins a mail session (which you won't use but just to see if you can start one). In a DOS shell, run:
telnet smtp.comcast.net 25
See if they connect and show you their welcome line. If that doesn't work, change 25 to 587. To exit the telnet session, use the bye command.
You mentioned being able to send e-mail when on a "different Comcast network". I don't know if that means you used another host at the same location as the problematic host (i.e., your working host is on the same intranet as the problematic host) or if you went to some other physical location and used a completely separate Comcast account to test for e-mail operation. If Dad's home doesn't work and you tested it at your home, the different computers that are configured different for hardware and software along with the entirely different dynamic IP address and possibly using a different Comcast account (which hasn't been barred from SMTP traffic by Comcast) doesn't really help in solving the problem with the non-working host. It may not be a problem with the e-mail account but that blocking was established on SMTP traffic on a particular IP address (actually the provisioned MAC address that represents the location or customer that they are blocking that traffic). If you were using a different host and network to test on the same account, well, that only shows the account itself is functional and the problem lies back with blocking on the IP address on the non-working network, hardware config problem, like in a router there, or software config problem on the host that has only been tested in that same problematic location.
Where were you when you had problems with sending e-mails? For the "from another Comcast network, I was able to configure that same account to both send/receive email correctly", did you move the problematic host from the non-working network to a physically different network where it then worked, like move Dad's computer from his home to your home?
ASKER
I'm not convinced the problem is with my client. I believe it is on the part of the ISP. I have tried all of the things listed in the article prior to posting on here, as was stated in the initial posting. It is unclear to me how someone other than the ISP can prove to be further help in this situation, so I'd like to please close this ticket.
Except you said, "from another Comcast network, I was able to configure that same account to both send/receive email correctly". That means there is no restriction in using that Comcast e-mail account to send and receive. They haven't placed any blocks on that account and have not terminated it. From that other location, you were also to reach the Comcast account to use it, so something from Dad's host in getting to his Comcast account is causing the problem. Certainly doesn't sound like an ISP problem. The interference could be antivirus software, firewall software (on Dad's host), other security software, a router (if Dad uses one instead of connects his host directly to the cable modem), a firewall in the router, the cable modem, or something with Comcast's DHCP server with the IP address that Dad got assigned to his router or host.
Try rebooting into Windows' safe mode (hit F8 when Windows starts to load to get the menu to select Safe Mode with Networking). When you login (which in safe mode), make sure the antivirus and firewall programs have been disabled. Now test if Dad can use his Comcast account.
If that doesn't work, try resetting each device in the path from Dad's host to his e-mail account. Check what IP address is now assigned to the computer (and to the router if one is used). On the computer, in a DOS shell, run "ipconfig /all" and record the IP address assigned to that host. If using a router and if the computer is configured to use DHCP for TCP/IP, the IP address for the host should get assigned by the DHCP server in the router and is usually in the 192.168.x.x range. If a router sits between the host and cable modem, and to see what IP address has been assigned to the WAN side of the router, connect to the web server in the router (it might be http://192.168.1.1). There should be a status screen that tells you what IP address is currently assigned to the router. Unplug power from both the cable modem and router. Wait at least 1 minute. With all devices powered down for a couple minutes, do the following:
- Plug in and power up the cable modem. Wait until it goes completely ready.
- Does the router have a power switch?
If yes:
o Make sure it is in the off position.
o Plug in the router's power cord.
o Press and hold the reset button for 10 seconds, or longer.
If no:
o Plug in the router.
o Press and hold the reset button for 10 seconds, or longer.
o Unplug the router. Wait a minute.
o Plug in the router.
- Power up Dad's computer.
- Login to Dad's account and retest e-mail operations.
That order guarantees that the upstream DHCP server is available when the downstream device wants to use it plus resets the router to factory defaults. After this, as a check, see if you happened to get a different IP address before for your router (or for your host if not using a router). Obviously Dad's Comcast e-mail account still works okay because you said so when accessing it from somewhere else. Sometimes the DHCP process screws up and you end up with an IP address that is stale (expired) and need to get a new one. Supposedly a client gets to continue using an expired IP address until they release it but I've seen times when Comcast did some maintenance and the DHCP process didn't work to get me a new IP address or the old stale one didn't work anymore.
If the above doesn't work, and if using a router, remove the router and connect the host directly to the cable modem. It is possible that the firewall in the router is causing problems. I've gone through 3 routers over 7 years. They burn out (there is no fan inside to get rid of the hot air and only convection is used through undersized vent holes, and why you NEVER stack anything atop a router). When behavior becomes flaky and cannot be corrected with a reset then it's time to get a replacement router.
Try rebooting into Windows' safe mode (hit F8 when Windows starts to load to get the menu to select Safe Mode with Networking). When you login (which in safe mode), make sure the antivirus and firewall programs have been disabled. Now test if Dad can use his Comcast account.
If that doesn't work, try resetting each device in the path from Dad's host to his e-mail account. Check what IP address is now assigned to the computer (and to the router if one is used). On the computer, in a DOS shell, run "ipconfig /all" and record the IP address assigned to that host. If using a router and if the computer is configured to use DHCP for TCP/IP, the IP address for the host should get assigned by the DHCP server in the router and is usually in the 192.168.x.x range. If a router sits between the host and cable modem, and to see what IP address has been assigned to the WAN side of the router, connect to the web server in the router (it might be http://192.168.1.1). There should be a status screen that tells you what IP address is currently assigned to the router. Unplug power from both the cable modem and router. Wait at least 1 minute. With all devices powered down for a couple minutes, do the following:
- Plug in and power up the cable modem. Wait until it goes completely ready.
- Does the router have a power switch?
If yes:
o Make sure it is in the off position.
o Plug in the router's power cord.
o Press and hold the reset button for 10 seconds, or longer.
If no:
o Plug in the router.
o Press and hold the reset button for 10 seconds, or longer.
o Unplug the router. Wait a minute.
o Plug in the router.
- Power up Dad's computer.
- Login to Dad's account and retest e-mail operations.
That order guarantees that the upstream DHCP server is available when the downstream device wants to use it plus resets the router to factory defaults. After this, as a check, see if you happened to get a different IP address before for your router (or for your host if not using a router). Obviously Dad's Comcast e-mail account still works okay because you said so when accessing it from somewhere else. Sometimes the DHCP process screws up and you end up with an IP address that is stale (expired) and need to get a new one. Supposedly a client gets to continue using an expired IP address until they release it but I've seen times when Comcast did some maintenance and the DHCP process didn't work to get me a new IP address or the old stale one didn't work anymore.
If the above doesn't work, and if using a router, remove the router and connect the host directly to the cable modem. It is possible that the firewall in the router is causing problems. I've gone through 3 routers over 7 years. They burn out (there is no fan inside to get rid of the hot air and only convection is used through undersized vent holes, and why you NEVER stack anything atop a router). When behavior becomes flaky and cannot be corrected with a reset then it's time to get a replacement router.
ASKER
Clarification: I should have said, "from another network", not another Comcast network. It worked fine for me from my house using Outlook 2007. I installed Outlook 2007 on his computer, and it started working again, for about one day, then the service was stopped again.
I'm not sure what Safe Mode will do, but we can try it.
There is nothing wrong with the IP address. We called Comcast to see when the lease expired, so I know we've renewed (validly) at least twice since then.
There is no router, just a direct connection to a cable modem.
Thunderbird and Mac Mail all do the same thing on dad's network, so that's really the main reason why I don't think it's client related. I thought maybe they were filtering us byb MAC/IP as you briefly mentioned earlier since it works from my home network.
Also, Comcast's claim is that "since Webmail is working for my dad's account, the problem is not with them". That may or may not be true, but I think you and I both understand that the two are likely not correlated.
You're help is really, really appreciated. I'm just not sure that the problem is with us, I think it's Comcast.
I'm not sure what Safe Mode will do, but we can try it.
There is nothing wrong with the IP address. We called Comcast to see when the lease expired, so I know we've renewed (validly) at least twice since then.
There is no router, just a direct connection to a cable modem.
Thunderbird and Mac Mail all do the same thing on dad's network, so that's really the main reason why I don't think it's client related. I thought maybe they were filtering us byb MAC/IP as you briefly mentioned earlier since it works from my home network.
Also, Comcast's claim is that "since Webmail is working for my dad's account, the problem is not with them". That may or may not be true, but I think you and I both understand that the two are likely not correlated.
You're help is really, really appreciated. I'm just not sure that the problem is with us, I think it's Comcast.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Outlook
Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.
105K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER