This site is great. I am learning a lot from it and I have only been registered today.
I have the ISA Server 2004 book. I am pretty clear on publishing a second mail server and needing the second public IP address to do so. I have four usable Static Public IP's available and we use PPPoE to connect to our ISP using the connection manager in SBS2003 to do it. I have posted several questions without any firm answer on how to bind the second ip address so I can use ISA to publish the second mail server. If my first statuc public ip is XXX.XXX.XXX.29 (the one we have used for 8 years now) and we have XXX.XXX.XXX.30 available to us to use, how do I bind it? Right now the ISP says that the XXX.XXX.XXX.30 is coming to me through the current PPPoE connection but my server just discards it because it knows nothing about it?
Is this true and how do I bind it if it is.
My infrastructure is Internet>Bridged Modem>SBS2003 with ISA 2004>Internal Network
Posts: 2228
Joined: 12.Apr.2004
From: Taylorville, IL
Status: offline
You just add it to the IP Specs of the external Nic (the "Advanced button"),...then select the IP from in the Publishing Rule.
But keep in mind that outbound mail comming from the second mail server will show comming from the same IP as the first mail server. Secondary IP#s are only used in the inbound direction,...never the outbound direction. It is the way it is,..you cannot change that.
Generally people never run two mail servers from behind the same ISA. Most of the time two mail server is not even the right approach. A single Mail server can handle multiple Mail Domains.
Posts: 2228
Joined: 12.Apr.2004
From: Taylorville, IL
Status: offline
You're not most people I suppose,...in fact I am sure you are not.
You probably also know how to create the right kind of environment so that it does not matter if all the outbound mail traffic shows comming from the same Primary External IP# of the ISA.
"Most people" in your world are probably different then "most people" in mine. In my world I've been in the TV industry for about 10 years and been involved directly or indirectly in over 40 TV Stations,...far to many of them run their facilities like a home user network with a DSL or CableTV line. Their "IT guy" is often a broadcast engineer that was deemed "good with computers" and their concept of a "firewall" is a "hardware firewall" that you "open ports" on to make it work. None of them would ever conceive of running multiple mail servers or would ever understand there proper circumstances when you should. Their eyes glaze over when I mention ISA, and they think "...but it runs on Windows?!"
That's my world,...probably why I'm so grumbly at times.
Posts: 2228
Joined: 12.Apr.2004
From: Taylorville, IL
Status: offline
Some of our sister stations had more channels than that and it was done with a single Exchange box that handled all the mail domains. That was WISH in Indianapolis when we were owned by a previous parent company.
We run 2 channels but due to the way it is arranged it does not have separate call letters. It is just WAND 17.1 and WAND 17.2. Before digital broadcasting came along the second one was a "cable-only" channel. So I only have one mail domain.
Posts: 2228
Joined: 12.Apr.2004
From: Taylorville, IL
Status: offline
I had some problems with ISA and the NBC's VOD box streaming video from the affiliate to the NBC Network. If you were dealing with the NBC affiliate you may have dealt with it. But if they are using a "hardware" firewall instead of ISA then you would not have run into it.
But we shouldn't hyjack this poor guy's thread anymore than we have.