Sign in
 
Exchange Server TechCenter > Exchange Server Forums > Exchange Software Updates > Exchange 2007 SP2 Relay Problem
Ask a questionAsk a question
Search Forums:
 

Proposed AnswerExchange 2007 SP2 Relay Problem

  • Wednesday, November 04, 2009 10:43 AMMicroTeck Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    After upgrading our Exchange 2007 to SP2 (192.168.0.X), we encoutnered a problem whereas our Scan to Email function for one of our printers sitting in the DMZ (192.168.1.X) cannot relay through Exchange. Does anyone know of a particular problem which would stop the relaying of traffic on port 25 into Exchange from internal subnets. I have check ISA and can see the traffic hitting the box. No rejections. Any help regarding the following problem would greatly be appreciated.
     

All Replies

  • Wednesday, November 04, 2009 10:50 AMShaun Croucher Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    By default, relaying is denied. You will need to customise a receive connector to allow relaying.

    Here is the article you need: http://msexchangeteam.com/archive/2006/12/28/432013.aspx

    Shaun
     
  • Wednesday, November 04, 2009 11:02 AM--Vinod-- Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Yes Please check the Connector Configuration Again and open the relay for Printer by following article provided by Shaun.
    Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
     
  • Wednesday, November 04, 2009 12:15 PMMicroTeck Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I have followed the articles as describes and still no luck!
     
  • Wednesday, November 04, 2009 1:43 PMShaun Croucher Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    OK,

    So what method did you use, allow anonymous users the relay permission or setup a receive connector to be externally secured?

    You need to make sure that you connect to the correct receive connector. It is often easier to give the new receive connector a secondary IP address for it to listen on, or use an alternative port so you know you are connecting to the customised receive connector.

    You can use telnet to connect to the receive connector and see what banner is shown, this is a good way to determine which receive connector you are connecting to

    If you run:

    telnet [IP of connector] 25

    Then take a note of the 220 BANNER

    Match this to the FQDN on your receive connector.

    I assure you if you configure a connector using either of those methods and connect to it successfully you will be able to relay.

    Shaun