Bridging on exchange server

Soldato
Joined
6 May 2009
Posts
20,194
We have a new server running Exchange. It has 4 1gb network cards, at the moment only one is used. We attempted to bridge 2 of them but a lot of services failed before the domain controller was contacted so had loads of authentication errors and exchange would not startup correctly after a restart.

Is it possible to set a time delay on services, or make the bridge process quicker? Seems a bit pointless we have 4 networks cards but are only using one
 
Last edited:
update - It seems that undoing the bridge looks like it fixed everything - what it actually did was disable services and stop 2 servers communicating with each other (without any notifications) People on the new server have not been able to receive external mail since 9.30am. Send external and send/receive internal have been working fine.

Error logs on exchange server show nothing???
 
This would be better in the Servers and Enterprise Solutions forum.

Why are you using bridging on an exchange server? Do you mean teaming?
 
Bridging is when you want to connect one network to a different network via a device (i.e. connect your laptop to you wireless network via a laptop).

Teaming is where you essentially make one 'virtual' NIC consisting of the 2 or more NIC's and is what you should be looking at.

A little hint is to remove the static IP (presumably you have one) on the NIC before you do this and then add it to the teamed NIC.



M.
 
If you want them teamed you'll normally need to change some config on the switches. Not sure on the exact commands as I always let the network team sort that out though.
 
To be honest exchange likely doesn't need the bandwidth so just put the NIC team in failover only mode, my experience is it's far more reliable, active/active teaming with LACP can be hit and miss...
 
Thanks guys, only just read all the replies. I'll let my boss know on tuesday. There's just me and him so he is the 'network team'
 
If you want them teamed you'll normally need to change some config on the switches. Not sure on the exact commands as I always let the network team sort that out though.
Depends on the switch tbh that.
Although it would be a good idea to let whoever's responsible for the physical infrastructure to know, incase they've done something with the switches that can mess teaming up.
 
From outside your IPCOP box, telnet:25 the RED IPCOP NIC. Do you get a SMTP conversation?

If not, does IPCOP logs show that connection being blocked?

If its not being blocked, and youre not talking SMTP, then your Exchange server isnt communicating.

Are you sure your MX record for the mail domain is setup correctly? Does it resolve correctly when you ping it by name?
 
From outside your IPCOP box, telnet:25 the RED IPCOP NIC. Do you get a SMTP conversation?

If not, does IPCOP logs show that connection being blocked?

If its not being blocked, and youre not talking SMTP, then your Exchange server isnt communicating.

Are you sure your MX record for the mail domain is setup correctly? Does it resolve correctly when you ping it by name?

10/10 for reading the thread...

Also forgive me but IPCOP? MX records? Did you even read the problem?
 
To be honest exchange likely doesn't need the bandwidth so just put the NIC team in failover only mode, my experience is it's far more reliable, active/active teaming with LACP can be hit and miss...

Hit the nail on the head.

Always think about redundancy and resilience.

Is there any reason to team your nics?

Are you maxing out your gig(or 10/100) link?
 
Back
Top Bottom