Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange behind a firewall

Status
Not open for further replies.

MarkRobinson

Programmer
Feb 18, 2000
112
US
I believe I've Done everything right...

Per MS Knowledgebase Q155831, Q176466, & Q148732

I've opened the following ports:

135 - Exchange Control
110 & 25 for POP3/SMTP
143 & 993 for IMAP4
389 & 636 for LDAP
I edited the registry so that
System\CurrentControlSet\Services\MSExchangeDS\Parameters uses TCP/IP port 1300
System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem uses TCP/IP port 1301
System\CurrentControlSet\Services\MSExchangeSA\Parameters uses TCP/IP port 1302
opened 1300, 1301, and 1302 on the firewall

Configuration.

NT SErver with 2 Nic Cards
I have a static IP to which a WebRamp (combines modem bandwidth without MultilinkPPP) is Connected.
The Webramp is connected to NIC card 10.0.0.98
The Hub is connected to NIC card 10.0.0.2

Webramp has been told to open all the ports.

Wingate (Deerfield Communications) has been told to accept signals on the above ports from interface 10.0.0.98 and map them to the same ports on 10.0.0.2.

When I try an Outlook "Check Name" from outside (through the Internet) I see the Port activity on 135 in Wingate... then nothing else... and a get an error message on the Outlook Client that Network Problems are preventing....

PHEW... What a mess. Any Ideas??


 
From outside try telnetting to the Exchange server on port 25 using Exchange command line parameters
 
SMTP and POP work fine... no problem. I can send an receive e-mail normally.
The problem appears to have something to do with RCP... The RCPing diagnostic can't connect to the server.

 
Mark,
I dont know if this will help but MS knowledge base article q161931 talks about configuring port 102 for RPC communication also. Hope this helps.
Mark
 
Thanks, I opened Port 102... Still Nothing. RCP Ping doesnt seem to connect unless I do an Endpoint Search... Anybody know anything about RCP Ping?
 
Hi,
I have installed micrsoft exchange 2000 in my organization.
My server is having two NIC's one with private ip and another with public ip.It is lying behind the friwall PIX.
I have opened all the ports for the exchange i.e for public ip. But when i telnet the port 25 of the exchange it give me the output as shown below....
220 **********************************************************
******************************************
But when I telnet the same ip with port 25 behind the firwall it got connected easily.
kindly help me out.

Amit [sig][/sig]
 
This may not help you, but i have a question...why do you need "rcp"?

usually for mail you would just need 25 & 110. [sig]<p>Gordon R. Durgha<br><a href=mailto:gd@vslink.net>gd@vslink.net</a><br><a href= Link Networks, Inc</a><br>[/sig]
 
I'm not positive, but I believe that RCP will let me connect, not only to the echange SMTP/POP server, but allow me to be fully functional as an exchange user through the internet (public folders, etc).

May have found the problem... I had 2 NICS in the server and they were on the same subnet... it was causing problems. I change the subnet of one of the cards and will try the exchange stuff again.
[sig][/sig]
 
Mailboxes are associated with a NT account in the domain. How are you getting by this? You might want look into setting up Outlook Web Access.

Dan [sig][/sig]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top