Effect of having mulitple IP addresses on an SBS2008 system
Hi,
I have inheritied an SBS2008 setup to support and the client is requesting some additional SPAM filtering above and beyond what exchange does.
A solution I have found sets it self up as a Proxy receiving the email and forwarding it on to exchange.
To install it on the same server as the exchange server, the installation instructions recommend that an additional IP address is added to the SBS2008 server. My question as this is not a recommended/supported configuration of the SBS server, what would the effect be on the SBS2008 server of having 2 IP addresses, and would it continue to function okay.
(The customer is not willing to spend money on a new server, and the system is setup in a virtual machine environment or else I would just bring up a VM and install the spam filter on an new OS instance).
Thanks for any help
Cheers
David
I have inheritied an SBS2008 setup to support and the client is requesting some additional SPAM filtering above and beyond what exchange does.
A solution I have found sets it self up as a Proxy receiving the email and forwarding it on to exchange.
To install it on the same server as the exchange server, the installation instructions recommend that an additional IP address is added to the SBS2008 server. My question as this is not a recommended/supported configuration of the SBS server, what would the effect be on the SBS2008 server of having 2 IP addresses, and would it continue to function okay.
(The customer is not willing to spend money on a new server, and the system is setup in a virtual machine environment or else I would just bring up a VM and install the spam filter on an new OS instance).
Thanks for any help
Cheers
David
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It doesnt break if you correct the bindings...it breaks if you leave those bindings to dynamically attach to any available IP/interface.
On any file and print server, etc...not a big deal to multi-home...but bottom line, on DC's (and SBS is a DC), multi-homing is not supported, not recommended and will break things. SBS has a very specific config it's looking for...go outside that and things quit working.
Perhaps if you follow the MS playbook to the letter, you are correct. But I have been adding secondary IPs and setting up anonymous relay connectors for exchange since SBS 2008's new limitations were encountered and have had no issues as long as the bindings on the core services are corrected on a reboot. All the same applies to SBS 2011.
I have to second gcolthart on this one I'm afaird. Not arguing it isn't supported and I'd reiterate I can't really comment directly about SBS but I've had scenarios where I've _had_ to multihome DC's (out of band management for example) and providing routing (particularly) and in some cases binding are managed, it works.
However, to get back onto track - I would recommend that as the OP has stated that the company paying the bills doesn't want to spend much (anything) that dropping a spare machine / virtual machine in and putting the completely free Mailcleaner product in would be the best approach - least ongoing cost, cheap and easy to manage.
However, to get back onto track - I would recommend that as the OP has stated that the company paying the bills doesn't want to spend much (anything) that dropping a spare machine / virtual machine in and putting the completely free Mailcleaner product in would be the best approach - least ongoing cost, cheap and easy to manage.
@gcoltharp there's a way to get around everything and if you're supporting it for your customers and don't ever expect to have to call anyone else, including MS, then you should by all means continue down that path.
The goal here is to provide posters with solutions and recommendations, even if the recommendation is to NOT do something, because the risk outweighs the reward, including being in an unsupported product configuration should they need to reach out the MS or other support organizations.
@davemj9876(author), it would be helpful to know what product you're trying to implement for this additional antispam solution. Have you considered doing this externally from services like Exchange Defender
The goal here is to provide posters with solutions and recommendations, even if the recommendation is to NOT do something, because the risk outweighs the reward, including being in an unsupported product configuration should they need to reach out the MS or other support organizations.
@davemj9876(author), it would be helpful to know what product you're trying to implement for this additional antispam solution. Have you considered doing this externally from services like Exchange Defender
ASKER
Thanks all, that gave me the information so that I could go back to the customer with and explain the situation, and we could continue to looks for alternatives to the original suggestion.
I don't know specifically to SBS but providing you only have one default gateway and manage your static routes very carefully, it _can_ be done on other servers.
Not that I'm recommending it, but in some scenarios it's a requirement.