Page 322 of 741« First...102030...320321322323324...330340350...Last »

Error message when you use Office Genuine Advantage to validate Office: "Incorrect Time Settings" or "Error code: 0×8018110"

When you use Office Genuine Advantage to validate your copy
of the 2007 Microsoft
Office system, Microsoft Office 2003, or Microsoft Office
XP, you receive one of the following error messages:
This issue may occur when the time on the computer is
incorrect by more than 24 hours.
To resolve this issue, verify and adjust the date and time
on your computer as needed. To verify and adjust the date and time, use the following methods depending on your operating system:

Windows Vista

Use Control Panel

  1. Click Start, click Control
    Panel
    , click Clock, Language, and Region, and then
    click Date and Time.
  2. Click the Date and Time tab, and then
    click Change date and time. If you are prompted for an
    administrator password or confirmation, type the password or provide
    confirmation.
  3. In the Date and Time Settings dialog box,
    do one or more of the following:

    • To change the hour, double-click the hour, and then
      click the arrows to increase or decrease the value.
    • To change the minutes, double-click the minutes, and
      then click the arrows to increase or decrease the value.
    • To change the seconds, double-click the seconds, and
      then click the arrows to increase or decrease the value.
  4. When you have finished changing the time settings, click
    OK.
  5. To change the time zone, click Change time
    zone
    .
  6. In the Time Zone Settings dialog box,
    click your current time zone in the list, and then click OK.

    Note If your time zone observes daylight saving time and you want your
    computer’s clock to be adjusted automatically when daylight saving time
    changes, make sure that the Automatically adjust clock for Daylight Saving
    Time
    check box is selected.

  7. Click OK.

For information about how to use the Clock gadget in Windows Sidebar,
see Windows Sidebar and gadgets (overview).

Windows XP

Method 1: Use the notification area

To use the notification area to verify and adjust the date and
time, follow these steps:

  1. Right-click the time in the notification area, and then
    click Adjust Date/Time.
  2. On the Date & Time tab, set the
    current date, year, and time.
  3. Click OK to close the Date and
    Time Properties
    dialog box.

Method 2: Use Control Panel

To use Control Panel to verify and adjust the date and time,
follow these steps:

  1. Click Start, click Control
    Panel
    , and then click Date, Time, Language, and Regional
    Options
    .
  2. Click Date and Time.
  3. On the Date & Time tab, set the
    current date, year, and time.
  4. Click OK to close the Date and
    Time Properties
    dialog box.
If you still experience problems when you use Office Genuine
Advantage to validate your copy of the
2007 Office system, Office 2003, or Office XP, run the Genuine
Advantage diagnostics
tool. To do this, visit the following Microsoft Web
site:

Article ID: 918000 – Last Review: August 31, 2012 – Revision: 4.0


Applies to
  • Microsoft Office Basic 2007
  • Microsoft Office Enterprise 2007
  • Microsoft Office Home and Student 2007
  • Microsoft Office Professional 2007
  • Microsoft Office Professional Plus 2007
  • Microsoft Office Small Business 2007
  • Microsoft Office Standard 2007
  • Microsoft Office Ultimate 2007
  • Microsoft Office Word 2007
  • Microsoft Office Word 2007 (Home and Student version)
  • Microsoft Office Excel 2007
  • Microsoft Office Excel 2007 (Home and Student version)
  • Microsoft Office PowerPoint 2007
  • Microsoft Office PowerPoint 2007 (Home and Student version)
  • Microsoft Office Professional Edition 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office Small Business Management Edition 2006
  • Microsoft Office Basic Edition 2003
  • Microsoft Office OneNote 2003
  • Microsoft Office Outlook 2003
  • Microsoft Office Outlook 2003 with Business Contact Manager
  • Microsoft Office PowerPoint 2003
  • Microsoft Office Publisher 2003
  • Microsoft Office Project Standard 2003
  • Microsoft Office Visio Professional 2003
  • Microsoft Office XP Small Business Edition
  • Microsoft Office XP Standard Edition
  • Microsoft Access 2002 Standard Edition
  • Microsoft Excel 2002 Standard Edition
  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Outlook 2002 Standard Edition
  • Microsoft PowerPoint 2002 Standard Edition
  • Microsoft Project 2002 Professional Edition
  • Microsoft Publisher 2002 Standard Edition
  • Microsoft Visio 2002 Professional Edition
  • Microsoft Visio 2002 Standard Edition
  • Microsoft Word 2002
  • Microsoft Office Genuine Advantage
  • Microsoft Office Access 2003
kbtshoot kblicensing kbsetup kbactivation kbexpertisebeginner kbprb KB918000
Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered “as is” and will no longer be updated.

Read More:
Error message when you use Office Genuine Advantage to validate Office: "Incorrect Time Settings" or "Error code: 0×8018110"

"Your local machine time zone does not match your current SharePoint regional setting" warning message in an Access web database in a SharePoint site

oneMscomBlade,oneMsomNav,oneMscomFooter,

Read the article:
"Your local machine time zone does not match your current SharePoint regional setting" warning message in an Access web database in a SharePoint site

You may receive a security warning message when you use the SendObject macro action or the SendObject method in Microsoft Access

When you use the SendObject macro action or
the SendObject Microsoft Visual Basic for Applications (VBA)
method with the EditMessage argument set to No, you may receive the following security warning message:

A program is trying to automatically send e-mail on
your behalf. Do you want to allow this? If this is unexpected, it may be a
virus and you should choose No.

The Yes button in the dialog box is
disabled for several seconds, and then you can click Yes. If you click Yes, the
e-mail message is sent. If you click No, the message is not sent, and you
may receive one of the following error messages:

Error message that is received with the SendObject macro action

Microsoft Office Access can’t send this
e-mail message. Before attempting to send an e-mail message from Microsoft
Office Access, resolve the problem identified
in the previous message, or configure your computer to send and receive e-mail
messages.

Error message that is received with the SendObject VBA method

Run-time error ’2293′: Microsoft Office
Access can’t send this e-mail message.

When you apply the Microsoft Outlook E-mail Security Update,

the Outlook E-mail Security Update provides
additional levels of protection against malicious e-mail messages.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

262631

(http://support.microsoft.com/kb/262631/
)

Information about the Outlook E-mail Security Update

The Outlook
E-mail Security Update changes the way that attachments are handled by Microsoft Outlook.
The Outlook
E-mail Security Update also changes the way that Outlook can be controlled programmatically.

Note The Outlook
E-mail Security Update is included with Microsoft Office Outlook 2007, Microsoft Office Outlook
2003, and Microsoft Outlook
2002.

To work around this problem, you can customize the behavior
of the Outlook E-mail Security Update. You can customize the behavior if you
are not running Outlook in a Microsoft Exchange Server environment.

For additional information about how to customize the behavior of the Outlook E-mail Security Update, click the following article number to view the article in the Microsoft Knowledge Base:

263297

(http://support.microsoft.com/kb/263297/
)

Administrator information about the Outlook E-mail Security update: June 7, 2000

Note If your mail is delivered to a Personal Folders (.pst) file, you
cannot configure the settings for the update.

Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

For more information about how other Microsoft Office products may be affected by the Outlook E-mail Security Update, click the following article numbers to view the articles in the Microsoft Knowledge Base:

290499

(http://support.microsoft.com/kb/290499/
)

Administrator information about e-mail security features

262634

(http://support.microsoft.com/kb/262634/
)

Description of known issues with the Outlook E-mail Security Update in Outlook 2000

262618

(http://support.microsoft.com/kb/262618/
)

Known issues with the Outlook E-mail Security Update

Article ID: 884998 – Last Review: August 31, 2012 – Revision: 6.0


Applies to
  • Microsoft Office Access 2007
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition

Excerpt from:
You may receive a security warning message when you use the SendObject macro action or the SendObject method in Microsoft Access

PRB: ThreadAbortException Occurs If You Use Response.End, Response.Redirect, or Server.Transfer

If you use the Response.End, Response.Redirect, or
Server.Transfer method, a ThreadAbortException exception occurs. You can use a try-catch statement to catch this exception.
The Response.End method ends the page execution and shifts the execution to the Application_EndRequest event in the application’s event pipeline. The line of code that follows Response.End is not executed.

This problem occurs in the Response.Redirect and Server.Transfer methods because both methods call Response.End internally.

To work around this problem, use one of the following methods:

  • For Response.End, call the HttpContext.Current.ApplicationInstance.CompleteRequest method instead of Response.End to bypass the code execution to the Application_EndRequest event.
  • For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example:
      Response.Redirect ("nextpage.aspx", false);
    						

    If you use this workaround, the code that follows Response.Redirect is executed.

  • For Server.Transfer, use the Server.Execute method instead.
This behavior is by design.

Article ID: 312629 – Last Review: August 30, 2012 – Revision: 4.0


Applies to
  • Microsoft ASP.NET 4.5
  • Microsoft ASP.NET 4
  • Microsoft ASP.NET 3.5
  • Microsoft ASP.NET 2.0
  • Microsoft ASP.NET 1.1
  • Microsoft ASP.NET 1.0
kbexcepthandling kbprb KB312629

View article:
PRB: ThreadAbortException Occurs If You Use Response.End, Response.Redirect, or Server.Transfer

You cannot assign delegates for Live Meeting in Outlook in a Office 365 dedicated/ITAR environment

Consider the following scenario. You are assigned delegate permissions for Microsoft Office Live Meeting in a Office 365 dedicated/ITAR environment. Then, you try to schedule a Live Meeting request on behalf of someone else. In this scenario, you receive the following error message:

You can’t schedule on behalf of this person because delegation isn’t supported on Live Meeting service. If you do schedule a Live Meeting using Live Meeting service, the invitation will be from you.

This is a known issue. The functionality in this delegation scenario is not supported by Microsoft Online Services when you use the Conferencing Add-in for Microsoft Outlook.
To work around this issue, use one of the following methods.

Method 1

You can set up instances of Live Meeting on behalf of someone else by using the Live Meeting Portal or the Conferencing Center. You must use the person’s user name and password to access the Live Meeting Portal or the Conferencing Center. This lets you schedule a meeting in Live Meeting. However, when you schedule a meeting by using the Live Meeting Portal or the Conferencing Center, the meeting does not appear on your calendar. This is a known issue.

Method 2

You can create a meeting on the Live Meeting Manager website by using the end-user’s credentials and then sending attendee and presenter invitations to yourself. You can then create a regular meeting in Microsoft Outlook on behalf of the other person by using that person’s delegation rights and then pasting the Live Meeting information from the Live Meeting invitations.

Method 3

You can have the meeting owner create the meeting and invite only the user who has delegate permissions. The delegate must open the invitation and copy the Live Meeting information. The delegate must then create a new appointment in Outlook, paste the Live Meeting information into the new appointment, and then send the invitation to all attendees.

Article ID: 2353019 – Last Review: August 30, 2012 – Revision: 15.0


Applies to
  • Microsoft Business Productivity Online Standard Suite
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Exchange Online
vkbportal221 vkbportal238 vkbportal230 vkbportal226 vkbportal107 KB2353019

Read the article:
You cannot assign delegates for Live Meeting in Outlook in a Office 365 dedicated/ITAR environment

Description of the Office XP Service Pack 1 (SP-1)

Microsoft Office XP Service Pack 1 (SP-1) provides the
latest updates to Office XP. Office XP SP-1 contains significant security
enhancements, and also improvements in stability and performance. Some of the
fixes that are included with Office XP SP-1 were released earlier as separate
updates. This service pack combines the updates into one integrated package and
includes a number of other changes that are designed to improve the reliability
and performance of your Office XP programs.

This article describes
how to download and install the Office XP SP-1.

How to Download and Install Office XP SP-1

Client Update

If you installed Office XP from a CD-ROM, you have two options:

  • Use the Office Product Updates Web site to automatically
    install all of the latest updates, including Service Pack 1.

    -or-

  • Install only Service Pack 1 by using the steps described
    below.

Both options require that you have your Office XP CD-ROM
available during the installation process.

Office Product Updates

To have the Office Product Updates Web site detect the
required updates you must install on your computer, click the following link:

After detection is complete, you receive a list of recommended
updates for your approval. Click Start Installation to complete the process.

Install Only Service Pack 1

