Solved

Cannot connect to Exchange 2010 SMTP port with telnet & no incoming email

Posted on 2010-09-12
27
3,280 Views
Last Modified: 2012-05-10
On a recently installed Excahnge 2010 server I am not able to connect to the SMTP port.  When it was originally installd I was able to telent into port 25 and get the mail server header info but now I am not and I am not getting any incoming mail.  

The server does not have any anti-virus software or spam filtering software and the receive connector is set to allow anonymous connections.  All available updates are installed and SP1 has been installed.  All after the problem started.  I know it is not a firewall issue because I am not able to connect from the local network or even the local machine.  

The system was not a upgrade, it was a clean install and it is running Server 2008 R2 with Exchange 2010 SP1.  The system is running the Hub Transport, Client Access and Mailbox roles as well as DNS and AD.  It is the only server in the network.  Any help would be appreciated.  
0
Comment
Question by:alapeter
  • 13
  • 8
  • 6
27 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658392
Can you telnet to port 587 instead?
0
 

Author Comment

by:alapeter
ID: 33658406
No i am not
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658414
Okay - what are the settings on your Receive Connector set to and what ports on your firewall are open?
0
 

Author Comment

by:alapeter
ID: 33658439
the client one is set for port 587, tla, basic, exchange, & integrated authenticationwith permisions set for exchange users  and the default is currently set for 25 tls, basic, exchange, integrated authentication and permisions are set for anonymous, exchange users, exchange servers & legacy.  Firewall is set to forward port 25 but as I said originally it won't accept a connection from the local network either.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658453
Okay - are all your Exchange Services started?
"What about the Receive mail from remote server that have these IP Addresses" part:
What IP's are set?
Also - what is your local IP set to on each connector?  The same as your Exchange Server's IP Address?
0
 

Author Comment

by:alapeter
ID: 33658661
the receive connectors are set to listen on all available ip address and to receive mail from 0.0.0.0-255.255.255.255.  All services are started except the transport service it starts then stops.  I checked one of the other exchange servers I manage and it acted the same way so I didn't think that was causing the issue.  
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658692
Well, without the Transport Service running, you won't be able to Telnet or send / receive mail.
Please check your Application Event Logs and see if there are any specific errors around the time you start the Service and it stops.
You will need this to be running permanently for Exchange to function properly.
 
0
 

Author Comment

by:alapeter
ID: 33658716
When I start the service it comes up and says that it started and then stopped and in the application log I get an

Event ID 1016 " The worker process crashes continuously on startup: C:\Program Files\Microsoft\Exchange Server\V14\Bin\edgetransport.exe. The service will be stopped."

and an

EventID 4999 "Watson report about to be sent for process id: 8088, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, edgetransport, M.Exchange.Rpc, M.E.R.RpcServerBase.RegisterServer, M.E.Rpc.RpcException, 7594, 14.01.0218.014.
ErrorReportingEnabled: False"
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658734
If the server is a clean install - is it in production yet?
If not - you may be better off flattening it and starting again.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658741
Have you installed any Rollups / SP1 yet?
0
 

Author Comment

by:alapeter
ID: 33658761
After the issue started the local admin installed all of the available rollups and updates and earlier today I installed SP1 and still no go.  Normally I would just melt it down and start over but I do not have physical access to the server and the office it is in is a 5 hour drive away.  It was working fine up until about 3 days ago.  After the initial install it was receiving and sending mail and I was able to telnet into port 25 and get the proper responses.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33658769
When were the Rollups / SP1 installed and did the problems occur straight after SP1?
You might want to roll back SP1 and see if all is well again.
0
 

Author Comment

by:alapeter
ID: 33658775
The rollups and SP1 were done after the problem started.  
0
Promote certifications in your email signature

Has your company recently won an award or achieved a certification? They'll no doubt want to show it off. Email signature images used to promote certifications & awards can instantly establish credibility with a recipient and provide you with numerous benefits.

 
LVL 74

Expert Comment

by:Glen Knight
ID: 33660088
As Alan has already pointed out if the Transport service is not starting then this is where the problem lies.

