Receive Connectors for Internal Relays - Before & After 2007-2013 Co-existence

I have just completed the process of migrating from Exchange 2007 Standard SP3 RP10 to Exchange 2013 Standard. I now have Exchange 2013 Standard CU3 installed on two Server 2012 Standard systems. The two new exchange servers are members of a DAG.
With Exchange 2007, I had to include the IP addresses of multi-function devices (MFDs) with scan to e-mail capability in a receive connector in order for the scan to e-mail to work.
Five of the MFDs were on the same subnet as our Exchange 2007 servers, and one MFD was not.
It is on the same subnet as our Exchange 2013 servers.
I created new Receive connectors on our Exchange 2013 servers for this purpose.
The one MFD on the same subnet as the Exchange 2013 servers was mistakenly excluded from a receive connector.
Much to my surprise, it is able to relay mail.
I removed the IP address of one of the other MFDs to see if the fact that it is on a different subnet than the Exchange 2013 servers made a difference.
I replicated our domain controllers to help ensure that a lack of AD replication would not be an issue with this test.
The excluded MFD is still able to relay items.
I have an application on a server. The application relays messages, but the IP address of the server it is on is not included in any receive connectors.
By searching through the SMTPreceive log, I found the IP address of the MFDs I did my scan to e-mail tests from in the log.
I also found the IP address and relayed messages from the application server.
The log indicates that the Default Frontend connector is handling this traffic.
Does Exchange 2013, by default, relay messages from all internal IP addresses?
Does this mean that I don’t need receive connectors for any internal devices (MFDs, servers, etc.).
Our Exchange 2007 servers have been decommissioned. Would I have needed connectors while we were still in a co-existence situation?
Am I likely to need them when we have our next co-existence situation in a few years?

Hi Cara. Thank you for the response.
If I understand you correctly, you are saying that the MFDs are able to relay because the Default Frontend connector allows them to.
That makes sense for the one MFD that was not included in the customised connector I created.
Thank you for helping me sort that out.
By analysing the Front End Transport logs at the following location on my server, I determined that the included MFDs were using the customised connector I had created.
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive
If I removed the IP address for one of those MFDs, it was still able to relay, but it was doing that through the Default Frontend connector.
That makes sense. As explained near the end of the following article, Exchange uses the most specific connector.
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
The one that includes the specific IP address of the MFD will be used, but if the IP address is not specified in any connectors, The Default Frontend connector will automatically be used by
the device.
I believe that I now understand how the have the relaying from MFDs is taking place, but I am not certain how some applications are completing their relaying.
Another department in my organisation has their own network.
I have a customised receive connector that includes the IP addresses of two application servers on their network.
Applications on these servers relay messages through the Exchange server on my network.
The headers on the relayed messages suggest that the messages are being relayed by the Default Frontend connector.
The logs for that connector, however, do not contain any entries for the two IP address.
The message tracking logs suggest that the Default <servername> connector is relaying for these applications.
If the most specific connector is supposed to handle the relaying, why is that not happening in this case?
Also, two other application servers from this network are not included in any customised connectors I have created.
The logs show that they are relaying mail through the Default Frontend connector.
If I understand you correctly, you are saying that this should not be happening, as applications and external users require a customised connector, rather than a built-in connector.
If I have mis-understood you, please clarify this for me.
Thanks!!

Similar Messages

Receive connector to allow relay for localhost

I have set up a relay receive connector to allow anonymous relay from another exchange server (send mails with Send-MailMessage cmdlet ) and it works just fine, but trying to send same mail from localhost falls into default receive connector and returns
authentication error. Adding anonymous users to permission groups in default receive connector it works, but it's not what I want. Is there a way to make the relay connector work for localhost too avoiding the overlap between connectors ?

Hi,
Let’s begin with the following article:
http://blogs.visendo.com/post/2009/12/23/Configuring-Exchange-2007-Relay-Settings-for-Exchange-Connector.aspx
“If you are using the localhost alias as the server name, be sure to include the loopback address (127.0.0.1) in the range.”
Thus, we can try to add 127.0.0.1 in the list of "receive mails from remote servers " setting.
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Thanks,
Angela Shi
TechNet Community Support

Exchange Server 2010 - Receive Connector for Client Computers

