noooodlez
asked on
Sending unauthenticated email through the mailserver from remote subnet. (Send connector issue?)
Hi
I have an APC UPS with a management card. Within the interface I can set my server IP, smtp port, sender, recipient for sending notifications (power outages, temperature etc).
I use this on my main site without issue, emails bounce off the exchange box and come in from APC_Server1@attwater.com completely unauthenticated.
The problem occurs when I replicate this setup on a remote network segment (connected through VPN). It fails/times out, with very little detail in the available log.
Initially I though it was a firewall issue (I have seen them have issues with remote subnets). I discounted this by turning off the firewall.
So it must be an exchange issue, presumably with permissions on the send connector. I have added the ip range of the remote segment to the Default Receive Connector, but still no joy.
I am running SBS 2008 with exchange 2007.
Any ideas how to test / debug?
I have an APC UPS with a management card. Within the interface I can set my server IP, smtp port, sender, recipient for sending notifications (power outages, temperature etc).
I use this on my main site without issue, emails bounce off the exchange box and come in from APC_Server1@attwater.com completely unauthenticated.
The problem occurs when I replicate this setup on a remote network segment (connected through VPN). It fails/times out, with very little detail in the available log.
Initially I though it was a firewall issue (I have seen them have issues with remote subnets). I discounted this by turning off the firewall.
So it must be an exchange issue, presumably with permissions on the send connector. I have added the ip range of the remote segment to the Default Receive Connector, but still no joy.
I am running SBS 2008 with exchange 2007.
Any ideas how to test / debug?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SBS doesn't use the Default Connector, it uses its own.
Therefore if you have been changing the default connector then you haven't been resolving anything.
You need to run the fix my network wizard and allow it to correct the settings back to the default.
Then once you have done that, create a new Receive Connector that is restricted to just the remote IP address range.
Simon.
Therefore if you have been changing the default connector then you haven't been resolving anything.
You need to run the fix my network wizard and allow it to correct the settings back to the default.
Then once you have done that, create a new Receive Connector that is restricted to just the remote IP address range.
Simon.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
(sorry, when I say default connector, I mean my new connector)
ASKER
I also tried extending out the range of my default connector (as created by fix my network) as my subnets are sequential.
Still no joy.
Still no joy.
Odd that the wizard removed your Receive Connector.
You will need to run the configuration wizards within the SBS console to get it configured correctly. Once you have done that, then create a new connector for this remote server.
Simon.
You will need to run the configuration wizards within the SBS console to get it configured correctly. Once you have done that, then create a new connector for this remote server.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I resolved myself with the assistance of sembee.
ASKER
I have tweaked all sorts of receive connector settings and cannot get it to work.
I have attached a couple of images of my setup.
DefaultReceiveConnector.jpg
DefaultReceiveConnector2.jpg