[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 727
  • Last Modified:

can receive but can not send after changing ip address

just got new t1 internet. i modified exchange 2003 to new ip addresses both internally and externally. i can receive mail but simply can't send. the exchange is going

where should i look at to solve the problem?
0
cuc888
Asked:
cuc888
  • 7
  • 5
  • 4
  • +4
1 Solution
 
Irwin SantosComputer Integration SpecialistCommented:
One way is to RIGHT CLICK on CONNECTORS (Internet Mail SMTP Connectors) in ESM, then choose, "Forward all mail through this connector to the following smart hosts"... enter your upstream providers SMTP server.
0
 
poweruser32Commented:
check your smtp VS click on properties general tab check ip address
0
 
cuc888Author Commented:
i've checked smtp and all ip addresses are correct.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
SembeeCommented:
Are the messages sitting in the queues? If so, what does the queue say?
Were you using a smart host before? Is that still a valid smart host? Check on the SMTP virtual server for a smart host as well.

Simon.
0
 
cuc888Author Commented:
there are lot of messages in queue, they are all in Retry state.
0
 
SembeeCommented:
If you click on the queue, what does the message box below say?

This looks like classic smart host error.

Check ESM, Servers, <your server>, Protocols, SMTP, Right click on the Default SMTP VS and choose Properties. Click on the tab Delivery and then Advanced. Ensure that smart host is blank.

If you have an SMTP Connectors, make sure that the smart host is blank or set to a smart host that is valid for your new IP address range.

Simon.
0
 
cuc888Author Commented:
i tried Force Connection but they won't go. is there anyway i can force to send them out for now while figuring it out.
0
 
SembeeCommented:
If something is blocking the connection then you can force the email as many times as you like - the messages will still not go. You have to find the source of the problem.

Simon.
0
 
robjeevesCommented:
G'day mate

Simons advice should be looked at first;

"Check ESM, Servers, <your server>, Protocols, SMTP, Right click on the Default SMTP VS and choose Properties. Click on the tab Delivery and then Advanced. Ensure that smart host is blank."

If you have a smarthost configured with your last ISP (assuming the T1 is with different ISP) your exchange box will be trying to send mail through them still.  As you have moved ISP they will not be allowing you to send through them.  

Rob
0
 
cuc888Author Commented:
i've checked and smart host is blank. it takes a while but mails seem to go out this evening or at least i can send and receive mail from hotmail.

does it also affect my HTTPS over RPC? apparently it is currently not working, i've tried numbers of machines from home. do i need to do anything or just wait till the new ip is propagated?
0
 
cjtramanCommented:
Simply restart your exchange smtp service. it would automatically force the mails in the queue to be delivered to the relay host.
0
 
Nilesh RoyCommented:
Cjtraman, what if the relay host is rejecting the emails?? wont they still remain in the Queue?? Read the thread above.

- Nilesh Roy.
0
 
Nilesh RoyCommented:
okie
0
 
cuc888Author Commented:
hi sembee,

everything is working now except RPC over HTTPS. did changing IP address affect this and where i should look to solve this problem? i've tested local connection and when i look at Connection Status it says TCP/IP instead HTTPS.
0
 
SembeeCommented:
RPC over HTTPS uses the host name, not the IP address, so it shouldn't have affected anything. As long as the certificate resolves correctly and all the internal names also resolve, then everything should continue to work as before.

Simon.
0
 
cuc888Author Commented:
that's the problem. i've changed nothing other than internal and external ip address.
0
 
Nilesh RoyCommented:
1 basic question, did you reapply Exchange 2003 SP2 onto your server?
0
 
Nilesh RoyCommented:
1 more thing, since you have changed your IP addresses, did you regenerate your certificates? please check that too.
0
 
Nilesh RoyCommented:
anyupdates on this?
0
 
cuc888Author Commented:
i've resolved the problem already. i overlooked ssl port ip address, the address was the old ip address and i changed it to new one.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 7
  • 5
  • 4
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now