To download and install only the SP-1 client update,
follow these steps:

  1. Visit the following Microsoft Web site:
  2. Click Save to save the Oxpsp1.exe file to the selected folder.
  3. In Windows Explorer, double-click Oxpsp1.exe.
  4. If you are prompted to install the update, click Yes.
  5. Click Yes to accept the License Agreement.
  6. Insert your Office XP CD-ROM when you are prompted to do
    so, and then click OK.
  7. When you receive a message that indicates the installation
    was successful, click OK.

NOTE: After you install the public update, you cannot remove it. To
return to an installation earlier than SP-1, you must remove all of Office XP
and install it again from the original CD.

Administrative Update

If you installed any of the products listed at the beginning of
this article from a server location, the server administrator must update the
server location with the administrative public update and deploy that update to
your computer.

If you are the server administrator, follow these
steps to download the administrative update:

  1. Visit the following Microsoft Web site:
  2. Download the file to your desktop.
  3. In Windows Explorer, double-click the oxpsp1a.exe file.
  4. Click Yes to accept the License Agreement.
  5. In the Please type the location where you want to
    place the extracted files
    box, type C:oxpsp1a,
    and then click OK.
  6. Click Yes when you are prompted to create the folder.
  7. If you are familiar with the procedure for updating your
    administrative installation, click Start and then click Run. Type the following command in the Open box


    msiexec /a Admin PathMSI File /p C:adminUpdateMSP File
    SHORTFILENAMES=1

    where Admin Path is the
    path to your administrative installation point for Office XP (for example,
    C:OfficeXP),

    where MSI File is the MSI database package for the Office XP product (for
    example, ProPlus.msi), and

    where MSP File
    is the name of the public administrative installation update. NOTE: You can append /qb+ to the previous
    command line to avoid receiving the Office XP Administrative Installation dialog box and the End User License Agreement dialog box.

  8. To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box


    msiexec /i Admin PathMSI File REINSTALL=Feature List REINSTALLMODE=vomus

    where Admin Path is the
    path to your administrative installation point for Office XP (for example,
    C:OfficeXP),

    where MSI File is the MSI
    database package for the Office XP product (for example, ProPlus.msi),
    and

    where Feature List is the list of
    feature names (case sensitive) that must be reinstalled for the update. To
    install all features, you can use REINSTALL=ALL.

For additional information about how to update your
administrative installation and deploy to client workstations, click the
following article number to view the article in the Microsoft Knowledge Base:

301348

(http://support.microsoft.com/kb/301348/
)

How to install a public update to administrative installations of Office XP

This article contains standard instructions for
installing an administrative public update.

Setup.ini Version Is Not Updated

The Setup.ini file, located in the FilesSetup folder of an
administrative installation, contains a Product section that includes product
version information. This version information is not updated after you apply
SP-1 to your administrative installation. This is different from updates for
earlier versions of Office.

Restarting the Computer During Installation

Under the following conditions, the installation of Office XP
SP-1 may require you to restart your computer:

  • You are running Microsoft Windows 2000 and you do not have
    the most recent version of the Windows Installer. To prevent the computer from
    restarting, upgrade to Windows Installer 2.0. For more information, visit the
    following Microsoft Web site:
  • The Office Shortcut Bar is running. To prevent the computer
    from restarting, shut down the Office Shortcut Bar before you apply the update.
  • SharePoint Team Services from Microsoft is installed. To
    prevent the computer from restarting, shut down the SharePoint Team Services
    service before you apply the update.

SP-1 May Require Office CD-ROM or Network Installation Location

To make sure of the integrity of your Office installation, the
Installation Wizard may require access to the Office product CD or your network
installation location during the installation process.

Office XP Multilingual User Interface Pack

For complete Office XP SP-1 functionality when you are using an
Office XP Multilingual User Interface Pack, you need the following updates:

  • Office XP Update: Service Pack 1 (SP-1)
  • Office XP Update: Service Pack 1 (SP-1) for Office XP
    Multilingual User Interface Pack

Office XP Update: To download Service Pack 1 (SP-1) for Office
XP Multilingual User Interface Pack, visit the following Microsoft Web site:

How to Determine Whether Service Pack 1 Is Installed

Office XP SP-1 contains updated versions of the following files:

Blnmgr.dll            Blnmgrps.dll         Cfgwiz.exe
Contab32.dll          Emablt32.dll         Emsabp32.dll
Emsmdb32.dll          EmSui32.dll          Eurotool.xla
Excel.exe             Exsec32.dll          Fontschm.ini
Fp5amsft.dll          Fp5autl.dll          Fp5avnb.dll
Fp5awec.dll           Fp5awel.dll          Fpcutl.dll
Fpeditax.dll          Fpmmc.dll            Frontpg.exe
Graph.exe             Imjp8k.dll           Intldate.dll
Mofl.dll              Msaccess.exe         Mscdm.dll
Msdaipp.dll           Mseuro.dll           Msgr2pb.dll
Msgrit32.DLL          MsMapi32.dll         Mso.dll
Msowc.dll             MsPst32.dll          Mspub.exe
Mssp3ko.dll           mssp3ko.lex          Msstko32.dll
Mstore.exe            Mstores.dll          Offfilt.dll
Olappt.fae            Outex.dll            Outlcm.dll
Outlctl.dll           Outllib.dll          Outllibr.dll
Outlmime.dll          Outlook.exe          Outlph.dll
Owc10.dll             Owsclt.dll           Owssvr.dll
Powerpnt.exe          Pstprx32.dll         Pub6intl.dll
Pubconv.dll           Qamgt.xlt            Rm.dll
Rtfhtml.dll           Setup.exe            Transform.mst
Vtidb.exe             Winword.exe          Wwintl.ddl
				

To determine whether SP-1 is installed, start any Office XP
program, and then click About Microsoft program on the Help menu. The product version is (SP-1) if SP-1 is
installed.

The following table shows the build numbers for the Office
products:

 Office program     SP-1 version
 ---------------------------------
 Access            10.3409.3501
 Excel             10.3506.3501
 FrontPage         10.3402.3501
 Outlook           10.3513.3501
 PowerPoint        10.3506.3501
 Word              10.3416.3501
				

For additional information, click the following article number
to view the article in the Microsoft Knowledge Base:

291331

(http://support.microsoft.com/kb/291331/
)

How to check the version of Office XP

Issues Fixed by SP-1

Office XP SP-1 addresses the issues described in the following
Microsoft Security Bulletins:
This Service Pack includes all earlier released updates for
Office XP:

300550

(http://support.microsoft.com/kb/300550/
)

Description of the Outlook 2002 update: June 21, 2001

300553

(http://support.microsoft.com/kb/300553/
)

Description of the Word 2002 Update: June 21, 2001

299040

(http://support.microsoft.com/kb/299040/
)

Overview of the Publisher 2002 update: June 21 2001

300552

(http://support.microsoft.com/kb/300552/
)

Overview of the Office XP Web Components update: August 9 2001

303825

(http://support.microsoft.com/kb/303825/
)

Description of the Outlook 2002 update: Aug 16, 2001

307741

(http://support.microsoft.com/kb/307741/
)

Description of the Office XP Activation Update: October 4, 2001

300551

(http://support.microsoft.com/kb/300551/
)

Description of the Outlook 2002 update: October 4, 2001

306605

(http://support.microsoft.com/kb/306605/
)

Description of the PowerPoint 2002 update: October 4, 2001

306606

(http://support.microsoft.com/kb/306606/
)

Description of the Excel 2002 update: October 4, 2001

Office XP SP-1 can be installed successfully, even
if one or more of the publicly available updates listed earlier in this article
is already installed on your computer.

Office XP SP-1 also includes
stability improvements that were developed as a result of the Microsoft Error
Reports submitted by Office XP users. For more information, visit the following
Microsoft Web site:

Office XP SP-1 fixes the issues described in the following
Microsoft Knowledge Base articles.

Microsoft Excel

311597

(http://support.microsoft.com/kb/311597/
)

List of issues that are fixed by Office XP Service Pack 1 in Excel 2002

Microsoft FrontPage

311574

(http://support.microsoft.com/kb/311574/
)

List of issues that are fixed in FrontPage 2002 by Office XP Service Pack 1

SharePoint Team Services from Microsoft

312543

(http://support.microsoft.com/kb/312543/
)

List of issues fixed by Office XP Service Pack 1 for SharePoint Team Services

Microsoft Outlook

311573

(http://support.microsoft.com/kb/311573/
)

Description of the issues that are fixed in Outlook 2002 by the Office XP Service Pack 1

Microsoft Office

307560

(http://support.microsoft.com/kb/307560/
)

Office XP may fail to open documents from a Web folder that requires client certificates

304226

(http://support.microsoft.com/kb/304226/
)

A reactivation message appears when you start an Office XP program that was installed from an Enterprise edition

305086

(http://support.microsoft.com/kb/305086/
)

“You do not have access…” error message when you open from or save to a domain DFS

Microsoft PowerPoint

298797

(http://support.microsoft.com/kb/298797/
)

Microsoft Graph stops responding when you change the chart type in a PowerPoint 2002 slide

304568

(http://support.microsoft.com/kb/304568/
)

Animation timings for multimedia are lost when you open a presentation in a different version of PowerPoint 2002

310409

(http://support.microsoft.com/kb/310409/
)

You receive a “The page cannot be displayed” error message when you click a hyperlink to a PowerPoint 2002 presentation

Microsoft Publisher

297082

(http://support.microsoft.com/kb/297082/
)

The size of the Web pages created in Publisher 2002 is so large that it takes a long time to display

301221

(http://support.microsoft.com/kb/301221/
)

Font list is blank and there are no fonts are displayed in Publisher 2002

Microsoft Word

311594

(http://support.microsoft.com/kb/311594/
)

Description of issues in Word 2002 that are fixed by Office XP Service Pack 1

301405

(http://support.microsoft.com/kb/301405/
)

Word 2002 stops responding when you insert an AutoShape

Additionally, the following issues are fixed.

Microsoft Access

Microsoft Access Cannot Connect to Database to Create Bound Datapage

When you try to design a data page in Turkish Microsoft Access,
the field list may be empty.

Office

Send To Not Available on Shortcut Menu

When you right-click a file in the Open dialog box (on the File menu, click Open) in a Microsoft Office program, Send To is unavailable (appears dimmed).

TIFF Image Not Visible in Office for the Macintosh

The following issue may occur if you insert a TIFF file into a
Microsoft Word document, a Microsoft Excel document, or a Microsoft PowerPoint
2002 document. When the file is saved and reopened in Microsoft Office 98
Macintosh Edition or Microsoft Office 2001 for Mac, the picture is replaced
with a big red X.

Cannot Save Documents in MSN Communities

In some cases, you cannot use Office programs to save documents
on MSN Communities.

Error 25003 Installing Office Updates

When you try to apply any update earlier than SP-1 to any
Microsoft Office 2002 program that was preinstalled by the computer
manufacturer, you may receive an error message similar to the following:

Microsoft Office Setup cannot continue because the
installation source has been corrupted.

Setup Does Not Start On Update

When you try to run Setup to update Office XP, you may receive an
error message that states that another version of this product is already
installed. To install the update, you must remove the original version.

Reactivation Message After Docking or Undocking Laptop

Office may report detecting a significant change in your computer
configuration after you dock a laptop. You must reactivate your product.

Buffer Overrun Opening HTML Document

All Office XP programs can quit unexpectedly when opening an HTML
file with an extremely long string in a certain tag.

Outlook

Geresh Sign Displayed as Percent Sign in Hebrew Outlook

The Hebrew punctuation Geresh sign is displayed as a percent sign
when you type the Geresh sign in any toolbar text boxes in Hebrew Outlook.

PowerPoint

Custom Timings Lost Between PowerPoint 2002 and PowerPoint 2000

The following issue can occur with presentations that are created
in Microsoft PowerPoint 2002 and viewed in earlier versions of PowerPoint or
with the PowerPoint Viewer. The media object animation timing is ignored. This
issue can also occur with PowerPoint 2000 presentations that you open in a
PowerPoint 2002 slideshow.

Publisher

Fonts Missing from Font Preview List

In some color schemes, the font-selection combo box on the edit
toolbar appears blank in Microsoft Publisher 2002.

Clip Art Gallery Displays Standard Icons