Other than the DrWatson error are there any other errors in the event log?

Are there any other services that are set to automatic that are not starting?

Can you disable any local firewalls and try restarting the service
0
 

Author Comment

by:alapeter
ID: 33660645
No other services are failing to start and Windows Firewall has already been disabled.  When I try to start the service I only get the 2 errors in the application log that I previously listed.

0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33660664
from a Exchange Management Shell can you run the following command and post the results.

Get-TransportAgent
0
 

Author Comment

by:alapeter
ID: 33661325
Identity                                           Enabled         Priority
--------                                           -------         --------
Transport Rule Agent                               True            1
Text Messaging Routing Agent                       True            2
Text Messaging Delivery Agent                      True            3
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33661346
Can you run the following:

Disable-TransportAgent -Identity "Transport Rule Agent"
Disable-TransportAgent -Identity "Text Messaging Routing Agent"
Disable-TransportAgent -Identity "Text Messaging Delivery Agent"

Then try starting the transport service.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 33663874
Thanks Glen.
Alan
0
 

Author Comment

by:alapeter
ID: 33667725
Ran the commands and tried to start the service and the service still doesn't stay running and I am  still getting the same errors in the event log
0
 

Author Comment

by:alapeter
ID: 33675215
Since the rest of Exchange looks like it is working correctly and the only thing that screwy is the Hub Transport funtion woudl it be worth a try to uninstall that role and reinstall it?
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33675310
That was my next suggestion.
Please give it ago
0
 

Author Comment

by:alapeter
ID: 33680769
Didn't work.  Same issue after the install and the install threw an error becuase the transport service wouldn't start.  SO I am think it is something outside of exchange that is causing the issue.  What else could cause the transport service to fail?
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33680779
Hmmm, it's a long shot but can you try:
Using the Group Policy Management Console, locate the Default Domain Controller Policy, right click on the policy and select Edit.

Once you have the Policy Editor open, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment and locate the Manage auditing and security log setting.

Modify the entry for the groups that have permissions so that the Exchange Server group is included. If you still have Exchange 2003 in your enterprise then you will also need to ensure that Exchange Enterprise Servers is entered here. The groups should be entered in the format of DOMAIN\Exchange Server and DOMAIN\Exchange Enterprise Servers.

Make sure you use the browse option to find the group as there are no validation checks performed in the user interface, so if the group doesn't exist or is spelled incorrectly it will still include it.

detailed in my article here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2829-Exchange-2007-Topology-discovery-failed.html
0
 

Author Comment

by:alapeter
ID: 33683502
Ok  I'll try that if I have too but I may have it solved.  I think something the local admin installed screwed something up with IPV6 because I started having issues with other network services (RDP, RRAS, etc) So I comepletly disabled IPV6 restarted and then had the local guy enable it and restart.  I was able to get almost all the services to work after doing this.  Since the re-install of the HUB Transport role crapped out before it finalized I am in the process of unitsalling the role and reinstalling then I will re-apply SP1, hopefully everything should be working and up to the same versions at that point.  I'll update the question I am finished.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33683518
IPv6 is required for the Transport Service to start, so if IPv6 was disabled then this would cause the problems you are seeing.
0
 

Accepted Solution

by:
alapeter earned 0 total points
ID: 33687494
I know that it requires IPV6 and it was enabled but the service was acting like it wasn't that is why we disabled it and then enabled it.  This seemed to do the trick.  Once I did that and uninstalled and reinstalled the hub transport role it started working.  So this is what we had to do.

1. Disable IPV6
2. Restart the server
3. Enabe IPV6
4. Delete send connectors
5. Uninstall Hub Transport Role
6. Restart the server
7. re-install Hub Transport role
8. restart server

Once I did this in this order I was able to telnet into port 25 and the server started receiving mail again.  S I do not know what caused the issue or exactly what fixed it but uninstalling adn re-installing didn't fix it.  It finally worked after the steps I listed above.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Distribution Group 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 Recipients >>…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

758 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

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now