Article Source: http://support.microsoft.com Installing Windows XP Service Pack 2 After Some programs seem to stop working for Summary After installing Microsoft Windows XP Service Pack 2 (SP2), some programs may not work. By default, the Windows firewall is enabled and blocked from an unsolicited connection to your computer. This article discusses how to add a program to an exception list so that the program can be used to run. This process allows the program to run as before installing service pack. Introduction To help protect the security based on Windows XP SP2-based computers, the Windows firewall blocks the unrulying connection of your computer. However, sometimes you may need to break and allow others to connect to your computer. For example, in the following, you may want others to connect to your computer: play multiple games through the Internet. It is desirable to receive files sent through instant messages. After installing Windows XP SP2, the client application may not be able to successfully receive data from the server. Here are some examples: FTP Client Multimedia Software Some new mail notifications in some email programs, or server applications running on Windows XP SP2-based computers may not respond to client requests. Here are some examples: Web Server, such as Internet Information Services (IIS) Remote Desktop File Sharing Back to top Windows Firewall Security Alert Sometimes, Windows Firewall Security Alert dialog box appears when Windows Firewall blocks a program. This dialog includes the following information: ... To help protect your computer, the Windows Firewall has prevented the program from receiving unsolicited information from the Internet or network This message display program name and the name of the program publisher. This dialog has three options: Cancel Blocking The program will continue to block the program from continuing to prevent the program, but later ask me to explain how to use this dialog as an enable program. Back to top The enabler must work normally, some programs and games must receive information over the network. This information enters your computer through an inbound port. To allow the Windows firewall to allow this information to enter, you must open the correct inbound port on your computer. To make a program communicate with Windows XP SP2 and enable programs you want to run, use one of the following methods. By using the Security Alert dialog box Enable program in the Security Alert dialog box, click Cancel to block the program. Click OK. The program will continue to stop the program if you do not click the "Cancellation of the Program" in the Security Alert dialog box. To enable a program using the Windows Firewall, follow these steps: Click Start, click Run, type WSCUI.cpl in the Open box, and then click OK. Click "Windows Firewall". In the Windows Firewall dialog box, click Exceptions tab, and then click Add Program. In the Add Program dialog, you can select a program from the displayed list or click the "Browse" to find the program. See the next section if you can't find your program. After selecting your program, click OK. On the Exceptions tab, make sure the check box next to the program is selected, and then click OK. Note: If you decide not to apply the program later, you can clear the check box. Adding a program to an exception list has the following advantages: You don't have to know a particular port number. (And when you need to open a port, you must know the port number used by the program. This will be described later.) The port used in the exception list is only opened when the program waits for receiving connections.
Back to top Determine and open port If you add a program to an exception list, the program does not work, or you can't find the program in step 4 of the previous section, you can manually open a port. Before you manually add a port, you must first determine the port used by the program. Determine the reliable method of the port used to use is to contact the supplier. If you are unable to contact the vendor or not find a list of ports used, you can use NetStat.exe to determine the port used by the program. Use NetStat.exe to determine port To determine ports used by NetState.exe, follow these steps: Start the program and try to use its network function. For multimedia programs, try to start the audio stream. For web servers, start the service. Click Start, click "Run", type CMD in the Open box, and then click OK. Get a list of all listening ports. To do this, type the following on the command prompt, then press Enter: NetStat -ano> NetStat.txt get the process identifier of the running process. Type the following command at the command prompt, then press ENTER: Tasklist> Tasklist.txt Note: If the program is running as a service, add / SVC switch to list the services loaded in each process: Tasklist / SVC> Tasklist .txt Open Tasklist.txt and find the program to find out the problem. Write down the process identifier of the process. Open NetStat.txt and record any entries associated with the process identifier. Also note the protocol (TCP or UDP) used. The number of ports used in the process may affect the way to resolve this issue: if the port is more than 1024, the number of ports may not change. If the port is less than 1024 ports, the program may use the port within a range. Therefore, open individual ports may not be able to reliably resolve this issue. Back to top A port port is manually opened to manually open port If you cannot determine the port used by the program, you can open a port manually. To determine the specific port number you need to open, contact your product vendor or view the user documentation of the product. After confirming the port number you want to open, follow these steps: Click Start, click Run, type WSCUI.cpl in the Open box, and then click OK. Click "Windows Firewall". On the Exceptions tab, click Add Port. In the Add Port dialog box, type the port number you want to open in the Port number box, and then click TCP or "UDP". Type a name for this port, and then click OK. For example, type Gameport. To view or set the range of port exceptions, click Change Scope, and then click OK. On the Exceptions tab, you will notice that new services are listed. To enable this port, click the check box next to the selection, and then click OK. For additional information about configuring Windows Firewall, click the article number below to view the article in the Microsoft Knowledge Base: 875357 Resolve Windows XP Service Pack 2 WINDOWS Firewall Settings Problem Back to top You may need you to manually open the port The procedures and games that may require you to manually open the port can be required.
Program Program Supplier Port Default Exception Visual Studio .NET Microsoft See related documents See related documents only for remote DCOM debugging SQL Microsoft For RPC and DCOM dynamic allocation ports only for remote debugging Backup EXEC 9 VERITAS 1000 C: / Program files / veritas / backup Exec / Rant32 / Beremote.exe is only used from server backup client Ghost Server Corporate Edition 7.5 Symantec 139-TCP-NetBIOS session service; 445-TCP-SMB over TCP; 137-UDP-NetBIOS Name Service 138-UDP-NetBIOS Data News Services See related documents For the lower phantom client Symantec AntiVirus Corporate Edition 8.0 Symantec file and printer sharing selection "Allow File and Printer Sharing" checkbox to open the following ports: UDP 137, 138 TCP 139, 445. For installation client SMS 2003 Server Microsoft Enable file and printer shared port See related documents For View Windows XP SP2 Client Event Viewer Cute FTP 5.0 XP GlobalScape 21 or FTP server See related documents for FTP to WINDOWS XP SP2 Computer Exceed 7.0, 8.0 Hummingbird 21 or FTP server See related documents to connect FTPs with Windows Explorer to Remote Computers KEA! 340 5.1 Attachmate 23 or "Telnet Server" See related documents for establishing Remote Host Telnet session WRQ REFLECTION X 10 and 11 WRQ 23 or "Telnet Server" See related documents for the Telnet session of the remote host REELNET session Reflection for IBM 9, 9.03, 10 and REFLECTION X 10, 11 WRQ 21 or FTP server See related documents to connect FTP clients to remote computers Smarterm Office 10 and Smarterm 11 Esker Software 23 or "Telnet Server" For the Documentation Telnet Session SMarterm Office 10 and Smarterm 11 Esker Software 21 Or FTP Server See related documents to connect the FTP tool to the remote computer ViewNow 1.05 NetManage FTP server or 21 See related documents to connect FTP tools to remote computers ViewNow 1.0 and 1.05 NetManage 6000 (TCP / IP) and 177 UDP) See related documents for establishing X-Windows sessions ViewNow 1 or 1.05 NetManage Telnet server or 23 See related documents for Telnet sessions for building to remote hosts Microsoft Operations Manager 2000 SP1 Microsoft Enables ICMP Election Request, Files, and Printers Sharing and UDP See related documents to push the MOM agent to enable Windows firewall and based on Windows XP SP2 client AutoCAD 2000, 2002, 2004 Autodesk 21 See related documents If the remote FTP host has enabled Windows Firewall, use the FTP viewer to browse the project ("File" -> "Opens" dialog) This port is required.
BACKUP EXEC 9.1.4691 VERITAS See related document% Program Files% / VERITAS / Backup EXEC / RANT / BEREMOTE.EXE Used to back up Windows XP SP2 Client Windows Scanner and Camera Wizard Xerox Network Scanners 21 See related documents Use this port to start the scanner and camera wizard, and make the scanned image to be accessible. Symantec Corporate AntiVirus 9.0 Symantec See related documents See related documents When you push the antivirus definition to the client, the client needs to use this port to accept updates and can scan the client.
ColdFusion MX Server Edition 6 Macromedia TCP (By default 8500) See the related documentation allows you to use this port CA ARCserve Computer Associates 137-UDP-NetBIOS Name Service when performing remote access as a web server; 138-UDP-NetBIOS Datashers 139-TCP-NetBIOS session service; 704-UDP; 1478-UDP-MS-SNA-BASE; 1900-UDP-SSDP; 6050-TCP-ARCserve service; 6051-TCP-ARCserve service See related documents for remote installation , Authorization and Client Communication EDM File System Agent 4.0 EMC 3895 See related documents to install the EDM client from the server to Windows XP SP2MICROSoft Systems Management Server 2003 Microsoft TCP: 2701% WINDIR% / System32 / CCM / CLICOMP / Remctrl / Wuser32.exe Remote Tools Remote Controlling Windows XP SP2-based client Aelita Erdisk for Active Directory 6.7 Quest SoftWare See related document files and printer sharing for communication with remote computers Hummingbird Host Explorer 8 Hummingbird 23 TCP and 21 TCP See related documents For Telnet to Windows XP SP2 client BV-Admin Mobile Bind View, see related document files and printer sharing for communications with remote computers SQL 2000A Microsoft 1433 and 1434 See related documents for Connect to Remote Computer Backup Exec 8.6.1 Server Use this port to push remote proxy to Windows XP SP2-based client Microsoft SNA 4.0 SP3 Microsoft See related document files and printer sharing for viewing Windows XP SP2-based client EXTRA ! Personal Client 6.5 and 6.7 Attachmate TE LNET Server or Port 23 See related documents for Telnet sessions for the remote host to build a Telnet session Extra! Enterprise 2000 Attachmate Telnet server or port 23 For the Telnet session Extra! Bundle for TCP / IP 6.6 Attachmate for the Remote Host Telnet Server or Port 23 See the related document Telnet session for the remote host Volume Manager 3.1 Veritas / Veritas Object Bus / Bin / Vxsvc.exe for connecting to Windows XP SP2-based customers End BMC Pather for Windows 2000 BMC Software On Windows XP SP2 (client) computer: TCP ports 3181, 10128, and 25; UDP ports 3181, 10128, and 25 //