In some situations, when you try to view any clips under Web
Collections, all the clips are displayed with the system icon for that file
type.

Cannot Apply a Font Scheme in Hebrew Publisher

When you try to apply a font scheme in Hebrew Publisher 2002 with
the user interface in Hebrew, nothing happens. When you switch the user
interface to English, you can apply font schemes.

Web Components

Analysis ToolPak Does Not Release Memory

A server with a Web that uses the Analysis ToolPak add-in may run
out of memory. The Analysis ToolPak add-in is instantiated in memory, but the
memory is not released when the memory is no longer needed.

Analysis ToolPak Leaks Memory

When you use a Web with the spreadsheet Web component from the
Analysis ToolPak, any circular references in formulas allocate memory without
releasing the memory later. The server slowly runs out of memory.

No Error in Analysis ToolPak Functions with Incorrect Parameters

When you use a Web with the spreadsheet Web component from the
Analysis ToolPak, a function which has too many or too few parameters returns
the value “0″ instead of an error (#VALUE!).

REFERENCES

For more information, visit the following Microsoft Office XP Web
site:

Continue Reading:
Description of the Office XP Service Pack 1 (SP-1)

Access 2003 may not start as expected after you install Office 2003 SP2

After you install Microsoft Office 2003 Service Pack 2
(SP2), Microsoft Office Access 2003 may not start as expected. You may receive
a message that is similar to the following:

Please wait
while Windows configures Microsoft Office Professional Edition
2003

The configuration appears to finish as expected, but Access 2003
does not start. When you try to start Access 2003 again, you receive the same
message.

This problem can occur if you use Group Policy to install
Office 2003 SP2 on a per-user basis. When you use Group Policy to install
Office 2003 SP2 on a per-user basis, a registry key may not be updated
correctly.
This problem is corrected in Office 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870924

(http://support.microsoft.com/kb/870924/
)

How to obtain the latest service pack for Office 2003

To resolve this problem, you can also use one of the following methods.

Method 1: Import the registry key from a computer where Access 2003 starts as expected

To resolve this problem, export a registry key from a computer
where Access 2003 starts as expected. To do this, follow these steps.

Note When you follow these steps, some settings, such as ODBC settings
or time-out settings, may be overwritten on the computer where Access 2003 does
not start.

  1. On the computer where Access 2003 starts as expected, click
    Start, click Run, type
    regedit, and then click OK.
  2. Locate the following registry key:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftJet

  3. Right-click the registry key that you located in step 2,
    and then click Export.
  4. In the Export Registry File dialog box,
    specify a location for the exported file, type a file name, click
    Selected branch, and then click
    Save.
  5. Copy the file that you created in step 4 to the computer
    where Access 2003 does not start as expected.
  6. On the computer where Access 2003 does not start as
    expected, double-click the file that you copied in step 5, and then click
    Yes to confirm that you want to add the information to the
    Windows registry.
  7. Click OK.

Method 2: Manually change the registry

To resolve this problem, manually change the registry on the
computer where Access 2003 does not start as expected. To do this, follow these
steps:

  1. Click Start, click Run,
    type regedit, and then click
    OK.
  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftJet4.0EnginesExcel

  3. In the right pane, right-click win32, and
    then click Modify.
  4. In the Value data box, type the following,
    and then click OK:

    C:Program FilesMicrosoft OfficeOFFICE11msaexp30.dll

    Note This path is for the default location. If the Msaexp30.dll file
    is located on another drive or in another folder, use the path of the actual
    drive and folder.

  5. Exit Registry Editor, and then start Access
    2003.
To work around this problem, use Group Policy to install
Office 2003 SP2 on each computer. For more information about how to deploy
Office 2003 SP2 on each computer, visit the following Microsoft Web site:
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

This problem was first corrected in Office 2003 Service Pack 3.

Article ID: 914830 – Last Review: August 29, 2012 – Revision: 1.0


Applies to
  • Microsoft Office 2003 Service Pack 2, when used with:
    • Microsoft Office Access 2003
  • Microsoft Office Access 2003
kboffice2003sp3fix kbtshoot kbprb KB914830

Read the article:
Access 2003 may not start as expected after you install Office 2003 SP2

SDP 361593d1b-21b0-43e3-9088-74e77dec12f4 Microsoft Dynamics CRM client for Outlook diagnostic tool

The Microsoft Dynamics CRM client for Microsoft Office Outlook diagnostic tool collects crash or dump files for the CRMAppPool account that is configured on the Microsoft Dynamics CRM Internet Information Services (IIS) computer. This article describes the data that is collected by the Memory Dump diagnostic tool. 
The diagnostic tool that described in this article can be used on the following versions of Windows: 

Information that is collected

The following data can be collected by the Memory Dump diagnostic tool of the Microsoft Support Diagnostic Tool. 

Notes

  • All file names in the data collection are prefaced with the ComputerName on which the Microsoft Support Diagnostic Tool is run.
  • The diagnostic tool uses the ProcDump tool to generate one or more .dmp files when the selected application either stops responding or ends unexpectedly. For more information about the ProcDump tool, go to the following Microsoft website:

    http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

    (http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx )

Operating system information

Collapse this tableExpand this table

Description

File name

Operating system version information

ComputerName_DateRan.htm

Installed applications

Collapse this tableExpand this table

Description

File name

Lists the applications that are installed on the Microsoft Dynamics CRM Client for Outlook computer

ComputerName_DateRan.htm

Internet Explorer and Microsoft Office version information

Collapse this tableExpand this table

Description

File name

Lists the versions of Internet Explorer and Office

ComputerName_DateRan.htm

Microsoft Outlook add-in information

Collapse this tableExpand this table

Description

File name

Lists the add-ins that are installed for use with Microsoft Outlook

ComputerName_DateRan.htm

Internet Explorer trusted sites and proxy settings

Collapse this tableExpand this table

Description

File name

The file lists registry keys and values that are stored under the HKCU:SoftwareMicrosoftWindowsCurrentVersionInternet SettingsZoneMapDomains registry hive. Additionally, this file also lists the registry keys and values under the HKCU:SoftwareMicrosoftWindowsCurrentVersionInternet Settings hive. 

ComputerName_DateRan.htm

Microsoft Dynamics CRM registry key values

Collapse this tableExpand this table

Description

File name

Lists registry keys and values that are stored that are under HKEY_LocalMachineSoftwareMicrosoftMSCRMClient registry hive. 

ComputerName_DateRan.htm

Microsoft Dynamics CRM registry user values

Collapse this tableExpand this table

Description

File name

Lists registry keys and values that are stored under HKEY_CurrentUserSoftwareMicrosoftMSCRMClient registry hive.

ComputerName_DateRan.htm

Installed Microsoft Dynamics CRM hotfixes

Collapse this tableExpand this table

Description

File name

Lists all applied Microsoft Dynamics CRM hotfixes. 

ComputerName_DateRan.htm

Microsoft Dynamics CRM files

Collapse this tableExpand this table

Description

File name

Lists all files from the InstallPath registry key value, including dates and file versions. 

ComputerName_DateRan.htm

Microsoft Dynamics CRM files that are installed in the assembly cache

Collapse this tableExpand this table

Description

File name

Lists all Microsoft Dynamics CRM files that are installed in the global assembly cache on the CRM server. 

ComputerName_DateRan.htm

TCP/IP configuration

Collapse this tableExpand this table

Description

File name

Lists TCP/IP registry keys and their values. 

ComputerName_DateRan.htm

Application logs

Collapse this tableExpand this table

Description

File name

Event log – Application – all Microsoft Dynamics CRM events in the last seven days Event log – Application – all ASP.NET events in the last seven days 

ComputerName_DateRan.htm

Installed .NET Framework information

Collapse this tableExpand this table

Description

File name

Lists all .NET Framework versions that are installed on the client computer.

ComputerName_DateRan.htm

Group Policy information

Collapse this tableExpand this table

Description

File name

Lists information about the applied Group Policy settings by using the gpresult utility. 

ComputerName_DateRan.htm

Mail profile information

Collapse this tableExpand this table

Description

File name

Lists the keys and values under the HKCU: SoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles registry hive. 

ComputerName_DateRan.htm

Note The setup and client configuration log files from the %APPDATA%MicrosoftMSCRMLogs file directory are also collected by this diagnostic tool.

Unresponsive application data dump

The following files are generated and collected if you select the The application has become unresponsive option when you are prompted by the diagnostic tool.

For this scenario, as many as three .dmp files are generated, 10 seconds apart, to capture memory details while the selected application is in an unresponsive state. Because these files are typically very large, the diagnostic tool may take several minutes to finish.

Collapse this tableExpand this table

Description

File name

A text file lists the .zip files generated by the diagnostic. The .zip file names and parent folder location are provided.

ComputerName _DumpFile_Information.txt

A .zip file that contains a compressed .dmp file.

ComputerName _w3wp.zip

A text file contains output information from the ProcDump tool. For example, the location and name of the uncompressed .dmp file are listed in the file.

ComputerName _w3wp.out

Crash dump data

The following files are generated and collected when you select the The application is crashing or terminating unexpectedly option when you are prompted by the diagnostic tool. For crash scenarios, the diagnostic tool waits for any second chance exceptions to occur and then creates a .dmp file for that process.

Collapse this tableExpand this table

Description

File name

A text file contains the name of the .zip file that is generated by the diagnostic tool. The .zip file name and parent folder location are provided.

ComputerName _DumpFile_Information.txt

A .zip file contains a compressed .dmp file.

ComputerName _w3wp.zip

A text file contains output information from the ProcDump tool. For example, the location and name of the uncompressed .dmp file are listed in the file.

ComputerName _w3wp.out

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
973559

(http://support.microsoft.com/kb/973559/
)

  Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) when it is used with Windows 7 or Windows Server 2008 R2  

Article ID: 2620926 – Last Review: August 28, 2012 – Revision: 3.0


Applies to
  • Microsoft Dynamics CRM 4.0
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM for Microsoft Office Outlook
kbmbsmigrate kbsurveynew KB2620926

Follow this link:
SDP 361593d1b-21b0-43e3-9088-74e77dec12f4 Microsoft Dynamics CRM client for Outlook diagnostic tool

Service overview and network port requirements for Windows

This article discusses the required network ports, protocols, and services that are used by Microsoft client and server operating systems, server-based programs, and their subcomponents in the Microsoft Windows server system. Administrators and support professionals may use this Microsoft Knowledge Base article as a road-map to determine what ports and protocols Microsoft operating systems and programs require for network connectivity in a segmented network.

You should not use the port information in this article to configure Windows Firewall. For information about how to configure Windows Firewall, see the Windows Firewall website.

The Windows server system includes a comprehensive and integrated infrastructure to meet the requirements of developers and information technology (IT) professionals. This system runs programs and solutions that you can use to obtain, analyze, and share information quickly and easily. These Microsoft client, server, and server program products use different network ports and protocols to communicate with client systems and with other server systems over the network. Dedicated firewalls, host-based firewalls, and Internet Protocol security (IPsec) filters are other important components that you must have to help secure your network. However, if these technologies are configured to block ports and protocols that are used by a specific server, that server will no longer respond to client requests.

Overview

The following list provides an overview of the information that
this article contains:

  • The “System services
    ports
    ” section contains a brief description of each service, displays the logical name of that service, and indicates the ports and protocols that each service requires for correct operation. Use this section to help identify the ports and protocols that a particular service uses.
  • The “Ports and
    protocols
    ” section includes a table that summarizes the information from the “System Services Ports” section. The table is sorted by the port number instead of by the service name. Use this section to quickly determine which services listen on a particular port.

This article uses certain terms in specific ways. To help avoid confusion, make sure that you understand how this document uses the following terms:  

  • System services: System services are programs that load automatically as part of an application’s startup process or as part of the operating system startup process. System services support the different tasks that the operating system must perform. For example, some system services that are available on computers that run Windows Server 2003 Enterprise Edition include the Server service, the Print Spooler service, and the World Wide Web Publishing service. Each system service has a friendly service name and a service name. The friendly service name is the name that appears in graphical management tools such as the Services Microsoft Management Console (MMC) snap-in. The service name is the name that is used with command-line tools and with many scripting languages. Each system service may provide one or more network services.
  • Application protocol: In this article, application protocol refers to a high-level network protocol that uses one or more TCP/IP protocols and ports. Examples of application protocols include Hypertext Transfer Protocol (HTTP), server message blocks (SMBs), and Simple Mail Transfer Protocol (SMTP).
  • Protocol: Operating at a lower level than the application protocols,
    TCP/IP protocols are standard formats for communicating between devices on a
    network. The TCP/IP suite of protocols includes TCP, User Datagram Protocol
    (UDP), and Internet Control Message Protocol (ICMP).
  • Port: This is the network port that the system service listens on for
    incoming network traffic.

