fox54
asked on
Exchange server behind firewall and MAPI client (Outlook)
I have a setup like this
Internet
|
Firewall A
|
LAN A Exchange server 2003
|
Firewall B
|
LAN B with users that wants to use Exchange in LAN A with Outlook as MAPI client
All communication from LAN B to LAN A are allowed
No communication from LAN A to LAN B are (or can be) allowed (LAN A is a sort of DMZ)
No budget for an Front-End and Back-End Exchange scenario
Is there a way to setup this thing ??
Internet
|
Firewall A
|
LAN A Exchange server 2003
|
Firewall B
|
LAN B with users that wants to use Exchange in LAN A with Outlook as MAPI client
All communication from LAN B to LAN A are allowed
No communication from LAN A to LAN B are (or can be) allowed (LAN A is a sort of DMZ)
No budget for an Front-End and Back-End Exchange scenario
Is there a way to setup this thing ??
How are people on Lan B going to know when they have mail if no communication goes from lan a to lan b?
Ok so you already have functioning domain Lan A. You want to add Domain B to Domain A's exchange server, but want to firewall between.
I highly doubt you can do this. You might be able to get the exchange server to work for multiple domains, but it was my understanding is that its limited to one domain [forest]. I could be wrong about this, I'm still learning as i always will.
I highly doubt you can do this. You might be able to get the exchange server to work for multiple domains, but it was my understanding is that its limited to one domain [forest]. I could be wrong about this, I'm still learning as i always will.
ASKER
For new mail, we'll plan a send/receive at intervals. Is it possible ?
Take a look at microsofts article on configuring static communication:
http://support.microsoft.com/kb/833799
If you already have the firewall A configured to traverse to the exchange, you should configure firewall B to traverse to the exchange the same way.
I'm guessing that you're hosting email for domains' A and B so the users will just authenticate to the exchange when they open outlook.
http://support.microsoft.com/kb/833799
If you already have the firewall A configured to traverse to the exchange, you should configure firewall B to traverse to the exchange the same way.
I'm guessing that you're hosting email for domains' A and B so the users will just authenticate to the exchange when they open outlook.
If this is Exchange 2003, then RPC over HTTPS would be the ideal choice. Runs over port 443 only and only requires the port to be open.
Simon.
Simon.
ASKER
As aktharchowdhury said
Yes, the Exchange will be hosting emails for domain A and domain B. User in Domain B just need to authenticate to Exchange. I guess we could save the credentials used to authenticate because password in domain A and passowird for users in domain B won't be in sync.
It's just that user in domain B wants all features of the Outlook/Exchange. I was wondering about users in domain B and Global catalog servers for the Global Adress List? Will all these features be available with RPC over HTTPS ?
Yes, the Exchange will be hosting emails for domain A and domain B. User in Domain B just need to authenticate to Exchange. I guess we could save the credentials used to authenticate because password in domain A and passowird for users in domain B won't be in sync.
It's just that user in domain B wants all features of the Outlook/Exchange. I was wondering about users in domain B and Global catalog servers for the Global Adress List? Will all these features be available with RPC over HTTPS ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
LAN A and LAN B are two different domains in two different forests