glennda Posted January 4, 2012 Posted January 4, 2012 I'm just in the throws of setting up our new Exchange box - I've setup so that OWA works correctly which is fine but I've got an issue with SMTP. When I change on our ISA where incoming mail is sent to 10.2.0.6 to 10.2.0.7 nothing comes through - As soon as you change back it works - I'm pretty sure I have set it up correctly but apparently not - any ideas folks? Most probably dead simple i'm just being an idiot!
john Posted January 4, 2012 Posted January 4, 2012 the SMTP receive connector on the EX box set to allow Anonimouse connections?
rh91uk Posted January 4, 2012 Posted January 4, 2012 have you examined the mail queues in exchange to see if any traffic is coming in? It sounds like an ISA problem? Turn on logging on the ISA box, if it is denied connections it should show you .... was good when I was examining some issues we had Just some thoughts
glennda Posted January 4, 2012 Author Posted January 4, 2012 Under server config/hub transport default? if so yes and also on client - its the same as the original server as far as i can see is exchange 2k7 sp3
glennda Posted January 4, 2012 Author Posted January 4, 2012 have you examined the mail queues in exchange to see if any traffic is coming in? It sounds like an ISA problem? Turn on logging on the ISA box, if it is denied connections it should show you .... was good when I was examining some issues we had Just some thoughts Its not getting to exchange - i'll look at Isa just can't see much valid info - Its getting to ISA its just ISA cannot forward for some reason.
sukh Posted January 5, 2012 Posted January 5, 2012 1. Are you using publishing rules for SMTP? 2. Up the receive connector logging on 2007 and see what the logs say
glennda Posted January 5, 2012 Author Posted January 5, 2012 Publishing rules on the ISA? if so yes - its setup and working on there as it works when i point to original server - when i point to new one it doesn't come though Where is the receive connector logging? Toolbox?
tom_newton Posted January 6, 2012 Posted January 6, 2012 Unlikely you have missed this, but is ISA the default gateway for the exchange box? It is possible to set up a forward that can't be replied to because the host you are forwarding to tries to send replies to a different gateway. Have you tried telneting to port 25 on the ISA externally, see what (if any) answer you get?
sukh Posted January 6, 2012 Posted January 6, 2012 So the new rule for the new server is identical except an IP change? Go to the EMC>Server Configuration>Receive Connectors and turn up the logging on the appropiate connector. I assume you have the default 2 unlesss you have created additional connectors. If not do it on the Default connector. From the ISA server, can you telnet to the new Exch server on port 25?
glennda Posted January 6, 2012 Author Posted January 6, 2012 @tom_newton - the default gateway is our core switch which then routes to the ISA (as vlans) - this is the same on both so shouldn't be a routing problem (I hope!) @sukh - will turn on logging and test this evening - not sure I can get away with testing during the day!
sukh Posted January 6, 2012 Posted January 6, 2012 Sure, sorry, the testing I'm saying is just a telnet test from the ISA to the new Exch server via a CMD prompt. This is just to verify that a connection and email can be sent from the ISA to Exch. XFOR: Telnet to Port 25 to Test SMTP Communication
tom_newton Posted January 6, 2012 Posted January 6, 2012 tracert from exchange to any external IP - if ISA is one of the hops, you're golden...
glennda Posted January 6, 2012 Author Posted January 6, 2012 Sure, sorry, the testing I'm saying is just a telnet test from the ISA to the new Exch server via a CMD prompt. This is just to verify that a connection and email can be sent from the ISA to Exch. XFOR: Telnet to Port 25 to Test SMTP Communication Yeah i'll test that in a sec - its the receive connector logging i meant i can't do!
sukh Posted January 6, 2012 Posted January 6, 2012 Oh ok, there's no impact and you dont have to restart any services if you worried about an outage. You can do this on the fly.
glennda Posted January 6, 2012 Author Posted January 6, 2012 Yeah thats cool - both Telnet and Tracert are correct so its def a problem with Exchange. Will play around tonight with the Receive connector and logging.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now