I have one customer with a SBS 2011 with Exchange Server 2010 - a pretty standard setup except for some customisation with Receive Connectors in order to cater for an application which is installed on a number of computers that requires to use an SMTP Server
to send notifications. In order to accomplish this (allow to be sent using Exchange Server) we added the IP Address of client computer (which we also set as a DHCP reservation) to a pre-configured Receive Connector (Anonymous setup for Printer/Scanner).
This worked fine, but we now find that there are other applications that require the same function to use SMTP to send.
How should/could this be better configured so an application can send if they authenticate?

Hi
For this you need to create a seperate receive connector to be used for Relay in your organizations.
Follow the below steps
1) Create a dedicated Relay Receive Connector
2) Add only the Ip addresses of the applications which needs to relay on Exchange servers
3) You can use either anonymous or authenticated relay according to your relay config
You can follow the below link as well
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Configuring Receive Connectors for External Notifications while still displaying Site Name

This is closely related to the issue we 'resolved' in
this blog
Our SharePoint notifications would not display the Site Name in the Display Name. i.e. If an Expense Request was approved, we wanted the display name of the email to come from "Accounting"
To resolve, we went to the receive connector and made sure only "Anonymous Users" was checked under Permission groups. The workflows and notifications immediately started displaying the site they originated in the Display Name, but...
All notification emails going to external users (outside our primary domain) ceased. We has to check 'Exchange Servers' under permission groups and then we lost the display name but gained email to external users.
Does anyone know how to get both working at the same time?
Thanks!!
Devster

Hi
Devster,
Check outgoing email settings in SharePoint Central Admin > System Settings
Let us know your results, thanks
Regards,
Pratik Vyas | SharePoint Consultant |
http://sharepointpratik.blogspot.com
Posting is provided AS IS with no warranties, and confers no rights
Please remember to click Mark As Answer if a post solves your problem or
Vote As Helpful if it was useful.

How to correctly configure send and receive connectors for SBS2011 exchange to connect to EOP

Hello SBS fans,
we have a customer with SBS2011 and exchange. The server email is setup for Exchange Online Protection.
It passes the Remote Connectivity Analyzer for inbound and outbound email. It shows a warning for the spf, saying it cannot find the spf record, BUT MXtool box passes everything associated with their domain name, including the spf record.
They are now getting some bounced email from yahoo servers, referencing this ip
65.55.169.249, which is a valid Microsoft ip.
I checked the bounce back email header carefully, and found a reference to an internal ip, 192.168.11.14, which just happens to be the ip of the user's desk PC!! - NOT the local addr of the sbs2011 server (which should not be there anyway)
I will guess that there is an incorrect setting in one or both of the hub transports? There is a correct smart host connector.
I am no longer sure about the other connectors!
Any ideas on this?
ewholz
Network and Server Installs

Hi,
à
It shows a warning for the spf, saying it cannot find the spf record
Would you please let me know the complete warning message that you can get? Meanwhile, would you please let
me know how long ago you add the SPF record? Be
more than 72 hours?
Please also refer to following article and check if can help you.
Configuring
Exchange 2007 Hub Transport role to receive Internet mail
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Device Removal message for internal hard drive after coming out of sleep

Hi,
I have search the forums and all the info I can find seems to just refer to external hard drives, how ever the problem I am having is with the internal drive.
When my G5 comes out of sleep mode, shortly after, I get a Device Removal error message then I loose my second drives and have to reboot for them to return. The drive is a 500 GB divided in two partitions, Mac OS Extended (Journaled), in slot B.
I have used Disk Utility and Tech Tools to check the drive, and the drive passes with no errors. I can't check file permissions as the drive is not a start-up drive.
This problem just started not long after using a USB thumb drive in the front, maybe just a coincidence or something went haywire after ejecting the USB drive?
Thanks,
Bill...

DaddyPaycheck wrote:
What brand is the drive?
Do you have a USB hub to try?
Have you checked the disk manufacturer's website to see if there are any updated drivers or firmware available and/or needed?
DaddyPaycheck wrote:
I have two Western Digital drives in the computer, both partitioned into two drives. One is a 1 TB the other a 500 GB. The 1 TB drive is the boot drive and I installed it about 2 months ago. The 500 GB drive, the one that is disappearing, I installed it about 6 months ago. Both drives pass Disk Utility, and TechTools testing (that is before the one disappears).
I do not have a USB hub, I have a DVD/RW connected via Firewire, and I have a USB external 320 GB to use for whatever.
No, I didn't think to check the manufacturer's web site for updates as the drives work fine, just the one 500 MB drive out of the blue I get the Device Removal message. And I am using the G5 at this moment replying here, and so far today I have connected my camera via usb with out issues.

