• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

Exchange server 2003 lost connectivity on port 25

Suddenly around noon today my Exchange Server stopped delivering incoming messages.  All internal emails work fine.

I am not getting a response from my exchange server when I try to telnet to port 25.

All services are running on exchange.

The information store is mounted.

The firewall is not in question when I try to telnet from the same subnet.

Help!!
0
LamkaB
Asked:
LamkaB
1 Solution
 
Exchange_AdminCommented:
Is your SMTP service running on the Exchange server?
0
 
LamkaBAuthor Commented:
Yes, the SMTP service is running along with all the exchange services.
0
 
Exchange_AdminCommented:
Are you sure that there is not a firewall running on the server?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LamkaBAuthor Commented:
Double checked.  Firewall service is not loaded.

Brenda
0
 
LamkaBAuthor Commented:
when running netstat -na on the exchange server the following entries exist:

Proto               Local Address               Foreign Address             State
TCP                 0.0.0.0:25                      0.0.0.0                        LISTENING
TCP                 192.168.1.248:25            192.168.1.1:52825       TIME_WAIT
TCP                 192.168.1.248:25            192.168.1.1:52833       TIME_WAIT
TCP                 192.168.1.248:25            192.168.1.1:52869       TIME_WAIT
TCP                 192.168.1.248:25            192.168.1.1:52874       TIME_WAIT

There are other entries for port 25 all showing TIME_WAIT
as well as other ports.

Brenda
0
 
LamkaBAuthor Commented:
Found the problem.  

I added an ip of 2 servers to the list of machines under connection control. One of which was the Firewall and the source of the incomming mail.

However, Exchange apparently did not like it!
0
 
SembeeCommented:
If you restricted the SMTP connection then I would expect traffic to stop.
Email that is coming from outside is not coming from the firewall - it simply passes through the firewall. Unless your email is coming in from an external machine (for example an antispam provider) then you cannot restrict access to SMTP if you want email to come in correctly.

Simon.
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now