This article does not specify which services rely on other
services for network communication. For example, many services rely on the
remote procedure call (RPC) or DCOM features in Microsoft Windows to assign
them dynamic TCP ports. The Remote Procedure Call service coordinates requests
by other system services that use RPC or DCOM to communicate with client
computers. Many other services rely on network basic input/output system
(NetBIOS) or SMBs, protocols that are actually provided by the Server service.
Others rely on HTTP or on Hypertext Transfer Protocol Secure (HTTPS). These
protocols are provided by Internet Information Services (IIS). A full
discussion of the architecture of the Windows operating systems is beyond the
scope of this article. However, detailed documentation on this subject is
available on Microsoft TechNet and on the Microsoft Developer Network (MSDN).
While many services may rely on a particular TCP or UDP port, only a single
service or process can be actively listening on that port at any one
time.

 When you use RPC with TCP/IP or with UDP/IP as the transport, incoming ports are frequently dynamically assigned to system services as required; TCP/IP and UDP/IP ports that are higher than port 1024 are used. These are frequently informally referred to as “random RPC ports.” In these cases, RPC clients rely on the RPC endpoint mapper to tell them which dynamic port(s) were assigned to the server. For some RPC-based services, you can configure a specific port instead of letting RPC assign one dynamically. You can also restrict the range of ports that RPC dynamically assigns to a small range, regardless of the service. For more information about this topic, see the “References” section of this article.

This article includes
information about the system services roles and the server roles for the
Microsoft products that are listed in the “Applies to” section at the end of
this article. While this information may also apply to Microsoft Windows XP and
to Microsoft Windows 2000 Professional, this article is intended to focus on
server-class operating systems. Because of this, this article describes the
ports that a service listens on instead of the ports that client programs use
to connect to a remote system.

System services ports

This section provides a description of each system service, includes the logical name that corresponds to the system service, and displays the ports and the protocols that each service requires.

Click the name of a system service in the following list to see the description:

Active Directory (Local Security Authority)

Active Directory runs under the LSASS process and includes the authentication and replication engines for Windows domain controllers. Domain controllers, client computers and application servers require network connectivity to Active Directory over specific hard-coded ports in addition to a range of ephemeral TCP ports between 1024 to 5000 and 49152 to 65535 unless a tunneling protocol is used to encapsulate such traffic.

Collapse this imageExpand this image

Note:

  • If your computer network environment uses only Windows Server 2008 R2, Windows Server 2008, Windows 7 or Windows Vista, you must enable connectivity over the high port range of 49152 through 65535.
  • If your computer network environment uses Windows Server 2008 R2, Windows Server 2008, Windows 7 or Windows Vista together with versions of Windows earlier than Windows Server 2008 and Windows Vista, you must enable connectivity over both port ranges:
    • over the high port range of 49152 through 65535
    • over the low port range of 1025 through 5000
  • If your computer network environment uses only versions of Windows earlier than Windows Server 2008 and Windows Vist, you must enable connectivity over the low port range of 1025 through 5000.

An encapsulated solution might consist of a VPN gateway located behind a filtering router using Layer 2 Tunneling Protocol (L2TP) together with IPsec. In this encapsulated scenario, you must allow IPsec Encapsulating Security Protocol (ESP) (IP protocol 50), IPsec Network Address Translator Traversal NAT-T (UDP port 4500), and IPsec Internet Security Association and Key Management Protocol (ISAKMP) (UDP port 500) through the router as opposed to opening all the ports and protocols listed below. Finally, the port used for Active Directory replication may be hard-coded as described in the Microsoft Knowledge Base article 224196: Restricting Active Directory replication traffic and client RPC traffic to a specific port

Collapse this imageExpand this image

Note Packet filters for L2TP traffic are not required, because L2TP is
protected by IPsec ESP.

Collapse this tableExpand this table

Application protocol Protocol Ports
Active Directory Web Services (ADWS) TCP 9389
Active Directory Management Gateway Service TCP 9389
Global Catalog Server TCP 3269
Global Catalog Server TCP 3268
LDAP Server TCP 389
LDAP Server UDP 389
LDAP SSL TCP 636
IPsec ISAKMP UDP 500
NAT-T UDP 4500
RPC TCP 135
RPC randomly allocated high TCP ports¹ TCP 1024 – 5000
49152 – 65535²

System service name: LSASS ¹ For more information about how to customize this port, see
the “Domain controllers and Active Directory” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista.


Application Layer Gateway Service


This subcomponent of the Internet Connection Sharing (ICS)/Internet Connection Firewall (ICF) service provides support for plug-ins that allow network protocols to pass through the firewall and work behind Internet Connection Sharing. Application Layer Gateway (ALG) plug-ins can open ports and change data (such as ports and IP addresses) that are embedded in packets. File Transfer Protocol (FTP) is the only network protocol with a plug-in that is included with Windows Server. The ALG FTP plug–in supports active FTP sessions through the network address translation (NAT) engine that these components use. The ALG FTP plug–in supports these sessions by redirecting all traffic that passes through the NAT and that is destined for port 21 to a private listening port in the range of 3000 to 5000 on the loopback adapter. The ALG FTP plug–in then monitors and updates FTP control channel traffic so that the FTP plug-in can forward port mappings through the NAT for the FTP data channels. The FTP plug–in also updates ports in the FTP control channel stream. 

System service name: ALG

Collapse this tableExpand this table

Application protocol Protocol Ports
FTP control TCP 21


ASP.NET State Service


ASP.NET State Service provides support for ASP.NET out-of-process
session states. ASP.NET State Service stores session data out-of-process. The
service uses sockets to communicate with ASP.NET that is running on a Web
server.

System service name: aspnet_state

Collapse this tableExpand this table

Application protocol Protocol Ports
ASP.NET Session State TCP 42424


Certificate Services


Certificate Services is part of the core operating system. By
using Certificate Services, a business can act as its own certification
authority (CA). In this way, the business can issue and manage digital
certificates for programs and protocols such as Secure/Multipurpose Internet
Mail Extensions (S/MIME), Secure Sockets Layer (SSL), Encrypting File System
(EFS), IPsec, and smart card logon. Certificate Services relies on RPC and on
DCOM to communicate with clients by using random TCP ports that are higher than
port 1024.

System service name: CertSvc

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Remote Procedure Calls and DCOM” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista.


Cluster Service


The Cluster service controls server cluster operations and
manages the cluster database. A cluster is a collection of independent
computers that act as a single computer. Managers, programmers, and users see
the cluster as a single system. The software distributes data among the nodes
of the cluster. If a node fails, other nodes provide the services and data that
was formerly provided by the missing node. When a node is added or repaired,
the cluster software migrates some data to that node.

System service
name: ClusSvc

Collapse this tableExpand this table

Application protocol Protocol Ports
Cluster Services UDP 3343
RPC TCP 135
Cluster
Administrator
UDP 137
Randomly allocated high UDP
ports¹
UDP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Remote Procedure Calls and DCOM” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista


Computer Browser


The Computer Browser system service maintains an up-to-date list
of computers on your network and supplies the list to programs that request it.
The Computer Browser service is used by Windows-based computers to view network
domains and resources. Computers that are designated as browsers maintain
browse lists that contain all shared resources that are used on the network.
Earlier versions of Windows programs, such as My Network Places, the net view command, and Windows Explorer, all require browsing capability.
For example, when you open My Network Places on a computer that is running
Microsoft Windows 95, a list of domains and computers appears. To display this
list, the computer obtains a copy of the browse list from a computer that is
designated as a browser.

If you are running only Windows Vista and nwer operating systems, the browser service is not required anymore.

System service name:
Browser

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139

 Browser service is using RPC over Named Pipes to compile browse lists between Master Browsers and the Domain Master Browser. So you need the ports that support domain NETBIOS name resolution and SMB.


DHCP Server


The DHCP Server service uses the Dynamic Host Configuration
Protocol (DHCP) to automatically allocate IP addresses. By using this service,
you can adjust the advanced network settings of DHCP clients. For example, you
can configure network settings such as Domain Name System (DNS) servers and
Windows Internet Name Service (WINS) servers. You can establish one or more
DHCP servers to maintain TCP/IP configuration information and to provide that
information to client computers.

System service name:
DHCPServer

Collapse this tableExpand this table

Application protocol Protocol Ports
DHCP Server UDP 67
MADCAP UDP 2535
DHCP Failover TCP 647


Distributed File System


The Distributed File System (DFS) integrates disparate file shares
that are located across a local area network (LAN) or wide area network (WAN)
into a single logical namespace. The DFS service is required for Active
Directory domain controllers to advertise the SYSVOL shared folder.

System service name: Dfs

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138³
NetBIOS Session Service TCP 139³
LDAP Server TCP 389
LDAP Server UDP 389
SMB TCP 445
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Remote Procedure Calls and DCOM” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista
³ The NETBIOS ports are optional and not needed when DFS is using FQDN Server names.


Distributed File System Replication


The Distributed File System Replication (DFSR) service is a
state-based, multi-master file replication engine that automatically copies
updates to files and folders between computers that are participating in a
common replication group. DFSR was added in Windows Server 2003 R2. You can
configure DFSR by using the Dfsrdiag.exe command-line tool to replicate files
on specific ports, regardless of
whether they are participating in Distributed File System Namespaces (DFSN) or
not.

System service name: DFSR

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
RPC TCP 5722³
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Distributed File Replication Service” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista
³ Port 5722 is only used on 2008 domain controller or 2008R2 domain controller.


Distributed Link Tracking Server


The Distributed Link Tracking Server system service stores
information so that files that are moved between volumes can be tracked to each
volume in the domain. The Distributed Link Tracking Server service runs on each
domain controller in a domain. This service enables the Distributed Link
Tracking Client service to track linked documents that have been moved to a
location in another NTFS file system volume in the same domain.

System service name: TrkSvr

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Remote Procedure Calls and DCOM” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista


Distributed Transaction Coordinator


The Distributed Transaction Coordinator (DTC) system service is
responsible for coordinating transactions that are distributed across multiple
computer systems and resource managers, such as databases, message queues, file
systems, or other transaction-protected resource managers. The DTC system
service is required if transactional components are configured through COM+. It
is also required for transactional queues in Message Queuing (also known as
MSMQ) and SQL Server operations that span multiple systems.

System
service name: MSDTC

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Distributed Transaction Coordinator” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista


DNS Server


The DNS Server service enables DNS name resolution by answering
queries and update requests for DNS names. DNS servers are required to locate
devices and services that are identified by using DNS names and to locate
domain controllers in Active Directory.

System service name:
DNS

Collapse this tableExpand this table

Application protocol Protocol Ports
DNS UDP 53
DNS TCP 53


Event Log


The Event Log system service logs event messages that are
generated by programs and by the Windows operating system. Event Log reports
contain information that can be useful in diagnosing problems. Reports are
viewed in Event Viewer. The Event Log service writes events that are sent by
programs, by services, and by the operating system to log files. The events
contain diagnostic information in addition to errors that are specific to the
source program, the service, or the component. The logs can be viewed
programmatically through the event log APIs or through the Event Viewer in an
MMC snap-in.

System service name: Eventlog

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC/named pipes (NP) TCP 139
RPC/NP TCP 445
RPC/NP UDP 137
RPC/NP UDP 138

Collapse this imageExpand this image

Note The Event Log service uses RPC over named pipes. This service has
the same firewall requirements as those of the “File and Printer Sharing”
feature.


Microsoft Exchange Server and Outlook clients


Versions of Microsoft Exchange Server and Exchange clients have
various port and protocol requirements. These requirements depend upon which
version of Exchange Server or Exchange client is in use.

