Posted on 2004-10-04
I have a mail server running Windows 2003 Server Standard.
It has two network interface cards.
One I call the public interface (although it has a non-public IP assigned our FW does NAT/port forwarding to port 110 and 25)
192.168.2.2 INTEL PRO SERVER 10/100/1000 Adapter
The other interface I call the internal interface (also a non-public IP with Client for MS Networks/File Printer Sharing etc enabled.
192.168.1.61 NETGEAR FA311 adapter
There seems to be a problem with the NETGEAR interface. For one it seems to pass the MOST traffic (over a gig after days of being up). The problem is the interface will crap out intermittently. One day I'll come into the office and no one can get mail (since it's synced with AD for authentication). The interface never goes into status DISABLED or anything, but if I disable the interface then enable it again all works fine.
My question is this:
A. Can someone give me a script that will test the interface then disable and re-enable if the test fails to communicate over the adapter.
B. Help me determine why the interface goes down period.
C. My more liked option....
I want to assign another internal IP to my (external interface) so if interface one goes down we can still acess mail VIA interface 2.
I've already assigned another internal IP to interface (external). I've created another HOST in AD DNS to point to the mail server. Doing an NSLOOKUP provides 2 IP addresses for mail. So far so good.
The problem is....if I try to test by DISABLING the internal interface (192.168.1.61) I was under the impression that DNS should tell my mail clients that since the FIRST IP ADDRESS assigned to the mail server isn't responding, try the SECOND ONE. But that's not happening....how can I make that happen?