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

Can't get relay to work on Exchange 2010 server

Our web server sends password help to users who forgot their passwords. After upgrading to Exchange 2010 is no longer worked so I Googled how to set up relay service to work on Exchange 2010.

I cerated a send connector on the internal exchange server and when the I hit forgot password it sent me the password change email, great it worked. But the problem is once I enabled the new connector the regular connecters for external emal stopped working. Mail stopped flowing, the only mail that would flow was that being relayed from the web server.

 I followed this information http://www.lazynetworkadmin.com/knowledgebase-mainmenu-6/2-windows/149-exchange-2010-configure-anonymous-relay-to-external-domains 

I had to disable the new connector and reboot the to get mail flowing again. So I then created the send connector on the edge server following these instructions and nothing happened. It just didn't work.

http://technet.microsoft.com/en-us/library/bb232021.aspx 

I assume there must ba a way to create a new connector and keep the existing one working, any help on what I am doing wrong would be greatly appreciated.
0
chicagohistory
Asked:
chicagohistory
1 Solution
 
RobertPartenCommented:
I need a little more on your setup here. How many Exchange servers are in your organization? You have an Client Access and a Edge Transport server?

Let me ask you a few questions:

1. The web server, does it reside on the same LAN as the Exchange and does it access Exchange interally?

2. Is content filtering turned on Exchange?

3. in your send connector is it set to allow email to be relayed from the web server through Exchange?
0
 
chicagohistoryAuthor Commented:
Robert,

The web server is on a different subnet as the mail server. Content filtering isn't on and the article i posted that I used to set this up said create a receive connector not a send connector. Like I said when I followed those instructions the relay worked but the rest of the regular mail stopped. I have narrowed it down to thet fact the two connectors can't use the same port number (25)

How can I work arround this issue?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
chicagohistoryAuthor Commented:
msabry,

I can't do the first opetion because I don't have another NIC in the server to add a second IP address. I did configure like the second article but it doesn't address the port 25 issue. That seems to be the sticking point - can't have two connectors with the same port number. I treid substituting but I guess mail can only go out on 25.
0
 
RobertPartenCommented:
You can create an Alias IP for the server under the NIC cards TCP/IP settings. Then you can choose the ALIAS'd IP of the server to use for that connector.
0
 
chicagohistoryAuthor Commented:
Never did that before - how do you cerate an alias IP?
0
 
RobertPartenCommented:
Go to the networls card properties (where you set ip and dns) and then click on advanced and you will see where you are able to add another ip address
0
 
chicagohistoryAuthor Commented:
I tried this but everyone lost connectivity to the mail server. I am set up for dhcp with a reserved IP address. The option to enter an alias was grayed out so I switched from dhcp and entered the IP manually then went to advanced properties and entered an alias IP but after that everyone lost connectivity to exchange. Did I miss something?
0
 
chicagohistoryAuthor Commented:
I called Microsoft and they made the settings exactly the same as I did for the relay connector. But he also added anomyous to the default connector, later he removed it from the default connector. It started working after he added it and continued after he removed it.

Making a change to the default connector must have shook something loose. I don't see any other explaination because it is working with the configuration I listed above.

The nice thing is they didn't charge me because it was resolved in a few minutes.

Thanks for your help - i hope this thread helps someone else sturggling like I did on this issue.
0
 
Glen KnightCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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