OIM LDAP connector for internal WebLogic LDAP?

Has anyone ever used OIM to manage internal LDAP for WebLogic? I'm considering it for compliance reasons.

Interesting thought, but how is the authentication realm configured in WLS for you? If it's just the default authentication provider in your security realm then you got only 3-4 odd users to manage (an overkill to use connector?). Make sure that you manage those account as service accounts from OIM, you don't want to corrupt out our domain by accident.
-Bikash

TS1424 I bought the tv show revenge. iTunes keeps saying error downloading on 3 episodes mid season. It was ok for the shows before & after???

I keep getting a download error on a few episodes of a series I downloaded...help!!!

Welcome to the Apple Community.
Try deleting the problematic file (electing to remove original file if/when prompted) and then re-downloading the file from the iTunes store.
You can re-download content purchased from the iTunes store (availability varies depending on location) using the purchased option from the Quick Links section in the top right corner of the iTunes homepage in your iTunes application on your computer.
You can re-download content purchased from the iTunes store (availability varies depending on location) using the purchased option at the bottom of the screen of the iTunes app (or video app) on your iOS device.
If the problem re-occurs, select the content which is causing a problem and use the 'Report a problem' button in Your Purchase History using your computer.

Lync 2010 and Exchange 2007/2013 Co-existence

Hi,
I do not work with Exchange, and am only familiar with how Lync 2010 actually interacts with the product. If today we are working with Exchange 2007, and in the future there are plans to migrate to Exchange 2013, I am assuming there will be some sort
of co-existence required for a period of time.
What I am wondering is if anyone has encountered (or is aware of) any issues that may arise as a result of having Lync 2010 deployed in an environment with both of the above versions of Exchange in parallel.
Would the differences essentially come down to where the user's mailbox was homed? In other words, would a Lync 2010 user receive the integration features that come with the particular version of Exchange they are homed on? Or would having both
versions of Exchange in one environment potentially impact Lync 2010 in some way?
Thanks so much in advance for any help you can provide, as I have had trouble finding answers so far.

sorry to reopen the thread...
Hi all,
Does anyone know of any update regarding the following link ??
http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/

Modifying Connectors for Receiving Internet Mail - Anonymous setting?

I have a mail reflector for my domain to deliver mail on an alternate port, other than 25 because my ISP blocks port 25. I have the following default receive connectors:
Default Client Font End Transport (FrontEnd Transport) - TLS, Basic, Integrated, Exchange users, port 587
Default Client Proxy (Hub Transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange Server Auth, Exchange Servers, Exchange users, port 465
Default Front End Transport (FrontEnd Transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange server auth, Exchange Servers, Legacy Exchange Servers, Anonymous Users, port 25
Default Hub Transport (Hub transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange Server Auth, Exchange Servers, Legacy, Exchange Users, port 2525
Default Outbound Proxy Frontend Transport (Frontend transport) TLS, Enable domain security, Basic, Offer basic after TLS, integrated, Exchange server auth, exchange servers, anonymous, port 717
Issue: When I initially had mail forwarded to port 2525, I received a mail delivery system message: host mail.skincdc.com[69.250.204.88] said: 530 5.7.1 .Client was not authenticated (in reply to MAIL FROM command).
I modified the “Default Hub Transport” connector to allow Anonymous Users in addition to what I already had selected in the security settings. Voila, email is delivered to my exchange server from external domains.
I wasn’t sure if adding Anonymous Users to this connector would pose any issues. In order to try an alternate port, I changed my registrar to port 2626 and created a new receive connector Hub Transport, with only Anonymous
Users and port 2626. I saw the initial connection in my TMG firewall logs, but mail never made it to my exchange server, and I wasn’t receiving the above error message right away as before. Disabling this new rule and modifying the firewall back to port 2525,
email immediately was delivered. So can I just leave my Default Hub Transport receive connector as is with the security settings and Anonymous set? Thanks.
Next….getting email to send out on a different port than 25 to external domains. Still having issues with this one.
-SK

Hi Slevin
According to your setup you would need to receive emails on different port apart from 25
You can do the following thing
1) Create a dedicated receive connector for your ISP domain
2) Grant relay permission only to your ISP subnet and IP ranges
3) Change the port to your desired number on which you need to receive emails from them
4) Disable the default receive connector since its not required anymore
So the mail-flow for inbound will be in the following type
Inbound
From Internet - Mails comes to your ISP - ISP delivers to your firewall on different port - then it comes to exchange server
Let me know if you have any confusions on this and i will be able to help you further
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Migrate from 2003 to 2010 - Receive Connector Authentication

