Link to home
Avatar of Tencha
Tencha

asked on

Exchange 2007 Static ports

I'm having a problem with a remote location with a domain trust between us not being able to communicate with my exchange sever, there is a firewall between us and with out opening all the exchange dynamic port after the contact with exchange using port 135, I was told that setting static port is what is need to do on my exchange server (within the registry) . Can anyone help and explain how to do so? Also, does anyone have a different work around? Every time I reboot the ports change and the remote location and no longer use outlook client (though OWA does work).
Avatar of endital1097
endital1097
Flag of United States of America image

i would configure the remote clients to use outlook anywhere which only requires port 443
Avatar of btdownloads7
Outlook anywhere will work, but it's a pain to set up. you can set up VPN access to the server, then set up Outlook to connect to the exchange server over LAN (just use the local IP or machine name for the server). Whenever the machine is actually on the LAN, it will connect just fine. Whenever it's outside the LAN connecting over the internet, you will have to connect to the VPN first, and then Outlook will connect easily.

The only port you'll have to forward on the router is 1723 to the server for the PPTP VPN connecton.
ASKER CERTIFIED SOLUTION
Avatar of flaphead_com
flaphead_com
Flag of United Kingdom of Great Britain and Northern Ireland image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Any joy?
If I  understand correctly, you have two domains, with a 1-way or 2-way trust setup between the two domains. In addition, you have a firewall between the two domains. Exchange is setup in one domain, and your outlook clients live in the other domain.

The firewall is blocking Netbios packets, which is preventing Outlook.exe from logging into Exchange.

Assuming this is the only problem you are having (which is not likely the case, the trust relationship is failing miserably unless you've set the RPC endpoints for Netlogin and server processes), then the easy solution is to configure your Outlook profiles to use RPC over HTTPS (now called "Outlook Anywhere" in Exchange 07.  You'll need a valid SSL cert and some powershelling, get autodiscover working so your Outlook 2007 clients just "go" and you'll solve the Outlook to Exchange problem.  However, the trust between the two domains (if it is necessary) needs some port mapping as well.
If this firewall is between two LANs with no Internet between them then get rid of the Firewall and replace it with a LAN Router.  It is going to be nothing but "in the way" for everything.  If you think that a firewall is the only security that exists then you are in trouble.  Your security comes from the natural access control abilities within Active Directory and within the Applications that are being used.  LAN Routers can also use ACLs for Layer3&4 if you still need those afterwards.
Avatar of Tencha
Tencha

ASKER

After reading all the doc.s  and appling the solution, things worked perfect!