Re: Ports for Exchange 2003 and 2007 Coexistence

On Fri, 8 Jun 2007 10:47:50 -0400, "Glaze, Christopher"
<glazecj.nojunkmailplease@xxxxxxxxxxxxxxxxxxx> wrote:

Good morning everyone,

Here is my setup.

* exch2003 - Production Exchange 2003 server on the DMZ. I inherited this
server. This was setup as a test system and was never meant for production,
so it has issues, software and hardware.
* exch2007cas - Exchange 2007 server with CAS on the internal network
* exch2007mb - Exchange 2007 server with Hub and Mailbox on the internal
network, server not set up yet
* isa2006 - ISA 2006 for OWA and ActiveSync
* dc1, dc2 - Active Directory and internal DNS.

My original plan was to move exch2003 to the internal network and use
isa2006 to publish OWA and ActiveSync. However, I ran into issues getting
ActiveSync to work through ISA. This would be a showstopper as the higher
ups use ActiveSync. OWA from isa2006 to exch2003 works fine.

Now, I'm leaning towards leaving exch2003 alone and to start setting up
exch2007mb. I want to move a select few mailboxes from exch2003 to
exch2007mb and test out OWA and ActiveSync before moving everyone else and
throwing exch2003 out the window.

My question is, what ports need to be opened through the PIX between
exch2003 and exch2007cas, exch2007mb, dc1, or dc2 to ensure proper
functionality? We have 53, 88, and 3268 from exch2003 to dc1 and dc2 open.
I know that 25 needs to be opened from exch2003 to exch2007mb for proper
mail flow. I haven't been able to find any other ports that could be
necessary. I would think 135 for RPC would be necessary but All the
documentation and articles I have read assume a proper setup of Exchange
2003 on an internal network.

Thanks in advance!

I would just let 443 through the firewall and move the Exchange box
into the internal network. That lets you keep safe using the ISA,
takes the ActiveSync problem away and eliminates your ports problem.

Don't go messing about with the ports, you'll only end up with the bad
people crawling all over your network.
.

Relevant Pages

  • Re: Ports for Exchange 2003 and 2007 Coexistence
    ... Open 443 through the PIX to exch2003 for ActiveSync. ... My original plan was to move exch2003 to the internal network and use ... what ports need to be opened through the PIX between ...
    (microsoft.public.exchange.setup)
  • Re: Activesync 4.1 can not see my USB Mobile PC
    ... a hard reset and then attempting to setup the partnership. ... ActiveSync 4.x Troubleshooting Guide - ... Plug and play pop up that a mobile PC has been plugged into USB. ... jsut keeps scanning ports and telling me my USB and com ports are ...
    (microsoft.public.pocketpc.activesync)
  • Re: Axim X5, WM2003, AS 4.1 - constant, random, over and over and over disconnects
    ... > your desktop computer and run Setup again. ... Restart your desktop computer and run Setup again. ... > This problem seems to plague all newer versions of Microsoft ActiveSync ... still no joy - it just WILL NOT INSTALL!! ...
    (microsoft.public.pocketpc)
  • Re: Windows 2003 network drop problem.
    ... > cards, and as stated previously, wonder what would happen if you could ... > disable the one not facing the internal network. ... I've setup at least 30 servers over the years and never had any problems ... other than fail NIC's, poorly configured protocols, or other configuration ...
    (microsoft.public.win2000.networking)
  • RE: Free BSD & Heartbeat + Samba + Rsync
    ... > Rob - ... My setup is fairly simple, a couple of minor points regarding what I set ... I had a couple of spare machines and some 250Gig IDE hds so I ... NIc to the internal network. ...
    (freebsd-questions)
Quantcast