cannot telnet to mail server on port 25

Hello Folks,

I have a mail server using just the IIS 6.0 SMTP relay. I am trying to mass mail to my customers on comcast, and my mail is not leaving the outgoing queue on it. I have disabled my antivirus. I cannot telnet to mx1.comcast.net on port 25, BUT I can telnet to its IP address. This is not the case with other mail servers like yahoo's. I am not having this trouble on my laptop as I can telnet to mx1.comcast.net and mx2.comcast.net. But I can only use those IPs to telnet to on the SMTP server. Is this possibly keeping this mail in the outgoing queue? I have tried rebooting and restarting the SMTP service. It is an update 2003 Windows server. Thanks!
mrosierAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ilya RubinshteynCommented:
It may be using secured SMTP for outbound transfer, I believe the port is 465? check the settings for comcast mail transfer on their site. You also need to have an authentication mechanism for the site.
mrosierAuthor Commented:
Well I was sending ok over the weekend without issue, and I actually have clear status on my connection sending the mail. They have confirmed to me that I should have a clear path to deliver my mails to comcast.net users. I have authentication requirements on my SMTP service on that server as well. What I don't understand is why I can telnet to port 25 of the IP addresses of those two servers but not the regular canoical names of those two servers? Could that be stopping me somehow?
Ilya RubinshteynCommented:
Oh, i did not realize you can telnet to the IP but not the FQDN. what happens when you ping the FQDN? try adding a manual entry pointing the fqdn of the server to the IP address and flushing the DNS settings on the machine.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

mrosierAuthor Commented:
DNS did the trick! my primary DNS server under the TCP/IP settings was out of date, and I forgot to update it as I have that machine's TCP/IP settings manually configured as it is a mail server. I changed it to the current DNS primary, was able to make the telnet sessions go with the FQDNs, flushed DNS, restarted the SMTP service, and mail started flowing. Thanks so much!
ExchangeOnTheRocksCommented:
From the IIS box, type nslookup and try to resolve the MX records of comcast.net. Are you able to see all the details successfully?
Secondly, on the properties of the SMTP virtual server, do you have any DNS server specified under Advanced settings?
Adam BrownSr Solutions ArchitectCommented:
It may be using secured SMTP for outbound transfer, I believe the port is 465?

As a note, Secured SMTP does not use a different port by default. Secure SMTP uses the STARTTLS command in SMTP to initiate a TLS secured SMTP communication. You can assign a different port for Secure SMTP from client to server (Like Google does, primarily to bypass ISPs that block SMTP for residential users), but most secure SMTP for server-to-server still goes over port 25.
systechadminConsultantCommented:
please check with your provide if the SMTP ports are opened from their end, its likely b the issue with port blocking
mrosierAuthor Commented:
The DNS check reminder showed me I had an out of date DNS server on the TCP/IP settings of that network connection. Thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.