In transitioning a customer from Exchange 2003 to Exchange 2010, one of the issues that cropped up was configuring the multi-function printers to be able to send messages internally.
Previously one just configured the relay list for the exchange server, and included the application server’s IP address or the multifunction printer/device’s IP address.
Exchange 2010 has far more stringent security focus, and therefore the process to enable anonymous connections requires a bit more effort and specific configurations. It is possible to do this with PowerShell (using Exchange modules) as well as creating it via the Exchange Management Console.
PowerShell:
New-ReceiveConnector -Name “NameOfConnector” -Custom -Server “Server Name” -AuthMechanism ExternalAuthoritative -Bindings xxx.xxx.xxx.xxx:25 -PermissionGroups Exchangeservers -RemoteIPRanges xxx.xxx.xxx.xxx/xx
where
- NameOfConnector is the descriptive name you give the connector (be sure to make it unique and easily understandable)
- Server Name is the name of the Hub Transport server on which the connector must be created
- Bindings xxx.xxx.xxx.xxx:25 is the IP address of the Local Network Settings for said HT server
- RemoteIPRanges xxx.xxx.xxx.xxx/xx is the range defined for example 192.168.1.0/24
EMC:
Create a new Receive Connector on each Hub transport role that will need to execute this anonymous connection.
- Open EMC
- Navigate to Server Configuration, select Hub Transport, select HT server
- Click on “New Receive Connector” on right hand task column
- Name it and ensure that “Custom” is selected for non-Exchange systems.
- Define the IP address and port number which the server will respond with to the send requests under “Local Network Settings”
- Remove any local addresses that are not relevant
- Define IP subnet(s) or specific IP addresses or ranges under “Remote Network Settings”
- Click “New” to create the connector
BIG NOTE! Be sure to monitor your queues to ensure that no authentication issues arise out of misconfigurations to the group permissions or authentication methods; or if any FQDN for DNS namespaces were configured. These misconfigurations may disrupt normal mail flow which wont make your life a happy place 
Bye for now…
Related posts:
- Exchange 2010 Address List Segregation and Current Support Stances
- Don’t call the Night Nurse – How To Upgrade Exchange 2010 Licensing from Exchange 2010 Standard to Exchange 2010 Enterprise
- More Exchange 2010 goodness – Exchange Management Shell Quick Reference for Exchange 2010
- Snom joins Compatible Devices Program for Microsoft Lync 2010
- Released: Update Rollup 4 for Exchange Server 2010
} – 
{ 1 comment… read it below or add one }
Hey, thanks for the steps. actually i was working on applying one receive connector for all authenticated MFPs and some applications, but i dont want relay, i want them to be authenticated senders, so whatever device or applications does not have authentications features then i dont want it to be able to send.
unfortunately i could not make it so far (it works only with relay, but we dont want the relay option), so is there a straight forward way to deploy such connector?
Thanks
Miamee