I'm in the process of upgrading a remote office from Exchange 2003 to Exchange 2010. Today, we changed the IP's on their firewall so that 2010 Hub Transport is handling mail. Normally, I always create a new Receive Connector for receiving mail
from the internet. I leave it as Anonymous users only and receive on internal IP of the server.
When I send an e-mail from the internet to a 2010 user, the mail is delivered fine, I'm assuming through the new "Anonymous" access connector I created. However, when I send e-mail from the internet to a 2003 user, I get the following NDR
with this error:
Reason: 530 5.7.1 Client was not authenticated
I was able to fix the problem by adding Anonymous authentication to the Default receive connector. I'm wondering why this connector is being chosen over the Internet connector though, and why only for 2003 users? Is it bad to leave the Default
Connector allowing anonymous access? I've always left that connector alone and created a new Internet connector which has seemed to work in the past.

Hi,
According to your description, exchange 2010 like a relay server, and relay the email to exchange 2003 when you send a email from the internet to a 2003 user.
As Ed mentioned, when you add the correct IP address where the traffic comes from on the receive connector, then it would ensure that the correct receive connector would be used.
The following article for your reference:
Resolve 530 5.7.1 Client was not authenticated
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 co-existence with 2007 can not send from 2013 - receives OK

2013 SP1 -separate servers for MBX and CAS - 4 of each. Exchange 2007 configured as a CCR
I am in co-existence mode but have not yet switched on the legacy.domainname.com. I have a new certificate installed on all servers - 2007 and 2013 with the legacy namespace included
I can receive on the exchange 2013 servers and can send to exchange 2013 users but cannot send to 2007 users or externally. I have enabled protocol logging and I'm seeing:
2014-04-02T00:57:31.476Z,Outbound Primary,08D1120CF8FEEDBA,0,,10.0.9.1:25,*,,attempting to connect
2014-04-02T00:57:52.521Z,Outbound Primary,08D1120CF8FEEDBA,1,,10.0.9.1:25,*,,"Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has failed to respond 10.0.9.1:25"
The client has a pair of Axway mailgateway appliances (Tumbleweed). We can Telnet between the exchange 2013 servers and the Axways. There is a firewall between these mail gateways and the exchange servers and the following ports were opened - 25,443,465,995,110
I used the existing send connectors from 2007 and just added the mailbox servers to them. I created 2 new receive connectors to match 2 specialist 2007 connectors.
But I still can't send mail. Any suggestions where next to check?

Hi Tony
Based on the protocol logs error looks like there is connectivity problem between Ex2007 and Ex2013
First you can try dropping an email through Telnet from Exchange 2013 to Exchange 2007 to see the message failure happens at which transit.
You can add the IP address of Exchange 2013 in Exchange 2007 default receive connector and vice versa.
Restart the transport service and try sending an email from exchange 2013 to Exchange 2007 and see the results
Also you can try creating a dedicated receive connector for Exchange 2007 in Exchange 2013 and vice versa if the above step does not work
Also try disabling the firewall and see if it helps.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

FIXED - Exchange 2013 - Can I Recreate Default Frontend Receive Connector SAFELY?

Hi
I'm need of some urgent assistance please.
I had a fully functional Exchange 2013 server and decided to create a receive connector for a photocopier/scanner to included its static IP  port number 25.
I accidentally chose Hub Transport role and not FrontEndTransport role which appears to have messed up port 25 connectivity on mail coming in from the internet. When I stopped and restarted the Transport Service within services.msc I then got this error.
Source: MSExchangeTransport
Event ID: 1036
Task Category: SmtpReceive
Level: Error
Description: Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running
properly.
I proceeded to delete the offending Receive connector for the scanner/photocopier and restart the server, the transport service started ok this time but still I cant receive mail from the outside world.
My question: Can I delete the automatically created default Frontend "servername" connector which contains the proper settings then recreate it again with the same settings and NOT harm/delete all the users emails or the mailstore
or anything bad for that matter?
I have the details on how to create the connector but just wanted to check that's its ok to remove it and re-add it again now that everything was setup and running fine. I'm hoping the recreated Connector will fix what I broke.
Appears what I have done has broken my connectivity to telnet to port 25 to the exchange server from the outside world although oddly I can telnet to the server from a command prompt on the exchange server (telnet "servername" 25) and
getpresented with the exchange server responding. The tickbox for anonymous is ticked already. Port 25 already is forwarded from the firewall to the exchange server and was working fine till I made the error.
Any help is greatly appreciated. Thankyou.

