This post provides Windows Server 2008 Security Guide. This guide provides instructions and recommendations to help strengthen the security of computers running Windows Server® 2008 that are members of an Active Directory® domain.
In addition to the guidance that the Windows Server 2008 Security Guide prescribes, this Solution Accelerator provides tools, step-by-step procedures, recommendations, and processes that significantly streamline the deployment process. This guide not only provides you with effective security setting guidance. It also provides you with a reproducible method that you can use to apply the guidance to both test and production environments.
The key tool that this Solution Accelerator provides for you is the GPOAccelerator. The tool enables you to run a script that automatically creates all the Group Policy objects (GPOs) you need to apply this security guidance. The Windows Server 2008 Security Guide Settings workbook that accompanies this guide provides another resource that you can use to compare and evaluate the Group Policy settings.
Microsoft engineering teams, consultants, support engineers, partners, and customers have reviewed and approved this prescriptive guidance to make it:
• Proven. Based on field experience.
• Authoritative. Offers the best advice available.
• Accurate. Technically validated and tested.
• Actionable. Provides the steps to success.
• Relevant. Addresses real-world security concerns.
Microsoft has published security guides for Windows Server 2003 and Windows 2000 Server. This guide references significant security enhancements in Windows Server 2008. The guide was developed and tested with computers running Windows Server 2008 joined to a domain that uses Active Directory® Domain Services (AD°DS).
Tuesday, October 13, 2009
Tuesday, October 6, 2009
Exchange Server Support for Backups and Single Item Recovery
Naturally after understanding the features included in Exchange 2010, a logical follow up question is "Do I still need backups for single item recovery?" The answer depends on your backup requirements and your capacity planning.
Today many customers minimize the deleted item retention window, yet they maintain long backup retention time periods (from 14 days to several months to years).
Let's consider a customer that currently maintains backups for 90 days and only retains deleted items within Exchange for 5 days. This customer is performing backup restores on a weekly basis to recover deleted items for end users. If the customer moved to Exchange 2010 they could move that process into Exchange by simply increasing their mailboxes capacity for dumpster: This post Contain the exchange server support tips to make backups and single Item Recovery.
o For Purges:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * 50KB ? 318MB
o For Versions:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * .1 = 650 emails
+ 650 emails * 50KB ? 32MB
o Total Space Required per mailbox: 350MB
By increasing each mailbox's capacity by a minimum of 350MB, backups are no longer needed for single item recovery. Single item recovery can be maintained and performed within Exchange.
But let's not stop there. What if the requirement is that items must be recoverable for 1 year? Assuming the same assumptions used in the previous example with the exception that deleted item retention is now configured for 365 days, each mailbox needs an additional minimum 1.4GB of space.
Ultimately, if the storage subsystem is planned and designed appropriately and mailbox resiliency features are leveraged, traditional point-in-time backups can be relegated to a disaster recovery mechanism, if they are even needed at all.
Today many customers minimize the deleted item retention window, yet they maintain long backup retention time periods (from 14 days to several months to years).
Let's consider a customer that currently maintains backups for 90 days and only retains deleted items within Exchange for 5 days. This customer is performing backup restores on a weekly basis to recover deleted items for end users. If the customer moved to Exchange 2010 they could move that process into Exchange by simply increasing their mailboxes capacity for dumpster: This post Contain the exchange server support tips to make backups and single Item Recovery.
- Users send/receive 100 messages per work day and have an average message size of 50KB
- Single Item Recovery is enabled and the deleted retention window is configured to be 90 days
- 10% of items are edited
- Mailbox capacity calculations
o For Purges:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * 50KB ? 318MB
o For Versions:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * .1 = 650 emails
+ 650 emails * 50KB ? 32MB
o Total Space Required per mailbox: 350MB
By increasing each mailbox's capacity by a minimum of 350MB, backups are no longer needed for single item recovery. Single item recovery can be maintained and performed within Exchange.
But let's not stop there. What if the requirement is that items must be recoverable for 1 year? Assuming the same assumptions used in the previous example with the exception that deleted item retention is now configured for 365 days, each mailbox needs an additional minimum 1.4GB of space.
Ultimately, if the storage subsystem is planned and designed appropriately and mailbox resiliency features are leveraged, traditional point-in-time backups can be relegated to a disaster recovery mechanism, if they are even needed at all.
Monday, September 28, 2009
How Managed Exchange Can Increase Your Business?
Managed Exchange can help your business by converting Microsoft Outlook from an email communication device into a critical work tool. Get Better access to critical and frequently used information, Book or reserve popular shared company resources and Coordinate your daily schedules through personal calendar tools by Managed Exchange.
Staff can access their email and Outlook work tools (mentioned above) through a number of web-enabled devices such as: Desktop PCs, laptops, PDAs with GPRS, WAP mobile phones with GPRS, Blackberry mobile devices with GPRS. Data is constantly synchronized and updated, so no matter how staffs access their work tools, they always have the most up-to-date information when online. It helps staff be more organized and get more out of their day.
Managed Exchange is ideal for any business whose staffs need to work together using frequently shared information and need to have flexible access to critical work tools such as email, contacts and calendar when they cannot make it into the office.
Service providers Managed Exchange Solution allows smaller businesses to leverage all of the functionality of Microsoft Exchange, without having to cover the associated capital and operating costs associated with running an Exchange Server in-house. Managed Exchange is also suitable for small businesses with limited IT resources because all service providers are able to manage the back-end for you.
Your Managed Exchange service can generally be activated within one business day. For larger, customized configurations, service provider will arrange with you a suitable timeframe for activation of your service. You can get protection from spam, viruses and malware before they reach your network. No software, hardware or user training required.
Staff can access their email and Outlook work tools (mentioned above) through a number of web-enabled devices such as: Desktop PCs, laptops, PDAs with GPRS, WAP mobile phones with GPRS, Blackberry mobile devices with GPRS. Data is constantly synchronized and updated, so no matter how staffs access their work tools, they always have the most up-to-date information when online. It helps staff be more organized and get more out of their day.
Managed Exchange is ideal for any business whose staffs need to work together using frequently shared information and need to have flexible access to critical work tools such as email, contacts and calendar when they cannot make it into the office.
Service providers Managed Exchange Solution allows smaller businesses to leverage all of the functionality of Microsoft Exchange, without having to cover the associated capital and operating costs associated with running an Exchange Server in-house. Managed Exchange is also suitable for small businesses with limited IT resources because all service providers are able to manage the back-end for you.
Your Managed Exchange service can generally be activated within one business day. For larger, customized configurations, service provider will arrange with you a suitable timeframe for activation of your service. You can get protection from spam, viruses and malware before they reach your network. No software, hardware or user training required.
Monday, September 14, 2009
How To Resolve OST Synchronization Error
In Microsoft Outlook, an offline folder (.ost file) is a locally stored file that is synchronized with your mailbox contents stored on Microsoft Exchange Server. The folders empower you to access them even when the mail delivery or network service is not available. The file converts into a usable .pst file as the synchronization process succeeds. But there can be several synchronization errors, due to which your .ost file might become unusable. In such cases, you might need to restore its contents from a backup stored as a .pst file. If it is not feasible, you should use a third-party tool to Convert OST to PST.
For an instance, you use Microsoft Outlook 2002 or 2003 with an offline folder. You press F9 to synchronize your .ost file with your Exchange Server mailbox, but fail to do so and come across the below error message:
If you close the application and try to perform synchronization again, you receive the same error message.
The Reason:
As the error message suggests, this error is encountered if you are attempting to synchronize the mailbox with an .ost file that is configured to use a different server or e-mail account. This usually occurs if you perform these steps in order:
You synchronize your .ost file with the mailbox 2-You perform some changes in name of either e-mail server or mailbox in your email account profile.
Doing so makes the current .ost file unusable.
Best Possible Solution
Create a new email profile with the desired account settings and restore data using any of the below solution:
Convert OST to PST are powerful applications that are competent to convert an usable .ost file into a usable .pst file after any type of crash.
Stellar Phoenix Mailbox Exchange Desktop is an effective utility that converts an .ost file into a .pst file. It can Convert OST by maintaining data integrity. Designed to perform safe file conversion, this utility can restore all file objects including emails, notes, journals, tasks and more. It is compatible with Outlook 2003, 2002, 2000, 98 and 97.
For an instance, you use Microsoft Outlook 2002 or 2003 with an offline folder. You press F9 to synchronize your .ost file with your Exchange Server mailbox, but fail to do so and come across the below error message:
"The file.ost cannot be accessed because it has been configured for use with a different mailbox."
If you close the application and try to perform synchronization again, you receive the same error message.
The Reason:
As the error message suggests, this error is encountered if you are attempting to synchronize the mailbox with an .ost file that is configured to use a different server or e-mail account. This usually occurs if you perform these steps in order:
You synchronize your .ost file with the mailbox 2-You perform some changes in name of either e-mail server or mailbox in your email account profile.
Doing so makes the current .ost file unusable.
Best Possible Solution
Create a new email profile with the desired account settings and restore data using any of the below solution:
- You can then include the .pst files maintained as a backup of previous .ost file.
- You can also copy this information to a .pst file from your mailbox after changing the changed email settings back to the original state.
- If applying the above solutions are not possible, Convert OST to a usable .pst file.
Convert OST to PST are powerful applications that are competent to convert an usable .ost file into a usable .pst file after any type of crash.
Stellar Phoenix Mailbox Exchange Desktop is an effective utility that converts an .ost file into a .pst file. It can Convert OST by maintaining data integrity. Designed to perform safe file conversion, this utility can restore all file objects including emails, notes, journals, tasks and more. It is compatible with Outlook 2003, 2002, 2000, 98 and 97.
Tuesday, August 25, 2009
Benefits of Small Business Server Exchange 2003
Microsoft small business server 2003 is designed for organizations with up to 50 computers who need high-level reliability and functionality but don't have the economy of scale that allows big corporations to sop up the cost and complexity of licensing best-of-breed enterprise software. SBS 2003 is a cost effective and simple way to form a solid foundation for an information network with enterprise-level security, connectivity, performance, and reliability.
Windows SBS 2003 will be available in standard and premium editions. The standard edition includes Microsoft SBS 2003 and window server 2003. Small business server 2000 included earlier versions of these products. The premium edition adds Microsoft SQL Server 2000 and Microsoft Internet Security and Accelerations Server.
Advantages of Microsoft Small Business Server 2003 include:
Windows SBS 2003 will be available in standard and premium editions. The standard edition includes Microsoft SBS 2003 and window server 2003. Small business server 2000 included earlier versions of these products. The premium edition adds Microsoft SQL Server 2000 and Microsoft Internet Security and Accelerations Server.
Advantages of Microsoft Small Business Server 2003 include:
- Windows 2003 server management and security tools deduct the cost and enhance the dependability of desktop computers by using centralized user policies, rights and configurations.
- SBS exchange 2003 enhances remote and mobile access by supporting a web client that offers a nearly full implementation of the familiar outlook interface, including calendaring and tools. It means that mobile workers can have complete, secure access to email from any internet-connected computer with a standard web browser.
- Windows SBS server 2003 maximizes server uptime and user availability by incorporating powerful fault tolerance aspects, including disk mirroring, cluster configurations, and distributed file system.
- SBS exchange 2003 uses active directory, providing a greatly simplified administration and security model. It makes exchange server monitoring very easy and also offers complete security. Security enhancements include improved safe and block lists and junk email filtering, public folder permission enhancements and attachment in MOOWA (Microsoft Office Outlook Web Access).
- ISA server features ideal support for protecting IIS servers behind the firewall, which have been the largest areas of hacker exploits for windows 2000 environments.
Sunday, August 16, 2009
Microsoft Exchange Server Troubleshooting
The Windows Exchange Server software suite is developed and supported by Microsoft. Microsoft Exchange is used to download, manage and organize email, contact data and calendars on a server network. The Windows-based Exchange server is also often used for mobile data, such as email on a smartphone. Occasionally, errors may be encountered when working within the Exchange framework. Learn how to troubleshoot the Windows Exchange Server network to identify problems and restore your Exchange server's functionality.
You can troubleshoot the exchange server very easily and efficiently with the following given steps;
If you still unable to resolve the issue, please login at http://www.iyogibusiness.com
You can troubleshoot the exchange server very easily and efficiently with the following given steps;
- Restart the computer or mobile device with which you are trying to access the Microsoft Exchange server. Occasionally, the issue may be due to software or hardware problems that interrupt the data transfer between the device and the server. These issues can often be easily solved by shutting down the hardware and rebooting the operating system. On a computer, click the "Start" menu and select "Shutdown" or "Restart." On a mobile device, press and hold down the power button or consult the manufacturer's manual.
- Launch Internet Explorer. Visit the Microsoft Exchange support website. See the Resources section below for a link. Read the list of "Top Issues" published on the top of the web page. This list catalogs all current issues and problems that may be experienced by Exchange users, as well as solutions to the errors. Also, check that all Exchange patches and upgrades have been installed on the server. If you are a businessperson trying to access your company's Exchange server, you typically would not have permission to install upgrades. Contact your company's IT department for assistance in keeping your Exchange products synced with the latest Microsoft Exchange upgrades.
- Download the official "Microsoft Exchange Troubleshooting Assistant." This program is developed and hosted by Microsoft specifically to pinpoint critical problems on an Exchange server and guide you through fixing the problem. Visit the Microsoft Exchange Troubleshooting Assistant website and click the "Download" button. See the Resources section for a link.
- Click "Save" in the dialog box that pops up in the Internet Explorer browser. Wait for the download to finish before closing the browser. Depending on the speed of your Internet connection, this may take several minutes.
- Double-click the "Microsoft Exchange Troubleshooting Assistant" icon on your computer desktop to begin the automated installation process. An installation wizard will appear to guide you through the process. Follow the on-screen prompts to complete the installation.
- Open the "Microsoft Exchange Troubleshooting Assistant" by clicking the "Start" menu and selecting the program from the pop-up menu. Run the Troubleshooting Assistant and wait for it to generate a report on the status of your Exchange server. The Assistant will scan both the local machine and the server to determine where any potential problems may exist. If it identifies a problem, the assistant will give you a report on how to successfully solve the problem and fix the issue.
If you still unable to resolve the issue, please login at http://www.iyogibusiness.com
Tuesday, June 30, 2009
Ports used by Exchange Server
For purposes of configuring firewalls or for troubleshooting communications issues, it may be useful to know what TCP/UDP ports Exchange 2000 Server and Exchange 2000 Conferencing Server are using. This article is also true for Exchange Server 2003 installations.
Protocol: LDAP
* Port (TCP/UDP): 389 (TCP)
Description: Lightweight Directory Access Protocol (LDAP), used by Active Directory, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory.
Protocol: LDAP/SSL
* Port (TCP/UDP): 636 (TCP)
* Description: LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted.
* To enable SSL, you must install a Computer certificate on the domain controller or Exchange Server 5.5 computer.
Protocol: LDAP
* Port (TCP/UDP): 379 (TCP)
* Description: The Site Replication Service (SRS) uses TCP port 379.
Protocol: LDAP
* Port (TCP/UDP): 390 (TCP)
* Description: While not a standard LDAP port, TCP port 390 is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on a Microsoft Windows 2000 Active Directory domain controller.
Protocol: LDAP
*Port (TCP/UDP): 3268 (TCP)
* Description: Global catalog. The Windows 2000 Active Directory global catalog (which is really a domain controller "role") listens on TCP port 3268. When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP.
Protocol: LDAP/SSL
*Port (TCP/UDP): 3269 (TCP)
*Description: Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data. To configure a global catalog to support SSL, you must install a Computer certificate on the global catalog.
Protocol: IMAP4
*Port (TCP/UDP): 143 (TCP)
*Description: Internet Message Access Protocol version 4, may be used by "standards-based" clients such as Microsoft Outlook Express or Netscape Communicator to access the e-mail server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service (Inetinfo.exe), and enables client access to the Exchange 2000 information store.
Protocol: IMAP4/SSL
*Port (TCP/UDP): 993 (TCP)
*Description: IMAP4 over SSL uses TCP port 993. Before an Exchange 2000 server supports IMAP4 (or any other protocol) over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: POP3
*Port (TCP/UDP): 110 (TCP)
*Description: Post Office Protocol version 3, enables "standards-based" clients such as Outlook Express or Netscape Communicator to access the e-mail server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange 2000 information store.
Protocol: POP3/SSL
*Port (TCP/UDP): 995 (TCP)
*Description: POP3 over SSL. To enable POP3 over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: NNTP
*Port (TCP/UDP): 119 (TCP)
*Description: Network News Transport Protocol, sometimes called Usenet protocol, enables "standards-based" client access to public folders in the information store. As with IMAP4 and POP3, NNTP is dependent on the IIS Admin Service.
Protocol: NNTP/SSL
Port (TCP/UDP): 563 (TCP)
Description: NNTP over SSL. To enable NNTP over SSL, you must install a Computer certificate on the Exchange 2000 Server.
Protocol: HTTP
*Port (TCP/UDP): 80 (TCP)
*Description: Hyper-Text Transfer Protocol is the protocol used primarily by Microsoft Outlook Web Access (OWA), but also enables some administrative actions in Exchange System Manager. HTTP is implemented through the World Wide Web Publishing Service (W3Svc), and runs on top of the IIS Admin Service.
Protocol: HTTP/SSL
*Port (TCP/UDP): 443 (TCP)
*Description: HTTP over SSL. To enable HTTP over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: SMTP
*Port (TCP/UDP): 25 (TCP)
*Description: Simple Mail Transfer Protocol, is the foundation for all e-mail transport in Exchange 2000. The SMTP Service (SMTPSvc) runs on top of the IIS Admin Service. Unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS).
Protocol: SMTP/SSL
*Port (TCP/UDP): 465 (TCP)
*Description: SMTP over SSL. TCP port 465 is reserved by common industry practice for secure SMTP communication using the SSL protocol. However, unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS). To enable TLS to work on Exchange 2000, you must install a Computer certificate on the Exchange 2000 server.
Protocol: SMTP/LSA
*Port (TCP/UDP): 691 (TCP)
*Description: The Microsoft Exchange Routing Engine (also known as RESvc) listens for routing link state information on TCP port 691. Exchange 2000 uses routing link state information to route messages and the routing table is constantly updated. The Link State Algorithm (LSA) propagates outing status information between Exchange 2000 servers. This algorithm is based on the Open Shortest Path First (OSPF) protocol from networking technology, and transfers link state information between routing groups by using the X-LSA-2 command verb over SMTP and by using a Transmission Control Protocol (TCP) connection to port 691 in a routing group.
Protocol: RVP
*Port (TCP/UDP): 80 (TCP)
*Description: RVP is the foundation for Instant Messaging in Exchange 2000. While RVP communication begins with TCP port 80, the server quickly sets up a new connection to the client on an ephemeral TCP port above 1024. Because this port is not known in advance, issues exist when you enable Instant Messaging through a firewall.
Protocol: IRC/IRCX
*Port (TCP/UDP): 6667 (TCP)
*Description: Internet Relay Chat (IRC) is the chat protocol. IRCX is the extended version offered by Microsoft. While TCP port 6667 is the most common port for IRC, TCP port 7000 is also very frequently used.
Protocol: IRC/SSL
*Port (TCP/UDP): 994 (TCP)
*Description: IRC (or Chat) over SSL. IRC or IRCX over SSL is not supported in Exchange 2000.
Full info here
Protocol: LDAP
* Port (TCP/UDP): 389 (TCP)
Description: Lightweight Directory Access Protocol (LDAP), used by Active Directory, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory.
Protocol: LDAP/SSL
* Port (TCP/UDP): 636 (TCP)
* Description: LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted.
* To enable SSL, you must install a Computer certificate on the domain controller or Exchange Server 5.5 computer.
Protocol: LDAP
* Port (TCP/UDP): 379 (TCP)
* Description: The Site Replication Service (SRS) uses TCP port 379.
Protocol: LDAP
* Port (TCP/UDP): 390 (TCP)
* Description: While not a standard LDAP port, TCP port 390 is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on a Microsoft Windows 2000 Active Directory domain controller.
Protocol: LDAP
*Port (TCP/UDP): 3268 (TCP)
* Description: Global catalog. The Windows 2000 Active Directory global catalog (which is really a domain controller "role") listens on TCP port 3268. When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP.
Protocol: LDAP/SSL
*Port (TCP/UDP): 3269 (TCP)
*Description: Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data. To configure a global catalog to support SSL, you must install a Computer certificate on the global catalog.
Protocol: IMAP4
*Port (TCP/UDP): 143 (TCP)
*Description: Internet Message Access Protocol version 4, may be used by "standards-based" clients such as Microsoft Outlook Express or Netscape Communicator to access the e-mail server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service (Inetinfo.exe), and enables client access to the Exchange 2000 information store.
Protocol: IMAP4/SSL
*Port (TCP/UDP): 993 (TCP)
*Description: IMAP4 over SSL uses TCP port 993. Before an Exchange 2000 server supports IMAP4 (or any other protocol) over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: POP3
*Port (TCP/UDP): 110 (TCP)
*Description: Post Office Protocol version 3, enables "standards-based" clients such as Outlook Express or Netscape Communicator to access the e-mail server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange 2000 information store.
Protocol: POP3/SSL
*Port (TCP/UDP): 995 (TCP)
*Description: POP3 over SSL. To enable POP3 over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: NNTP
*Port (TCP/UDP): 119 (TCP)
*Description: Network News Transport Protocol, sometimes called Usenet protocol, enables "standards-based" client access to public folders in the information store. As with IMAP4 and POP3, NNTP is dependent on the IIS Admin Service.
Protocol: NNTP/SSL
Port (TCP/UDP): 563 (TCP)
Description: NNTP over SSL. To enable NNTP over SSL, you must install a Computer certificate on the Exchange 2000 Server.
Protocol: HTTP
*Port (TCP/UDP): 80 (TCP)
*Description: Hyper-Text Transfer Protocol is the protocol used primarily by Microsoft Outlook Web Access (OWA), but also enables some administrative actions in Exchange System Manager. HTTP is implemented through the World Wide Web Publishing Service (W3Svc), and runs on top of the IIS Admin Service.
Protocol: HTTP/SSL
*Port (TCP/UDP): 443 (TCP)
*Description: HTTP over SSL. To enable HTTP over SSL, you must install a Computer certificate on the Exchange 2000 server.
Protocol: SMTP
*Port (TCP/UDP): 25 (TCP)
*Description: Simple Mail Transfer Protocol, is the foundation for all e-mail transport in Exchange 2000. The SMTP Service (SMTPSvc) runs on top of the IIS Admin Service. Unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS).
Protocol: SMTP/SSL
*Port (TCP/UDP): 465 (TCP)
*Description: SMTP over SSL. TCP port 465 is reserved by common industry practice for secure SMTP communication using the SSL protocol. However, unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS). To enable TLS to work on Exchange 2000, you must install a Computer certificate on the Exchange 2000 server.
Protocol: SMTP/LSA
*Port (TCP/UDP): 691 (TCP)
*Description: The Microsoft Exchange Routing Engine (also known as RESvc) listens for routing link state information on TCP port 691. Exchange 2000 uses routing link state information to route messages and the routing table is constantly updated. The Link State Algorithm (LSA) propagates outing status information between Exchange 2000 servers. This algorithm is based on the Open Shortest Path First (OSPF) protocol from networking technology, and transfers link state information between routing groups by using the X-LSA-2 command verb over SMTP and by using a Transmission Control Protocol (TCP) connection to port 691 in a routing group.
Protocol: RVP
*Port (TCP/UDP): 80 (TCP)
*Description: RVP is the foundation for Instant Messaging in Exchange 2000. While RVP communication begins with TCP port 80, the server quickly sets up a new connection to the client on an ephemeral TCP port above 1024. Because this port is not known in advance, issues exist when you enable Instant Messaging through a firewall.
Protocol: IRC/IRCX
*Port (TCP/UDP): 6667 (TCP)
*Description: Internet Relay Chat (IRC) is the chat protocol. IRCX is the extended version offered by Microsoft. While TCP port 6667 is the most common port for IRC, TCP port 7000 is also very frequently used.
Protocol: IRC/SSL
*Port (TCP/UDP): 994 (TCP)
*Description: IRC (or Chat) over SSL. IRC or IRCX over SSL is not supported in Exchange 2000.
Full info here
Subscribe to:
Posts (Atom)
