asked on Exchange server down after IP change
Hi,
I have an Windows 2003 64 bit server running Exchange 2007. We recently changed the IP address from a 192.168.1.xx to 192.168.10.xx network.
Now users can send email, but they cannot receive anything.
When I try and telnet to the server on port 25 I get the message "421 4.3.2 Service not available, closing transmision channel"
I am at a loss, what should I check?
I know the previous company has fooled with bindings, and the customer is down!
I have an Windows 2003 64 bit server running Exchange 2007. We recently changed the IP address from a 192.168.1.xx to 192.168.10.xx network.
Now users can send email, but they cannot receive anything.
When I try and telnet to the server on port 25 I get the message "421 4.3.2 Service not available, closing transmision channel"
I am at a loss, what should I check?
I know the previous company has fooled with bindings, and the customer is down!
ExchangeWindows Server 2003
Last Comment
borgmember
ASKER
Yes, I checked that first thing and it appears to be okay. I can get to 25, its just like the service isnt running, but all services are running on the server.
ASKER CERTIFIED SOLUTION
THIS SOLUTION 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.
ASKER
They are setup weird, there is a company the prior people setup named mxpath.net that sends their mail into the server.
They have one named "Client" under General the FQDN is their local server name such as server.domain.com
Under network IP address allowed to receive mail is All available and Port 587
Receive from is stated as 208.74.22.0 and the subnet is 255.255.248.0
Under authentication the following is checked:
Transport layer security TLS
Basic authentication - offer basis authentication only after starting TLS
Integrated windows authentication.
Under permissions groups
Exhcnage users is checked.
The next receive connector under network says:
server.domain.com for FQDN
IP Addresses allowed to receive email is :
192.168.10.2 port 25 (this is the servers local lan ip address now)
Receive mail from remove servers is
208.74.52.0/21
Authenitcation, nothing checked
Under permissions Anonymous is checked,
From what I gather they send with a smarthost which is working, but they cannot receive anything and exchange does not answer on 25. What should my receive connectors look like?
They have one named "Client" under General the FQDN is their local server name such as server.domain.com
Under network IP address allowed to receive mail is All available and Port 587
Receive from is stated as 208.74.22.0 and the subnet is 255.255.248.0
Under authentication the following is checked:
Transport layer security TLS
Basic authentication - offer basis authentication only after starting TLS
Integrated windows authentication.
Under permissions groups
Exhcnage users is checked.
The next receive connector under network says:
server.domain.com for FQDN
IP Addresses allowed to receive email is :
192.168.10.2 port 25 (this is the servers local lan ip address now)
Receive mail from remove servers is
208.74.52.0/21
Authenitcation, nothing checked
Under permissions Anonymous is checked,
From what I gather they send with a smarthost which is working, but they cannot receive anything and exchange does not answer on 25. What should my receive connectors look like?
ASKER
I just ran the mail troubleshooter. When it tries and sends email to me, I get the message:
"Mail submission failed: Error message: Service not available, closing transmission channel. The server response was: 4.3.2 Service not available, closing transmission channel."
"Mail submission failed: Error message: Service not available, closing transmission channel. The server response was: 4.3.2 Service not available, closing transmission channel."
Have you checked your local A and MX records to ensure that they are updated to your new internal IP? Have you checked your routing to ensure that external traffic is now redirected properly as well?
ASKER
I made a new connector and let it receive anything from anyone and now it works.
If you have any firewall or antispam agent in between than need to change the natting of the ip address and specify the new ip address given to the server.