Skip to content

xchange 2003 public facing server help

Featured Replies

right one of the directors has just got a nokia 9300 and wants to be able to get emails on it from our exchange 2003 server problem is our server is hidden behind our fire wall.

so i would say we need a public facing exchange server right ?

and if i did that it shouldnt be our existing mail server for security reasons right ?

so i would need to put in a front end backend exchange setup so you connect to the public frontend server that then passes the request onto the secure backend server right ?

so id like to know whats the best way to do this if not the way above as my balls really are on the line over this so it has to go right first time.

please help

mike

Do you not just forward a couple of ports on your firewall? Im sure that's all my guys did for ours and we had our Exchange03 server working behind a firewall but mobile devices connecting and downloading email.

  • Author

yeah but that way people can also abuse it so i beleive but im not sure i kind of want to make this hard to do lol so i can get out of doing it at the moment :D

We are doing this at work.

Install frontend exchange server. This server will just be a an install of exchange 2003, the server will contain no mailboxes. The server needs to be a member of your AD domain for this to work. I have pasted below an extract from an MS KB article.

...

Between the DMZ and the internal network the Exchange front-end server needs to be able to connect to some ports on the Exchange mailbox server and some domain controllers and DNS servers.

The front-end server needs to be able to connect to TCP ports 80 and 691 on the Exchange mailbox server.

It also needs to be able to send to the following ports on domain controllers and DNS servers.

TCP and UDP port 53

TCP and UDP port 88

TCP port 135

TCP and UDP port 389

TCP port 3268

TCP port 1026

You must also set the following registry entries on your front-end server OTHERWISE IT WON't WORK:

Note: You should now configure the DSAccess service for perimeter networks on your Frontend Server. At first you should disable the check for available disk space at netlogon by using RPC. This can be done by changing the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess

Registry Value: DisableNetlogonCheck

Value Type: REG_DWORD

Value Data: 1

In addition to this you should prevent DSAccess from pinging domain controllers. This can be done by creating the following key on your Frontend Server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess

Registry Value: LdapKeepAliveSecs

Value Type: REG_DWORD

Value Data: 0

Note: You can limit RPCs across the firewall by editing the registry of all your DCs. You should now change the registry setting of the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

Registry Value: TCP/IP Port

Value Type: REG_DWORD

Value Data: 1026

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.