• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

looking for exchange administrators

You usually don't have to ask first, just ask away and subscribe to your post to receive email notification whenever someone responds. 🙂
 
Can someone tell me what ports need to be opened in order to use exchange. I was told by a teacher that exchange uses its on propertitary protocal which communicated on its on tcp port.
 
unless your trying to run ALL of exchange stuff over the internet, in which case it needs a whole slew of ports....

Dont do it this way
 
Let me guess, you have an exchange server behind a router and the dynamic ports it is trying to use is not letting it communicate through? Search the Microsoft Knowledge Base for Exchange behind a firewall, as you will need to edit your exchange server registry and set non-dynamic ports instead of letting the server dyanmically created ones in the 1025 and greater range.
 
Now for my question regarding exchange server, does anyone know how to keep it from timing out connections to clients on the WAN?
 
It really depends on a few things.

1) Exchange 2000 or 5.5
2) Using SMTP, POP3 and IMAP?
3) Using OWA?
4) Is the server in a DMZ?

If you put a Exch 2000 server on a DMZ, you're looking at a world of headaches. It can be done, but it really negates the entire concept of a DMZ. You will need to open ports for things like Kerberos, LDAP, etc so that the Exchange box can communicate with the Active Directory.
I've had alot of success using an SMTP relay in a DMZ situation. It accepts mail in the DMZ on behalf of the Exchange server, located in the private network. It content checks and blocks spam, then passes it along. Works well and saves the headaces. Even the IIS SMTP server will do this well enough, just make sure it isnt an open relay.

If it's just behind a router, on the same network as a DC, then open 25 (SMTP) both ways to allow incoming/outgoing mail. Make sure it has a way to resolve internet names, and that it can be resolved on the internet itself. ( Map mail.yourdomain.com to the external ip of your router) That's the simplest way to do it.

Exchange uses SMTP by default, which is an RFC standard and non-propriatary. It can use POP3, IMAP, etc as well (most of which allow clients to retrieve mail only). SMTP is still used to send in this case.

The simplest way to do it is to use SMTP for everything.
 
Back
Top