Port Forwarding for Exchange?

Hi Everybody!

I have an MN-700 here in an .org along with an Exchange 2003 SP1 server
(running on Windows 2003, 'natch - with all the available updates).
Exchange works perfectly when I place it in a "virtual DMZ" but I'm a wary
of keeping it there as this is a small satellite office (3 users) and the
server is also their DC and file server.

I've tried forwarding ports 25, 80 and 110 to the Exchange server
(192.168.1.3) but when in this configuration mail can go out but not come
in. I receive no error message from Yahoo! or Hotmail when I send an email
to the server and the messages appear to just fall into a digital black
hole.

Is there any way to just use some kind of port-forwarding to get this to
work?? I've read some guides on this from various sources via Google but
these extremely complex and were mostly for Exchange 5.5 and 2000.

Thank you,

Jim

Try looking here (which was found by Googling for "exchange ports")

http://www.techtutorials.com/tutoria...ge/ports.shtml

It seems that you might not be port forwarding all the appropriate ports for
Exchange (and note that there might be subtle differences for Exchange 2003
too for all I know).

HTH

[You may also want to chase that aspect in a newsgroup that is dedicated to
Exchange - for example, the ones on MS's news server]

Kerry Liles

"Jim Cofer" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi Everybody!
>
> I have an MN-700 here in an .org along with an Exchange 2003 SP1 server
> (running on Windows 2003, 'natch - with all the available updates).
> Exchange works perfectly when I place it in a "virtual DMZ" but I'm a wary
> of keeping it there as this is a small satellite office (3 users) and the
> server is also their DC and file server.
>
> I've tried forwarding ports 25, 80 and 110 to the Exchange server
> (192.168.1.3) but when in this configuration mail can go out but not come
> in. I receive no error message from Yahoo! or Hotmail when I send an
email
> to the server and the messages appear to just fall into a digital black
> hole.
>
> Is there any way to just use some kind of port-forwarding to get this to
> work?? I've read some guides on this from various sources via Google but
> these extremely complex and were mostly for Exchange 5.5 and 2000.
>
> Thank you,
>
> Jim
>
>
>

I have the same setup at here (Exchange 2003 + Windows
2003 + MN-700) and the only portfowarding I have is 25).
Mail flows in and out with no problems.

I have the ;atest firmware for MN700 as well.

I might be wrong, but maybe your config for portforwarding
is not right, or you have a firmware version in MN700 that
doesn't work well with portforwarding.

Hop this helps,

Movedor

>-----Original Message-----
>Try looking here (which was found by Googling
for "exchange ports")
>
>http://www.techtutorials.com/tutoria...nge/ports.shtm
l
>
>It seems that you might not be port forwarding all the
appropriate ports for
>Exchange (and note that there might be subtle differences
for Exchange 2003
>too for all I know).
>
>HTH
>
>[You may also want to chase that aspect in a newsgroup
that is dedicated to
>Exchange - for example, the ones on MS's news server]
>
>Kerry Liles
>
>"Jim Cofer" <(E-Mail Removed)> wrote in message
>news:%(E-Mail Removed)...
>> Hi Everybody!
>>
>> I have an MN-700 here in an .org along with an Exchange
2003 SP1 server
>> (running on Windows 2003, 'natch - with all the
available updates).
>> Exchange works perfectly when I place it in a "virtual
DMZ" but I'm a wary
>> of keeping it there as this is a small satellite office
(3 users) and the
>> server is also their DC and file server.
>>
>> I've tried forwarding ports 25, 80 and 110 to the
Exchange server
>> (192.168.1.3) but when in this configuration mail can
go out but not come
>> in. I receive no error message from Yahoo! or Hotmail
when I send an
>email
>> to the server and the messages appear to just fall into
a digital black
>> hole.
>>
>> Is there any way to just use some kind of port-
forwarding to get this to
>> work?? I've read some guides on this from various
sources via Google but
>> these extremely complex and were mostly for Exchange
5.5 and 2000.
>>
>> Thank you,
>>
>> Jim
>>
>>
>>
>
>
>.
>