Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

exchange 2003 cannot send to comcast.net

Posted on 2013-01-23
7
Medium Priority
?
657 Views
Last Modified: 2013-01-24
As of 48 hours (or so) ago, mail stopped flowing to comcast.net.  The queue for comcast.net in exchange server says "an smtp protocol error has occurred".

Mail has been flowing fine to comcast for years and now i cannot get mail to go to them.

Mail to all other domains flows fine.  

No changes to nameserver since October last year, Not blacklisted.  Nothing new done on server.  

Ideas?
0
Comment
Question by:AndyMT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 12

Expert Comment

by:michaelgoldsmith
ID: 38812221
Try to telnet to their mail server from your mail server.
Also run SMTPdiag on your mail server to see what the error message is from their end. You may be blacklisted.
0
 

Author Comment

by:AndyMT
ID: 38812267
We are clean on all the blacklists.  Will telnet shortly.  Thanks
0
 
LVL 12

Accepted Solution

by:
michaelgoldsmith earned 2000 total points
ID: 38812274
SMPTdiag will give you the error info you need to trace.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:AndyMT
ID: 38812325
Here's the results.  I had added Google's DNS servers earlier today in case the problem was there, but that made no difference.  I need education on the "serial numbers do not match".


C:\SmtpDiag>smtpdiag larry@balcombgreen.com mritrash@comcast.net

Searching for Exchange external DNS settings.
Computer name is SERVER.
VSI 1 has the following external DNS servers:
208.72.70.5,208.72.71.5,8.8.8.8,8.8.4.4

Checking SOA for comcast.net.
Checking external DNS servers.
Checking internal DNS servers.
Serial numbers do not match: 2008177974  2008177972
Serial numbers do not match: 2008177974  2008177972
Serial numbers do not match: 2008177974  2008177972
SOA serial number match: Failed with one or more failures.

Checking local domain records.
Checking MX records using TCP: balcombgreen.com.
Checking MX records using UDP: balcombgreen.com.
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Checking MX records using TCP: comcast.net.
Checking MX records using UDP: comcast.net.
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for mritrash@comcast.net.
Connecting to mx1.comcast.net [68.87.26.147] on port 25.
Error: Expected "220". Server is not accepting connections.
Failed to submit mail to mx1.comcast.net.
Connecting to mx2.comcast.net [76.96.40.147] on port 25.
Error: Expected "220". Server is not accepting connections.
Failed to submit mail to mx2.comcast.net.
0
 

Author Comment

by:AndyMT
ID: 38812401
Reran the same test with the "/v".  Turns out Comcast has the domain blacklisted even though it passes every blacklist check.  Problem solved I think.
0
 
LVL 12

Expert Comment

by:michaelgoldsmith
ID: 38812933
Glad to see you resolved the issue. I suspected blacklist initially. Email them and they should get u removed within 24-48 hours.
0
 

Author Closing Comment

by:AndyMT
ID: 38814995
Even though all the normal blacklists were clean, Comcast had blocked their domain.  Running SMTPDIAG /v gave me the info I needed to resolve the situation
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question