OK so I found some more details online and decided to take the plunge (after a backup was taken) and my problem is now fixed. Although thank you to the 40 people that atleast looked at my query.
This worked for me, please read, backup and decide yourself if you wish to follow my steps.
1. I Read this to understand more on how I broke it in the first place  :
First section of this......
https://exchangemaster.wordpress.com/tag/smtp/
then
http://support.microsoft.com/kb/2958036
2. Deleted the Default Frontend "servername" Receive connector
3. Recreated it using these guidelines below. (I included them all for your ref). Source https://social.technet.microsoft.com/Forums/exchange/en-US/32e13998-a84e-4f10-8557-3f7ce6fdb824/2013-default-receive-connectors:
[PS] C:\>Get-ReceiveConnector | fl Name,AuthMechanism,RemoteIPRanges,TransportRole,permissiongroups,MaxMessageSize
Name             : Default EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Name             : Client Proxy EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Name             : Default Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Name             : Outbound Proxy Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Name             : Client Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : ExchangeUsers
MaxMessageSize   : 35 MB (36,700,160 bytes)
4. Recreated the Receive connector for my photocopier/scanner but this time choose Frontend Transport role and Not the default Hubtransport. Restarted the server, crossed my fingers and everything worked!! (Apparently restarting both transport services
is sufficient, but hey I just want to be sure it works from reboot in future.
Exchange SP1 will break any custom receive connectors that you have made prior to installing the update (nor even warn you that you're about to create an addition hub transport connector on port 25 after the SP1 update, there should
be only one hubtransport on port 25 as I understand it, its ok for Frontend transport) . The transport service will not start, so to save you the hassle of deleting your custom connector just run this command from an elevated exchange powershell command to
change the custom connector from hubtransport to Frontend Transport then start the transport service. ( you may have to kill the Transport service .exe process in task manager, then start the transport services after this amendment from the services.msc panel)
Set-ReceiveConnector –Identity "Your Receive connector name" –TransportRole FrontendTransport
Alternatively, delete and re-create the receive connector and set its role to
FrontendTransport and NOT HUBTRANSPORT !!!!!!!!!!!
This issue occurs if there is a receive connector of Transport type
HubTransport that has the binding set to port 25 on the affected Exchange 2013 server. On an Exchange 2013 server that has both back-end and front-end roles, only the
FrontendTransport server-type receive connector should have the binding set to port 25.
To fix this issue, run the following cmdlet to change the connector type from
HubTransport to FrontendTransport:
Source: http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-server-2013-sp1-transport-service-stops-and-does-not-restart.html

Send and receive connector

Hi Everyone, I have 2 send connectors and 4 receive connectors configured on exchange server 2007.How do i know which send or receive connector i am using for my exchange 2007.I am doing the transition to exchange server 2013. If i create a new send
and receive connector in exchange 2013 without looking back to exchange 2007 will i face any issue.Do guide me how to create it in exchange 2013.

Hi Risingflight,
According to your description, I found that we want to create send and receive connectors for the new Exchange 2013 server with the same settings as the old Exchange 2007 server.
I suggest collecting the settings on EMC from Exchange 2007 server, and doing the same settings on Exchange 2013 server.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Configure send connector for exchange online protection

Hello Forum members,
I am trying to configure send and receive connectors for Exchange 2010 to route
on-premises mailboxes to Exchange OnLine Protection. The "help" info MS provides
is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
Exch Management Console. How can I configure connectors to properly connect to the Exchange Online Protection?
I have seen where the ip addresses are posted, etc. I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
Any tips will help,
Thanks,
Eric H.
Network and Server Installs

Hello Wesleyhe,
You cannot use AD anything with EOP - if you mean exchange on-line protection.
you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
on the SBS server. the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
Then you need to configure the outside ip for your SBS server access in the EOP admin area.
Hope this helps.
eholz
Network and Server Installs

Receive Connectors for Internal Relays - Before & After 2007-2013 Co-existence

Similar Messages

Maybe you are looking for