For Outlook
clients to connect to versions of Exchange prior to Exchange 2003, direct RPC
connectivity to the Exchange server is required. RPC connections made from
Outlook to the Exchange server will first contact the RPC endpoint mapper (Port
TCP 135) to request information on the port mappings of the various endpoints
required. The Outlook client then tries to make connections to the Exchange
server directly by using these endpoint ports.

Exchange 5.5 uses two
ports for client communication. One port is for the Information Store, and one
port is for the Directory. Exchange 2000 and 2003 use three ports for client
communication. One port is for the Information Store, one is for Directory
Referral (RFR), and one port is for DSProxy/NSPI.

In most cases, these
two or three ports will be mapped randomly into the range TCP 1024-65535. If
required, these ports can be configured to always bind to a static port mapping
rather than to use the ephemeral ports.

For more information about how to configure static TCP/IP ports in Exchange Server, see Microsoft Knowledge Base article 270836: Exchange Server static port mappings
Outlook 2003 clients support direct connectivity to
Exchange servers by using RPC. However, these clients can also communicate with
Exchange 2003 servers that are hosted on Windows Server 2003-based computers on
the Internet. The use of RPC over HTTP communication between Outlook and
Exchange server eliminates the need to expose unauthenticated RPC traffic
across the Internet. Instead, traffic between the Outlook 2003 client and the
Exchange Server 2003 computer is tunneled within HTTPS packets over TCP port
443 (HTTPS).

RPC over HTTPS requires that port TCP 443 (HTTPS) be
available between the Outlook 2003 client and the server that is functioning as
the “RPCProxy” device. The HTTPS packets are terminated at the RPCProxy server
and the unwrapped RPC packets are then passed to the Exchange server on three
ports, in similar fashion to the direct RPC traffic described above. These RPC
over HTTPS ports on the Exchange server are statically mapped to TCP 6001 (the
Information Store), TCP 6002 (Directory Referral), and TCP 6004 (DSProxy/NSPI).
No endpoint mapper must be exposed when using RPC over HTTPS communication
between Outlook 2003 and Exchange 2003, since Outlook 2003 knows to use these
statically mapped endpoint ports. In addition, no global catalog needs to be
exposed to the Outlook 2003 client because the DSProxy/NSPI interface on the
Exchange 2003 server will provide this functionality.

Exchange Server
can also provide support for other protocols, such as SMTP, Post Office
Protocol 3 (POP3), and IMAP.

Collapse this tableExpand this table

Application protocol Protocol Ports
IMAP TCP 143
IMAP over SSL TCP 993
POP3 TCP 110
POP3 over SSL TCP 995
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²
RPC TCP 135
RPC over HTTPS TCP 443 or 80
SMTP TCP 25
SMTP UDP 25
Information Store TCP 6001
Directory Referral TCP 6002
DSProxy/NSPI TCP 6004

¹ For more information about how to customize this port, see
the “Remote Procedure Calls and DCOM” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista.


ISA Server

Collapse this tableExpand this table

Application protocol Protocol Ports
Configuration Storage (domain) TCP 2171
(note 1)
Configuration Storage (replication) TCP 2173
(note 1)
Configuration Storage (workgroup) TCP 2172
(note 1)
Firewall Client
Application
TCP/UDP 1025-65535 (note 2)
Firewall Client Control Channel TCP/UDP 1745
(note 3)
Firewall Control Channel TCP 3847 (note
1)
RPC TCP 135 (note 6)
Randomly allocated high TCP ports (note
6)
TCP random port number between 1024 – 65535
random port
number between 49152 – 65535 (note 7)
Web Management TCP 2175 (note 1, 4)
Web Proxy Client TCP 8080 (note 5)

Collapse this imageExpand this image

Notes:

  1. Not used with ISA 2000
  2. FWC application transport / protocols are negotiated within
    the FWC control channel
  3. ISA 2000 FWC control defaults to UDP; ISA 2004 and 2006
    default to TCP.
  4. Firewall Web Management is used by OEM to provide non-MMC
    management of ISA Server
  5. Also used for intra-array traffic.
  6. Used only by the ISA management MMC during remote server
    and service status monitoring.
  7. This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows
    Vista.


Fax Service

Fax Service, a Telephony API (TAPI)–compliant system service,
provides fax capabilities. By using Fax Service, users can send and receive
faxes from their desktop programs by using either a local fax device or a
shared network fax device.

System service name: Fax

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Session Service TCP 139
SMB TCP 445
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “Remote Procedure Calls and DCOM” section in the “References”
section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows Vista.


File Replication


The File Replication service (FRS) is a file-based replication
engine that automatically copies updates to files and folders between computers
that are participating in a common FRS replica set. FRS is the default
replication engine that is used to replicate the contents of the SYSVOL folder
between Windows 2000-based and Windows Server 2003-based domain controllers
that are located in a common domain. FRS may be configured to replicate files
and folders between targets of a DFS root or link by using the DFS
Administration tool.

System service name: NtFrs

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see
the “File Replication Service” section in the “References” section.
² This
is the rangeWindows Server 2008 R2, Windows 7, in Windows Server 2008 and in Windows Vista.


File Server for Macintosh


By using the File Server for Macintosh system service, Macintosh
computer users can store and access files on a computer that is running Windows
Server 2003. If this service is turned off or blocked, Macintosh clients cannot
access or store files on that computer. File Server for Macintosh is not included in Windows Server 2008, or later versions of Windows.

System service name:
MacFile

Collapse this tableExpand this table

Application protocol Protocol Ports
File Server for Macintosh TCP 548


FTP Publishing Service

FTP Publishing Service provides FTP connectivity. By default, the
FTP control port is 21. However, you can configure this system service through
the Internet Information Services (IIS) Manager snap-in. The default data (that
is used for active mode FTP) port is automatically set to one port less than
the control port. Therefore, if you configure the control port to port 4131,
the default data port is port 4130. Most FTP clients use passive mode FTP. This
means that the client initially connects to the FTP server by using the control
port, the FTP server assigns a high TCP port between ports 1025 and 5000, and
then the client opens a second connection to the FTP server for transferring
data. You can configure the range of high ports by using the IIS metabase.

System service name: MSFTPSVC

Collapse this tableExpand this table

Application protocol Protocol Ports
FTP control TCP 21
FTP default data TCP 20
Rrandomly allocated high TCP
ports
TCP random port number between 1024 -
65535

random port number between 49152 -
65535¹

¹ This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008 and in Windows
Vista.


Group Policy


To successfully apply Group Policy, a client computer must be able to contact a domain controller over the Kerberos, ICMP, LDAP, SMB, and RPC protocols. If any one of these protocols are unavailable or blocked between the client and a relevant domain controller, Group Policy will not apply or update. For a cross-domain logon, where a computer is in one domain and the user account is in another domain, these protocols may be required for the client, the resource domain, and the account domain to communicate. ICMP is used for slow link detection. For more information about slow link detection, see the following Microsoft Knowledge Base article: 227260: How a slow link is detected for processing user profiles and Group PolicyGroup Policy Slow Link Detection Using Windows Vista and Server 2008

System service name: Group Policy

Collapse this tableExpand this table

Application protocol Protocol Ports
DCOM ¹ TCP + UDP random port
number between 1024 – 65535

random port number
between 49152 – 65535²
ICMP (ping) ICMP
LDAP TCP 389
SMB TCP 445
RPC ¹ TCP 135, random port number
between 1024 – 65535
²

¹ For more information about how to customize this port, see “Domain controllers and Active Directory” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and in Windows Vista.

Collapse this imageExpand this image

Note When the Group Policy Microsoft Management Console (MMC) snap-in creates Group Policy Results reports and Group Policy Modeling reports, it uses DCOM and RPC to send and to receive information from the Resultant Set of Policy (RSoP) provider on the client or on the domain controller. The various binary files that make up the Group Policy Microsoft Management Console (MMC) snap-in features primarily use COM calls to send or to receive information.


HTTP SSL


The HTTP SSL system service enables IIS to perform SSL functions. SSL is an open standard for establishing an encrypted communications channel to help prevent the interception of extremely important information, such as credit card numbers. Although this service works on other Internet services, it is primarily used to enable encrypted electronic financial transactions on the World Wide Web (WWW). You can configure the ports for this service through the Internet Information Services (IIS) Manager snap-in. 

System
service name: HTTPFilter

Collapse this tableExpand this table

Application protocol Protocol Ports
HTTPS TCP 443


Internet Authentication Service


Internet Authentication Service (IAS) performs centralized
authentication, authorization, auditing, and accounting of users who are
connecting to a network. These users can be on a LAN connection or on a remote
connection. IAS implements the Internet Engineering Task Force (IETF) standard
Remote Authentication Dial-In User Service (RADIUS) protocol.

System
service name: IAS

Collapse this tableExpand this table

Application protocol Protocol Ports
Legacy RADIUS UDP 1645
Legacy RADIUS UDP 1646
RADIUS Accounting UDP 1813
RADIUS Authentication UDP 1812


Internet Connection Firewall (ICF)/Internet Connection Sharing


This system service provides NAT, addressing, and name resolution services for all computers on your home network or your small-office network. When the Internet Connection Sharing feature is enabled, your computer becomes an “Internet gateway” on the network. Other client computers can then share one connection to the Internet, such as a dial-up connection or a broadband connection. This service provides basic DHCP and DNS services but will work with the full-featured Windows DHCP or DNS services. When ICF and Internet Connection Sharing act as a gateway for the rest of the computers on your network, they provide DHCP and DNS services to the private network on the internal network interface. They do not provide these services on the external network interface. 

System service name:
SharedAccess

Collapse this tableExpand this table

Application protocol Protocol Ports
DHCP Server UDP 67
DNS UDP 53
DNS TCP 53


Kerberos Key Distribution Center


When you use the Kerberos Key Distribution Center (KDC) system
service, users can log on to the network by using the Kerberos version 5
authentication protocol. As in other implementations of the Kerberos protocol,
the KDC is a single process that provides two services: the Authentication
Service and the Ticket-Granting Service. The Authentication Service issues
ticket granting tickets, and the Ticket-Granting Service issues tickets for
connection to computers in its own domain.

System service name:
kdc

Collapse this tableExpand this table

Application protocol Protocol Ports
Kerberos TCP 88
Kerberos UDP 88
Kerberos Password V5 UDP 464
Kerberos Password V5 TCP 464
DC Locator UDP 389


License Logging


The License Logging system service is a tool that was originally designed to help customers manage licenses for Microsoft server products that are licensed in the Server Client Access License (CAL) model. License Logging was introduced with Microsoft Windows NT Server 3.51. By default, the License Logging service is disabled in Windows Server 2003. Because of legacy design constraints and evolving license terms and conditions, License Logging may not provide an accurate view of the total number of CALs that are purchased compared to the total number of CALs that are used on a particular server or across the enterprise. The CALs that are reported by License Logging may conflict with the interpretation of the Microsoft Software License Terms and with Product Use Rights (PUR). License Logging will not be included in future versions of the Windows operating system. We recommend that only users of the Microsoft Small Business Server family of operating systems enable this service on their servers.

System service name:
LicenseService

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138
NetBIOS Session Service TCP 139
SMB TCP 445

Collapse this imageExpand this image

Note The License Logging service uses RPC over named pipes. This service has the same firewall requirements as the “File and Printer Sharing” feature.


Message Queuing


The Message Queuing system service is a messaging infrastructure and development tool for creating distributed messaging programs for Windows. These programs can communicate across heterogeneous networks and can send messages between computers that may be temporarily unable to connect to one another. Message Queuing helps provide security, efficient routing, support for sending messages within transactions, priority-based messaging, and guaranteed message delivery. 

System service name: MSMQ

Collapse this tableExpand this table

Application protocol Protocol Ports
MSMQ TCP 1801
MSMQ UDP 1801
MSMQ-DCs TCP 2101
MSMQ-Mgmt TCP 2107
MSMQ-Ping UDP 3527
MSMQ-RPC TCP 2105
MSMQ-RPC TCP 2103
RPC TCP 135


Messenger


The Messenger system service sends messages to or receives messages from users and computers, administrators, and the Alerter service. This service is not related to Windows Messenger. If you disable the Messenger service, notifications that are sent to computers or users who are currently logged on to the network are not received. Additionally, the net send command and the net name command no longer function.

In many customer environments this service is disabled. Therefore, you do not have to enable NETBIOS for this service.

