Just that Exchange 5.5 can't dynamically detect link state and reroute based on whether the connector is up or down. A Microsoft rep tells me that 2K is capable of detecting link state and rerouting to the connector that is up. Our plan is to use monitoring software until we upgrade to 2K to notify if the connector is down and I will have to manually reroute in the event I lose one of the IMC's. I have both IMCs in the same Exchange site. 2 IMC's were implemented mainly for redundancy. I'm not sure that our solution would work for you with your SMTP relay's in two different geographic locations but this is how we're configured: We have both SMTP servers in one site on a different subnet from the Exchange IMC's. They each have dual NICs. I used Network Load Balancing to configure a virtual IP address (1 NIC from each box answers to the load balanced address using the Network Load Balancing Service). I force all incoming traffic from each IMC as well as the traffic coming in from the internet through the firewall to the virtual address for the SMTP Relay. By placing my SMTP Relay servers on a different subnet than my Exchange servers and removing the gateway off the NICs that contain the virtual IP address, I was able isolate all incoming traffic to the virtual address and then use the other 2 NICs for outbound traffic by providing them with a default gateway. This allows a redundant configuration and easier troubleshooting since all traffic inbound to the SMTP relay that the receiver service picks up is traversing the virtual IP address and all my outbound traffic that the delivery service handles is using the integrated NIC's on my SMTP servers. I know that you can use a virtual address for your IMC because that's how I've done it here. I'm not sure if this helps you or not, but hopefully this information will give you something to go on... -----Original Message----- From: Dêniz Feital (Chiptek) [mailto:dfeital@xxxxxxxxxxxxx] Sent: Friday, October 11, 2002 2:28 PM To: [ExchangeList] Subject: [exchangelist] RE: RES: Using 2 IMC Servers and 2 SMTP Relay http://www.MSExchange.org/ Hi Sherri. Thanks for replying me. Well, what did you mean by "The best you can hope for is to detect the state of the connector and manually reconfigure to route to the other IMC". Also, Can I put a virtual ip address in my IMC? How do I configure two server answering for only one virtual IP address? I know this is not about Exchange, but... if you can help me, I will appreciate it. Thanks > Dêniz Feital > GIC - Chiptek / Vésper > Tel (11) 3489-7730 > Microsoft Certified Systems Engineer > > > -----Original Message----- From: Shorter, Sherri [mailto:sshorter@xxxxxxxx] Sent: Friday, October 11, 2002 3:24 PM To: [ExchangeList] Subject: [exchangelist] RE: RES: Using 2 IMC Servers and 2 SMTP Relay http://www.MSExchange.org/ I run two SMTP relay servers using Win 2K Advanced Server. These I have load balanced so I use one IP address to represent both servers providing automatic failover on these systems. I have two IMC's (same site configuration) on different servers but since Exchange 5.5 cannot dynamically detect link state, even setting routing calculation to "always" will not provide automatic fail over to the other IMC. The best you can hope for is to detect the state of the connector and manually reconfigure to route to the other IMC. My IMC's are both configured to forward all mail to the load balanced IP (virtual address) of the SMTP servers. On the SMTP servers, I pass to the Exchange IMC's with a cost. Assigning lower cost to the primary on each box and vice versa. -----Original Message----- From: Dêniz Feital (Chiptek) [mailto:dfeital@xxxxxxxxxxxxx] Sent: Friday, October 11, 2002 2:04 PM To: [ExchangeList] Subject: [exchangelist] RE: RES: Using 2 IMC Servers and 2 SMTP Relay http://www.MSExchange.org/ Oh I am sorry, I forgot to tell you !! Exchange 5.5 Service Pack 4. Thanks > Dêniz Feital > GIC - Chiptek / Vésper > Tel (11) 3489-7730 > Microsoft Certified Systems Engineer > > > -----Original Message----- From: Alex Decarli [mailto:decarli@xxxxxxxxxxxxx] Sent: Friday, October 11, 2002 3:03 PM To: [ExchangeList] Subject: [exchangelist] RES: Using 2 IMC Servers and 2 SMTP Relay http://www.MSExchange.org/ what are the exchange versions ? -----Mensagem original----- De: Dêniz Feital (Chiptek) [mailto:dfeital@xxxxxxxxxxxxx] Enviada em: sexta-feira, 11 de outubro de 2002 14:46 Para: [ExchangeList] Assunto: [exchangelist] Using 2 IMC Servers and 2 SMTP Relay http://www.MSExchange.org/ Hi everyone. I have a question about IMC and SMTP Relay. I am doing some changes in my Exchange Organization. In the future, it will have 2 sites, 2 imc and 2 smtp relay, These sites will be in diferent geografic locations. I am planning to put one imc in each site, and one smtp relay for each site as well, in a dmz zone. My question is: I want users from site A use as much as they can the imc in site A and this imc in site A use as much as it can the smtp relay in site A. The same thing for site B. If one smtp relay falls, the imc should use the smtp relay in the other site. I think I know how to do it about users using the first imc, but I am not sure how to do it for imc use one smtp relay and if the smtp relay is down, it must to use the second smtp relay, instead of waiting for the first one go up again. I know I should use dns instead of ip address in imc, connections, message delivery, but how to do it? Should I creat a fqdn for both smtp relays, using A record? Which is my garantee the site one will always use the first smtp relay, instead of using one of them each time? I am kind of confused here. Any ideas? Thanks All imc = Internet Mail Connector > Dêniz Feital > GIC - Chiptek / Vésper > Tel (11) 3489-7730 > Microsoft Certified Systems Engineer ******************************************************** This message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. If you have received this message in error please notify the Postmaster@xxxxxxxxx The unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden. *********************************************************