System service name:
Messenger

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138


Microsoft Exchange MTA Stacks


In Microsoft Exchange 2000 Server and Microsoft Exchange Server
2003, the Message Transfer Agent (MTA) is frequently used to provide
backward-compatible message transfer services between Exchange 2000
Server-based servers and Exchange Server 5.5-based servers in a mixed-mode
environment.

System service name: MSExchangeMTA

Collapse this tableExpand this table

Application protocol Protocol Ports
X.400 TCP 102


Microsoft Operations Manager 2000


Microsoft Operations Manager (MOM) 2000 delivers enterprise-class
operations management by providing comprehensive event management, proactive
monitoring and alerting, reporting, and trend analysis. After you install MOM
2000 Service Pack 1 (SP1), MOM 2000 no longer uses a clear text communications
channel, and all traffic between the MOM agent and the MOM server is encrypted
over TCP port 1270. The MOM Administrator console uses DCOM to connect to the
server. This means that administrators who manage the MOM server over the
network must have access to random high TCP ports.

System service
name: one point

Collapse this tableExpand this table

Application protocol Protocol Ports
MOM-Clear TCP 51515
MOM-Encrypted TCP 1270


Microsoft POP3 Service


The Microsoft POP3 service provides email transfer and retrieval services. Administrators can use this service to store and manage email accounts on the mail server. When you install Microsoft POP3 Service on the mail server, users can connect to the mail server and can retrieve email messages by using an email client that supports the POP3 protocol, such as Microsoft Outlook. 

System service name: POP3SVC

Collapse this tableExpand this table

Application protocol Protocol Ports
POP3 TCP 110


MSSQLSERVER


MSSQLSERVER is a system service in Microsoft SQL Server 2000. SQL
Server provides a powerful and comprehensive data management platform. You can
configure the ports that each instance of SQL Server uses by using the Server
Network Utility.

System service name: MSSQLSERVER

Collapse this tableExpand this table

Application protocol Protocol Ports
SQL over TCP TCP 1433
SQL Probe UDP 1434


MSSQL$UDDI


The MSSQL$UDDI system service is installed during the installation
of the Universal Description, Discovery, and Integration (UDDI) feature of the
Windows Server 2003 family of operating systems. MSSQL$UDDI provides UDDI
capabilities in an enterprise. The SQL Server database engine is the core
component of MSSQL$UDDI.

System service name:
MSSQLSERVER

Collapse this tableExpand this table

Application protocol Protocol Ports
SQL over TCP TCP 1433
SQL Probe UDP 1434


Net Logon


The Net Logon system service maintains a security channel between your computer and the domain controller to authenticate users and services. It passes the user’s credentials to a domain controller and returns the domain security identifiers and the user rights for the user. This is typically known as pass-through authentication. Net Logon is configured to start automatically only when a member computer or domain controller is joined to a domain. In the Windows 2000 Server and Windows Server 2003 families, Net Logon publishes service resource locator records in the DNS. When this service runs, it relies on the WORKSTATION service and on the Local Security Authority service to listen for incoming requests. On domain member computers, Net Logon uses RPC over named pipes. On domain controllers, it uses RPC over named pipes, RPC over TCP/IP, mail slots, and Lightweight Directory Access Protocol (LDAP). 

System service name: Netlogon

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138 ³
NetBIOS Name Resolution UDP 137 ³
NetBIOS Session Service TCP 139 ³
SMB TCP 445
LDAP UDP 389
RPC¹ TCP 135, random port number
between 1024 – 65535

135, random port number
between 49152 – 65535²

¹ For more information about how to customize this port, see “Domain controllers and Active Directory” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista.
³ The NETBIOS ports are optional. Netlogon uses these only for trusts that don’t support DNS or when DNS fails during an attempted fallback. If there is no WINS infrastructure and boradcasts can’t work, you should either disable NetBt or set the machines to NodeType=2.

Collapse this imageExpand this image

Note The Net Logon service uses RPC over named pipes for earlier versions of Windows clients. This service has the same firewall requirements as the “File and Printer Sharing” feature.


NetMeeting Remote Desktop Sharing


The NetMeeting Remote Desktop Sharing system service allows authorized users to use Windows NetMeeting to remotely access your Windows desktop from another personal computer over a corporate intranet. You must explicitly enable this service in NetMeeting. You can disable or shut down this feature by using an icon that is displayed in the Windows notification area. 

System
service name: mnmsrvc

Collapse this tableExpand this table

Application protocol Protocol Ports
Terminal Services TCP 3389


Network News Transfer Protocol (NNTP)


The Network News Transfer Protocol (NNTP) system service lets computers that are running Windows Server 2003 act as news servers. Clients can use a news client, such as Microsoft Outlook Express, to retrieve newsgroups from the server and to read the headers or the bodies of the articles in each newsgroup. 

System service name:
NNTPSVC

Collapse this tableExpand this table

Application protocol Protocol Ports
NNTP TCP 119
NNTP over SSL TCP 563


Performance Logs and Alerts


The Performance Logs and Alerts system service collects performance data from local or remote computers based on preconfigured schedule parameters and then writes that data to a log or triggers a message. Based on the information that is contained in the named log collection setting, the Performance Logs and Alerts service starts and stops each named performance data collection. This service runs only if at least one performance data collection is scheduled. 

System service name:
SysmonLog

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Session Service TCP 139


Print Spooler


The Print Spooler system service manages all local and network
print queues and controls all print jobs. Print Spooler is the center of the
Windows printing subsystem. It manages the print queues on the system and
communicates with printer drivers and input/output (I/O) components, such as
the USB port and the TCP/IP protocol suite.

System service name:
Spooler

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139
SMB TCP 445

Collapse this imageExpand this image

Note The Print Spooler service uses RPC over named pipes. This service has the same firewall requirements as the “File and Printer Sharing” feature.


Remote Installation


You can use the Remote Installation system service to install Windows 2000, Windows XP, and Windows Server 2003 on Pre-Boot Execution Environment (PXE) remote boot-enabled client computers. The Boot Information Negotiation Layer (BINL) service, the primary component of Remote Installation Server (RIS), answers PXE client requests, checks Active Directory for client validation, and passes client information to and from the server. The BINL service is installed when you add the RIS component from Add/Remove Windows Components, or you can select it when you first install the operating system.

System service name: BINLSVC

Collapse this tableExpand this table

Application protocol Protocol Ports
BINL UDP 4011


Remote Procedure Call (RPC)


The Remote Procedure Call (RPC) system service is an interprocess communication (IPC) mechanism that enables data exchange and invocation of functionality that is located in a different process. The different process can be on the same computer, on the LAN, or in a remote location, and it can be accessed over a WAN connection or over a VPN connection. The RPC service serves as the RPC Endpoint Mapper and Component Object Model (COM) Service Control Manager. Many services depend on the RPC service to start successfully. 

System service name: RpcSs

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
RPC over HTTPS TCP 593
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139
SMB TCP 445

Collapse this imageExpand this image

Notes

  • RPC does not use only the hard-coded ports that are listed in the table. Ephemeral range ports that are used by Active Directory and other components occur over RPC in the ephemeral port range. The ephemeral port range depends on the server operating system that the client operating system is connected to.
  • The RPC Endpoint Mapper also offers its services by using named pipes. This service has the same firewall requirements as the “File and Printer Sharing” feature.

 


Remote Procedure Call (RPC) Locator


The Remote Procedure Call (RPC) Locator system service manages the RPC name service database. When this service is turned on, RPC clients can locate RPC servers. By default, this service is turned off. 

System
service name: RpcLocator

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139
SMB TCP 445

Collapse this imageExpand this image

Note The RPC Locator service offers its services by using RPC over named pipes. This service has the same firewall requirements as the “File and Printer Sharing” feature.


Remote Storage Notification


The Remote Storage Notification system service notifies users when they read from or write to files that are available only from a secondary storage media. Stopping this service prevents this notification.

System service name: Remote_Storage_User_Link

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see “Remote Procedure Calls and DCOM” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and in Windows Vista.


Remote Storage


The Remote Storage system service stores infrequently used files on a secondary storage medium. If you stop this service, users cannot move or retrieve files from the secondary storage media. 

System
service name: Remote_Storage_Server

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see “Remote Procedure Calls and DCOM” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and in Windows Vista.


Routing and Remote Access


The Routing and Remote Access service provides multiprotocol LAN-to-LAN, LAN-to-WAN, VPN, and NAT routing services. The Routing and Remote Access service also provides dial-up and VPN remote access services. Although the Routing and Remote Access service can use all the following protocols, the service typically uses only a few of them. For example, if you configure a VPN gateway that lies behind a filtering router, you will probably use only one protocol. If you use L2TP with IPsec, you must allow IPsec ESP (IP protocol 50), NAT-T (UDP on port 4500), and IPsec ISAKMP (UDP on port 500) through the router.

Collapse this imageExpand this image

Note Although NAT-T and IPsec ISAKMP are required for L2TP, these ports are monitored by the Local Security Authority. For more information about this, see the “References” section.  

System service name: RemoteAccess

Collapse this tableExpand this table

Application protocol Protocol Ports
GRE (IP protocol 47) GRE n/a
IPsec AH (IP protocol 51) AH n/a
IPsec ESP (IP protocol 50) ESP n/a
L2TP UDP 1701
PPTP TCP 1723


Server


The Server system service provides RPC support and file sharing, print sharing, and named pipe sharing over the network. The Server service lets users share local resources, such as disks and printers, so that other users on the network can access them. It also enables named pipe communication between programs that are running on the local computer and on other computers. Named pipe communication is memory that is reserved for the output of one process to be used as input for another process. The input-accepting process does not have to be local to the computer.

Collapse this imageExpand this image

Note If a computer name resolves to multiple IP addresses by using WINS, or if WINS failed and the name is resolved by using DNS, NetBIOS over TCP/IP (NetBT) tries to ping the IP address or addresses of the file server. Port 139 communications depend on Internet Control Message Protocol (ICMP) echo messages. If IP version 6 (IPv6) is not installed, port 445 communications will also depend on ICMP for name resolution. Preloaded Lmhosts entries will bypass the DNS resolver. If IPv6 is installed on computers that are running Windows Server 2003 or Windows XP operating systems, port 445 communications do not trigger ICMP requests.

The NetBIOS ports that are listed here are optional. Windows 2000 and newer clients can work over port 445.

System service name:
lanmanserver

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139
SMB TCP 445


SharePoint Portal Server


The SharePoint Portal Server system service lets you develop an intelligent portal that seamlessly connects users, teams, and knowledge. This helps people take advantage of relevant information across business processes. Microsoft SharePoint Portal Server 2003 provides an enterprise business solution that integrates information from various systems into one solution through single sign-on and enterprise application integration capabilities.  

Collapse this tableExpand this table

Application protocol Protocol Ports
HTTP TCP 80
HTTPS TCP 443


Simple Mail Transfer Protocol (SMTP)


The Simple Mail Transfer Protocol (SMTP) system service is an email submission and relay agent. It accepts and queues email messages for remote destinations, and it retries at set intervals. Windows domain controllers use the SMTP service for intersite e-mail-based replication. The Collaboration Data Objects (CDO) for the Windows Server 2003 COM component can use the SMTP service to submit and to queue outgoing email messages. 

System service name:
SMTPSVC

Collapse this tableExpand this table

Application protocol Protocol Ports
SMTP TCP 25


Simple TCP/IP Services


Simple TCP/IP Services implements support for the following
protocols:

  • Echo, port 7, RFC 862
  • Discard, port 9, RFC 863
  • Character Generator, port 19, RFC 864
  • Daytime, port 13, RFC 867
  • Quote of the Day, port 17, RFC 865

System service name: SimpTcp

Collapse this tableExpand this table

Application protocol Protocol Ports
Chargen TCP 19
Chargen UDP 19
Daytime TCP 13
Daytime UDP 13
Discard TCP 9
Discard UDP 9
Echo TCP 7
Echo UDP 7
Quotd TCP 17
Quoted UDP 17


SMS Remote Control Agent


SMS Remote Control Agent is a system service in Microsoft Systems
Management Server (SMS) 2003. SMS Remote Control Agent provides a comprehensive
solution for change and for configuration management for the Microsoft
operating systems. With this solution, organizations can provide relevant
software and updates to users.

System service name:
Wuser32

Collapse this tableExpand this table

Application protocol Protocol Ports
SMS Remote Chat TCP 2703
SMS Remote Chat UDP 2703
SMS Remote Control (control) TCP 2701
SMS Remote Control (control) UDP 2701
SMS Remote Control (data) TCP 2702
SMS Remote Control (data) UDP 2702
SMS Remote File Transfer TCP 2704
SMS Remote File Transfer UDP 2704


SNMP Service


SNMP Service lets the local computer service incoming Simple Network Management Protocol (SNMP) requests. SNMP Service includes agents that monitor activity in network devices and report to the network console workstation. SNMP Service provides a method of managing network hosts (such as workstation or server computers, routers, bridges, and hubs) from a centrally-located computer that is running network management software. SNMP performs management services by using a distributed architecture of management systems and agents. 

System service name: SNMP

Collapse this tableExpand this table

Application protocol Protocol Ports
SNMP UDP 161


SNMP Trap Service


SNMP Trap Service receives trap messages that are generated by local or by remote SNMP agents. Then the SNMP Trap Service forwards those messages to SNMP management programs that are running on your computer. When SNMP Trap Service is configured for an agent, the service generates trap messages if any specific events occur. These messages are sent to a trap destination. For example, an agent can be configured to start an authentication trap if an unrecognized management system sends a request for information. Trap destinations include the computer name, the IP address, or the Internetwork Packet Exchange (IPX) address of the management system. The trap destination must be a network-enabled host that is running SNMP management software.

System service name:
SNMPTRAP

Collapse this tableExpand this table

Application protocol Protocol Ports
SNMP Traps Outgoing UDP 162


SQL Server Analysis Services


The SQL Server Analysis Services system service is a component of SQL Server 2000. With SQL Analysis Server, you can create and manage online analytical processung (OLAP) cubes and data mining models. The Analysis service may access local or remote data sources for creating and storing cubes or data mining models.  

Collapse this tableExpand this table

Application protocol Protocol Ports
SQL Server Analysis Services TCP 2725


SQL Server: Downlevel OLAP Client Support


This system service is used by SQL Server 2000 when the SQL Server Analysis Server service has to support connections from downlevel (OLAP Services 7.0) clients. These are the default ports for OLAP services that are used by SQL 7.0.  

Collapse this tableExpand this table

Application protocol Protocol Ports
OLAP Services 7.0 TCP 2393
OLAP Services 7.0 TCP 2394


SSDP Discovery Service


SSDP Discovery Service implements Simple Service Discovery Protocol (SSDP) as a Windows service. SSDP Discovery Service manages receipt of device presence announcements, updates its cache, and sends these notifications to clients that have outstanding search requests. SSDP Discovery Service also accepts the registration of event callbacks from clients. The registered event callbacks are then turned into subscription requests. SSDP Discovery Service then monitors for event notifications and sends these requests to the registered callbacks. This system service also provides periodic announcements to hosted devices. Currently, the SSDP event notification service uses TCP port 5000. 

Collapse this imageExpand this image

Note Starting with Windows XP Service Pack 2 (SP2), the SSDP event notification service uses TCP port 2869.

System service name:
SSDPRSR

Collapse this tableExpand this table

Application protocol Protocol Ports
SSDP UDP 1900
SSDP event notification TCP 2869
SSDP legacy event notification TCP 5000


Systems Management Server 2.0


Microsoft Systems Management Server (SMS) 2003 provides a comprehensive solution for change and configuration management for Microsoft operating systems. Organizations can use SMS 2003 to quickly and cost-effectively provide relevant software and updates to users.  

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139
RPC TCP 135
SMB TCP 445
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see “Remote Procedure Calls and DCOM” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and in Windows Vista.

Collapse this imageExpand this image

Note SMS uses SMB to communicate. This service has the same firewall requirements as the File and Printer Sharing feature.


TCP/IP Print Server


The TCP/IP Print Server system service enables TCP/IP–based
printing by using the Line Printer Daemon (LPD) protocol. The LPD service on
the server receives documents from Line Printer Remote (LPR) utilities that are
running on UNIX computers.

System service name:
LPDSVC

Collapse this tableExpand this table

Application protocol Protocol Ports
LPD TCP 515


Telnet


The Telnet system service for Windows provides ASCII terminal sessions to Telnet clients. A Telnet server supports two kinds of authentication and supports the following kinds of terminals: 

American National Standards Institute (ANSI)
VT-100
VT-52
VTNT

System service name: TlntSvr

Collapse this tableExpand this table

Application protocol Protocol Ports
Telnet TCP 23


Terminal Services


Terminal Services provides a multi-session environment that enables client devices to access a virtual Windows desktop session and Windows-based programs that are running on the server. Terminal Services enables multiple users to be connected interactively to a computer. 

System
service name: TermService

Collapse this tableExpand this table

Application protocol Protocol Ports
Terminal Services TCP 3389


Terminal Services Licensing


The Terminal Services Licensing system service installs a license server and provides licenses to registered clients when the clients connect to a terminal server (a server that has Terminal Server enabled). Terminal Services Licensing is a low-impact service that stores the client licenses that are issued for a terminal server and tracks the licenses that are issued to client computers or terminals. 

System service name:
TermServLicensing

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²
NetBIOS Datagram Service UDP 138
NetBIOS Name Resolution UDP 137
NetBIOS Session Service TCP 139
SMB TCP 445

¹ For more information about how to customize this port, see “Remote Procedure Calls and DCOM” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and in Windows Vista.

Collapse this imageExpand this image

Note Terminal Services Licensing offers its services by using RPC over named pipes. This service has the same firewall requirements as the File and Printer Sharing feature.


Terminal Services Session Directory


The Terminal Services Session Directory system service enables clusters of load-balanced terminal servers to correctly route a user’s connection request to the server where the user already has a session running. Users are routed to the first-available terminal server regardless of whether they are running another session in the server cluster. The load-balancing functionality pools the processing resources of several servers by using the TCP/IP networking protocol. You can use this service with a cluster of terminal servers to increase the performance of a single terminal server by distributing sessions across multiple servers. Terminal Services Session Directory keeps track of disconnected sessions on the cluster and makes sure that users are reconnected to those sessions. 

System service name:
Tssdis

Collapse this tableExpand this table

Application protocol Protocol Ports
RPC TCP 135
Randomly allocated high TCP
ports¹
TCP random port number between 1024 -
65535

random port number between 49152 -
65535²

¹ For more information about how to customize this port, see “Remote Procedure Calls and DCOM” in the “References” section.
² This is the range in Windows Server 2008 R2, Windows 7, Windows Server 2008, and in Windows Vista.


Trivial FTP Daemon


The Trivial FTP Daemon system service does not require a user name or a password and is an important part of the Remote Installation Services (RIS). The Trivial FTP Daemon service implements support for the Trivial FTP Protocol (TFTP) that is defined by the following RFCs:

RFC 1350 – TFTP
RFC 2347 – Option extension
RFC 2348 – Block size option
RFC 2349 – Time-out interval, and transfer size options

Trivial File Transfer Protocol (TFTP) is an FTP that supports diskless startup environments. The TFTP service listens on UDP port 69, but it responds from a randomly allocated high port. Therefore, when you enable this port, the TFTP service receives incoming TFTP requests, but it does not let the selected server respond to those requests. The service is free to respond to any such request from any source port, and the remote client then uses that port during the transfer. Communication is bidirectional. If you have to enable this protocol through a firewall,you may want to open UDP port 69 incoming. You can then rely on other firewall features that dynamically let the service respond through temporary holes on any other port.

System service name:
tftpd

Collapse this tableExpand this table

Application protocol Protocol Ports
TFTP UDP 69


UPnP Device Host


The UPnP Device Host discovery system service implements all the components that are required for device registration, control, and the response to events for hosted devices. The information that is registered that relates to a device, such as the description, the lifetimes, and the containers, are optionally stored to disk and are announced on the network after registration or when the operating system restarts. The service also includes the web server that serves the device in addition to service descriptions and a presentation page. 

System service name:
UPNPHost

Collapse this tableExpand this table

Application protocol Protocol Ports
UPNP TCP 2869


Windows Internet Name Service (WINS)


Windows Internet Name Service (WINS) enables NetBIOS name resolution. This service helps you locate network resources by using NetBIOS names. WINS servers are required unless all domains have been upgraded to the Active Directory directory service and unless all computers on the network are running Windows 2000 or later versions. WINS servers communicate with network clients by using NetBIOS name resolution. WINS replication is only required between WINS servers. 

System service name: WINS

Collapse this tableExpand this table

Application protocol Protocol Ports
NetBIOS Name Resolution UDP 137
WINS Replication TCP 42
WINS Replication UDP 42


Windows Media Services


Windows Media Services in Windows Server 2003 and later versions replaces the following services that are included in Windows Media Services versions 4.0 and 4.1: 

Windows Media Monitor Service
Windows Media Program Service
Windows Media Station Service
Windows Media Unicast Service

Windows Media Services is now a single service that runs on Windows Server. Its core components were developed by using COM, and it has a flexible architecture that you can customize for specific programs. Windows Media Services supports a larger variety of control protocols. These include Real Time Streaming Protocol (RTSP), Microsoft Media Server (MMS) protocol, and HTTP.

System service name: WMServer

Collapse this tableExpand this table

Application protocol Protocol Ports
HTTP TCP 80
MMS TCP 1755
MMS UDP 1755
MS Theater UDP 2460
RTCP UDP 5005
RTP UDP 5004
RTSP TCP 554


Windows Time


The Windows Time system service maintains date and time synchronization on all the computers on a network that are running Windows XP or later versions and Windows Server 2003 or later versions. This service uses Network Time Protocol (NTP) to synchronize computer clocks so that an accurate clock value, or time stamp is assigned for network validation and for resource access requests. The implementation of NTP and the integration of time providers help make Windows Time a reliable and scalable time service for your business. For computers that are not joined to a domain, you can configure Windows Time to synchronize time with an external time source. If this service is turned off, the time setting for local computers is not synchronized with a time service in the Windows domain or with an externally configured time service. Windows Server 2003 uses NTP. NTP runs on UDP port 123. The Windows 2000 version of this service uses Simple Network Time Protocol (SNTP). SNTP also runs on UDP port 123. 

When the
Windows Time service uses a Windows domain configuration, the service requires
domain controller location and authentication services. Therefore, the ports
for Kerberos and DNS are required.

System service name:
W32Time

Collapse this tableExpand this table

Application protocol Protocol Ports
NTP UDP 123
SNTP UDP 123


World Wide Web Publishing Service


World Wide Web Publishing Service provides the infrastructure that you must have to register, manage, monitor, and serve websites and programs that are registered with IIS. This system service contains a process manager and a configuration manager. The process manager controls the processes where custom applications and websites reside. The configuration manager reads the stored system configuration for World Wide Web Publishing Service and makes sure that Http.sys is configured to route HTTP requests to the appropriate application pools or operating system processes. You can use the Internet Invormation Services (IIS) Manager snap-in to configure the ports that are used by this service. If the administrative website is enabled, a virtual website is created that uses HTTP traffic on TCP port 8098. 

System service
name: W3SVC

Collapse this tableExpand this table

Application protocol Protocol Ports
HTTP TCP 80
HTTPS TCP 443


Ports and protocols

The following table summarizes the information from the “System services ports” section. This table is sorted by port number instead of by service name. Click here to see the table

Collapse this tableExpand this table

Port Protocol Application protocol System service name
n/a GRE GRE (IP protocol 47) Routing
and Remote Access
n/a ESP IPsec ESP (IP protocol
50)
Routing and Remote Access
n/a AH IPsec AH (IP protocol
51)
Routing and Remote Access
7 TCP Echo Simple TCP/IP
Services
7 UDP Echo Simple TCP/IP
Services
9 TCP Discard Simple TCP/IP
Services
9 UDP Discard Simple TCP/IP
Services
13 TCP Daytime Simple TCP/IP
Services
13 UDP Daytime Simple TCP/IP
Services
17 TCP Quotd Simple TCP/IP
Services
17 UDP Quotd Simple TCP/IP
Services
19 TCP Chargen Simple TCP/IP
Services
19 UDP Chargen Simple TCP/IP
Services
20 TCP FTP default data FTP
Publishing Service
21 TCP FTP control FTP Publishing
Service
21 TCP FTP control Application Layer
Gateway Service
23 TCP Telnet Telnet
25 TCP SMTP Simple Mail Transfer
Protocol
25 TCP SMTP Exchange Server
42 TCP WINS Replication Windows
Internet Name Service
42 UDP WINS Replication Windows
Internet Name Service
53 TCP DNS DNS Server
53 UDP DNS DNS Server
53 TCP DNS Internet Connection Firewall/Internet Connection Sharing
53 UDP DNS Internet Connection Firewall/Internet Connection Sharing
67 UDP DHCP Server DHCP Server
67 UDP DHCP Server Internet Connection Firewall/Internet Connection Sharing
69 UDP TFTP Trivial FTP Daemon
Service
80 TCP HTTP Windows Media
Services
80 TCP HTTP World Wide Web Publishing Service
80 TCP HTTP SharePoint Portal
Server
88 TCP Kerberos Kerberos Key
Distribution Center
88 UDP Kerberos Kerberos Key
Distribution Center
102 TCP X.400 Microsoft Exchange MTA
Stacks
110 TCP POP3 Microsoft POP3
Service
110 TCP POP3 Exchange Server
119 TCP NNTP Network News Transfer
Protocol
123 UDP NTP Windows Time
123 UDP SNTP Windows Time
135 TCP RPC Message Queuing
135 TCP RPC Remote Procedure
Call
135 TCP RPC Exchange Server
135 TCP RPC Certificate Services
135 TCP RPC Cluster Service
135 TCP RPC Distributed File
System
135 TCP RPC Distributed Link
Tracking
135 TCP RPC Distributed Transaction
Coordinator
135 TCP RPC Distributed File
Replication Service
135 TCP RPC Fax Service
135 TCP RPC Microsoft Exchange
Server
135 TCP RPC File Replication
Service
135 TCP RPC Group Policy
135 TCP RPC Local Security
Authority
135 TCP RPC Remote Storage
Notification
135 TCP RPC Remote Storage
135 TCP RPC Systems Management Server
2.0
135 TCP RPC Terminal Services
Licensing
135 TCP RPC Terminal Services Session
Directory
137 UDP NetBIOS Name
Resolution
Computer Browser
137 UDP NetBIOS Name
Resolution
Server
137 UDP NetBIOS Name
Resolution
Windows Internet Name Service
137 UDP NetBIOS Name Resolution Net
Logon
137 UDP NetBIOS Name
Resolution
Systems Management Server 2.0
138 UDP NetBIOS Datagram
Service
Computer Browser
138 UDP NetBIOS Datagram
Service
Messenger
138 UDP NetBIOS Datagram
Service
Server
138 UDP NetBIOS Datagram Service Net
Logon
138 UDP NetBIOS Datagram
Service
Distributed File System
138 UDP NetBIOS Datagram
Service
Systems Management Server 2.0
138 UDP NetBIOS Datagram
Service
License Logging Service
139 TCP NetBIOS Session
Service
Computer Browser
139 TCP NetBIOS Session Service Fax
Service
139 TCP NetBIOS Session
Service
Performance Logs and Alerts
139 TCP NetBIOS Session Service Print
Spooler
139 TCP NetBIOS Session
Service
Server
139 TCP NetBIOS Session Service Net
Logon
139 TCP NetBIOS Session
Service
Remote Procedure Call Locator
139 TCP NetBIOS Session
Service
Distributed File System
139 TCP NetBIOS Session
Service
Systems Management Server 2.0
139 TCP NetBIOS Session
Service
License Logging Service
143 TCP IMAP Exchange Server
161 UDP SNMP SNMP Service
162 UDP SNMP Traps Outgoing SNMP Trap
Service
389 TCP LDAP Server Local Security
Authority
389 UDP DC Locator Local Security
Authority
389 TCP LDAP Server Distributed File
System
389 UDP DC Locator Distributed File
System
389 UDP DC Locator Netlogon
389 UDP DC Locator Kerberos Key Distribution Center
443 TCP HTTPS HTTP SSL
443 TCP HTTPS World Wide Web
Publishing Service
443 TCP HTTPS SharePoint Portal
Server
443 TCP RPC over HTTPS Exchange
Server 2003
445 TCP SMB Fax Service
445 TCP SMB Print Spooler
445 TCP SMB Server
445 TCP SMB Remote Procedure Call
Locator
445 TCP SMB Distributed File
System
445 TCP SMB License Logging
Service
445 TCP SMB Net Logon
464 UDP Kerberos Password V5 Kerberos Key Distribution Center
464 TCP Kerberos Password V5 Kerberos Key Distribution Center
500 UDP IPsec ISAKMP Local Security
Authority
515 TCP LPD TCP/IP Print Server
548 TCP File Server for
Macintosh
File Server for Macintosh
554 TCP RTSP Windows Media
Services
563 TCP NNTP over SSL Network News
Transfer Protocol
593 TCP RPC over HTTPS endpoint mapper Remote Procedure Call
593 TCP RPC over HTTPS Exchange
Server
636 TCP LDAP SSL Local Security
Authority
636 UDP LDAP SSL Local Security
Authority
993 TCP IMAP over SSL Exchange
Server
995 TCP POP3 over SSL Exchange
Server
1067 TCP Installation Bootstrap
Service
Installation Bootstrap protocol server
1068 TCP Installation Bootstrap
Service
Installation Bootstrap protocol client
1270 TCP MOM-Encrypted Microsoft
Operations Manager 2000
1433 TCP SQL over TCP Microsoft SQL
Server
1433 TCP SQL over TCP MSSQL$UDDI
1434 UDP SQL Probe Microsoft SQL
Server
1434 UDP SQL Probe MSSQL$UDDI
1645 UDP Legacy RADIUS Internet
Authentication Service
1646 UDP Legacy RADIUS Internet
Authentication Service
1701 UDP L2TP Routing and Remote
Access
1723 TCP PPTP Routing and Remote
Access
1755 TCP MMS Windows Media
Services
1755 UDP MMS Windows Media
Services
1801 TCP MSMQ Message Queuing
1801 UDP MSMQ Message Queuing
1812 UDP RADIUS
Authentication
Internet Authentication Service
1813 UDP RADIUS Accounting Internet
Authentication Service
1900 UDP SSDP SSDP Discovery
Service
2101 TCP MSMQ-DCs Message
Queuing
2103 TCP MSMQ-RPC Message
Queuing
2105 TCP MSMQ-RPC Message
Queuing
2107 TCP MSMQ-Mgmt Message
Queuing
2393 TCP OLAP Services 7.0 SQL Server: Downlevel OLAP Client Support
2394 TCP OLAP Services 7.0 SQL Server: Downlevel OLAP Client Support
2460 UDP MS Theater Windows Media
Services
2535 UDP MADCAP DHCP Server
2701 TCP SMS Remote Control
(control)
SMS Remote Control Agent
2701 UDP SMS Remote Control
(control)
SMS Remote Control Agent
2702 TCP SMS Remote Control
(data)
SMS Remote Control Agent
2702 UDP SMS Remote Control
(data)
SMS Remote Control Agent
2703 TCP SMS Remote Chat SMS Remote
Control Agent
2703 UPD SMS Remote Chat SMS Remote
Control Agent
2704 TCP SMS Remote File Transfer SMS
Remote Control Agent
2704 UDP SMS Remote File Transfer SMS
Remote Control Agent
2725 TCP SQL Analysis Services SQL Server Analysis Services
2869 TCP UPNP UPnP Device Host
2869 TCP SSDP event notification SSDP Discovery Service
3268 TCP Global Catalog Server Local
Security Authority
3269 TCP Global Catalog Server Local
Security Authority
3343 UDP Cluster Services Cluster
Service
3389 TCP Terminal Services NetMeeting
Remote Desktop Sharing
3389 TCP Terminal Services Terminal
Services
3527 UDP MSMQ-Ping Message
Queuing
4011 UDP BINL Remote
Installation
4500 UDP NAT-T Local Security
Authority
5000 TCP SSDP legacy event
notification
SSDP Discovery Service
5004 UDP RTP Windows Media
Services
5005 UDP RTCP Windows Media
Services
5722 TCP RPC Distributed File System Replication
6001 TCP Information Store Exchange
Server 2003
6002 TCP Directory Referral Exchange
Server 2003
6004 TCP DSProxy/NSPI Exchange Server
2003
42424 TCP ASP.Net Session
State
ASP.NET State Service
51515 TCP MOM-Clear Microsoft
Operations Manager 2000
1024-65535 TCP RPC Randomly allocated
high TCP ports

Collapse this imageExpand this image

Note Port 5722 is only used on a Windows Server 2008 domain controller or a Windows Server 2008R2 domain controller.

Microsoft provides part of the information that is in this table in a Microsoft Excel worksheet. This worksheet is available for download from the Microsoft Download Center.

Active Directory port and protocol requirements

Application servers, client computers and domain controllers that are located in common or external forests have service dependencies so that user-initiated and computer-initiated operations such as domain join, logon authentication, remote administration, and Active Directory replication work correctly. Such services and operations require network connectivity over specific port and networking protocols. 

A summarized list of services, ports and protocols required for member computers and domain controllers to inter-operate with one anotheror for application servers to access Active Directory include but are not limited to the following.

Click here to see a list of services on which Active Directory depends

  • Active Directory / LSA
  • Computer Browser
  • Distributed File System
  • File Replication Service
  • Kerberos Key Distribution Center
  • Net Logon
  • Remote Procedure Call (RPC)
  • Server
  • Simple Mail Transfer Protocol (SMTP) (if it is configured)
  • WINS (in Windows Server 2003 SP1 and later versions for backup Active Directory replication operations, if DNS is not working)
  • Windows Time
  • World Wide Web Publishing Service


Click here to see a list of services that require Active Directory services

  • Certificate Services (required for specific configurations)
  • DHCP Server (if it is configured)
  • Distributed File System
  • Distributed Link Tracking Server (optional but on by default on Windows 2000 computers)
  • Distributed Transaction Coordinator
  •  DNS Server (if it is configured)
  •   Fax Service (if it is configured)
  • File Replication Service
  • File Server for Macintosh (if it is configured)
  •  Internet Authentication Service (if it is configured)
  • License Logging (on by default)
  • Net Logon
  • Print Spooler
  • Remote Installation (if it is configured)
  • Remote Procedure Call (RPC) Locator
  • Remote Storage Notification
  • Remote Storage
  • Routing and Remote Access
  • Server
  • Simple Mail Transfer Protocol (SMTP) (if it is configured)
  • Terminal Services
  • Terminal Services Licensing
  • Terminal Services Session Directory

View post:
Service overview and network port requirements for Windows

You cannot receive email messages that include large attachments in a dedicated Office 365 environment

You cannot receive email messages that include large attachments in a dedicated Microsoft Office 365 environment. Additionally, one or more of the following occur:
  • You receive a non-delivery report (NDR) that states that the message is too large (NDR code 5.2.1 or 5.2.3).
  • The sender does not receive an NDR.

This issue occurs when one or more of the following conditions are true:
  • A message size limitation is set on the sender’s mailbox, or a limitation policy is set on the sender’s email server.
  • A message size limitation is set on the recipient’s email server.
  • The Forefront Security for Exchange (FSE) agent crashes.
To resolve this issue, you must reduce the message size and then resend the message. To reduce the message size, use one or more of the following methods:
  1. Use compression technology, such as WinZip. 
  2. Split the attachment into multiple files that can be sent separately.
  3. Use other technologies such as FTP or Internet File Sharing (such as SkyDrive) to share or to transport large files that do not require high security or data encryption.

If you do not receive an NDR, Microsoft Support Services may have to conduct additional message tracking to determine the issue. Collect the following information, and then contact Microsoft Support Services by using the Message Tracking/NDR escalation template:

  • Message subject
  • SMTP sender/recipient
  • Date/time sent

Article ID: 2519303 – Last Review: August 28, 2012 – Revision: 6.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Exchange Online Dedicated

Link:
You cannot receive email messages that include large attachments in a dedicated Office 365 environment

Page 322 of 741« First...102030...320321322323324...330340350...Last »

Recent Comments

    Archives

    Categories