ServicePack 2 disabled this feature. You can enable it again by creating the following registry entry on the XP client: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server "AllowRemoteRPC" = REG_DWORD:1 Also make sure that the Windows firewall on the client is configured to allow File and Print sharing, as well as Remote Desktop.

No, Microsoft desktop operating systems (including Windows XP and Windows 2000 Professional) do not have a built-in Terminal Services CAL. For Windows 2000 Terminal Servers, the license server issues machines running Windows 2000/Windows XP Professional a "free" Terminal Services CAL from its built-in pool (and its use is permitted under the Windows 2000 Server EULA).

Windows XP SP2 is supported with the current shipping versions of eCopy ShareScan 8.3 Build XX and eCopy Desktop 8.5 Build 0.116. We do not have any plans to certify Windows XP SP2 with earlier versions.

You can't do this with the Remote Desktop Protocol client. Windows 2000 Pro, Vista Home Basic and Vista Home Premium workstations can only be rdp clients, not hosts.

If you noticed a decrease in your FireWire performance after installing Windows XP Service Pack 2, try downloading this patch from Microsoft.

There are a few ways that you are going to get hold of XP SP2 and not all of these will be available at the same time.

Microsoft has patched various flaws in SP2, but you can still be able to disable unwanted services or change behaviours of included software and other features.

I just upgraded to the latest version of PowerTCP XXX for .NET, now my Delphi 8 app does not compile. I get an error about a manifest declaration.

Windows XP SP2 limits the number of TCP connection attempts to 10 (quite small ). If there are more concurrent TCP connection attempts, Windows generates a warning: EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. You can go to Xp's Admin tool, event viewer, look in system tab and notice tcpip entry (with yellow warning sign).

Yes, the CrypKey-protected application can run via terminal services or remote desktop. To run a CrypKey-protected application via remote desktop or terminal services you must issue a network license with x number of seats to the machine that has the application installed. Issue the machine the application is running on, a network license for as many seats as you would like to allow concurrent use. As of version 6.

Yes. You can access your single-user (SU) desktop copy of S-PLUS from a remote location using Terminal Services or Windows Remote Desktop. (Note: as implied by the "single-user" license name, having another person use your desktop copy at the same time as you access it remotely is not allowed.) If you have a Concurrent-Session (SESS) or Production-Session (PSESS) license, accessing S-PLUS via Terminal Services will decrement the license count by one.

Terminal Server/Services and Remote Desktop Connection are supported. Some Oracle components will be exceptions to this support. Please check the Oracle Database release notes for your specific version for more details. Oracle certifies against the specific Microsoft operating system and, if applicable, service packs (SPs) stated in the Oracle product documentation. Oracle will support the use of our products on any later SP as soon as that SP becomes generally available.

To connect from a Windows OS client to a Macintosh client, use VNC. The Apple Remote Desktop client has a built-in VNC client. Check in the Sharing Preferences pane in System Preferences.

Yes, preEmpt is completely compatible with Windows XP SP2 and provides significant security benefits beyond the changes included in SP2. First and foremost, Windows XP SP2 is a one-time event, coming almost a full year after the last significant service pack, SP1. Windows XP SP2 contains a number of important security fixes, including some that were originally identified and published by PivX Labs security researchers complete with mitigation steps to block exploits of those vulnerabilities.

No. If your Symantec product runs on Windows® XP now, it does not require SP2 to continue working. Symantec Client Security may not appear correctly in the Windows Security Console, but the product will work as designed.

Windows® XP SP2 contains some important enhancements. Today's enterprise environments will gain maximum protection from an integrated, multilayered approach to security. Windows® XP SP2 users can protect themselves fully by adding Symantec Client Security to their desktop or laptop security strategy.

Microsoft is including NAP support in Windows XP Service Pack 3. For more information about the availability of Windows XP Service Pack 3, see Windows Service Pack Road Map. For additional information about NAP support for versions of Windows prior to Windows Vista and Windows Server 2008, click here.

To move a Terminal Services CAL, see Knowledge Base article How to Transfer Terminal Services CAL from One Computer to Another (Q248430). For information about how Terminal Services CALs can be automatically reissued, please see the Knowledge Base article describing the two licensing enhancements made for Windows 2000. These licensing enhancements are also in Windows Server 2003.

If your dedicated server are running on Windows 2000 or Windows 2003, you will be provided with Terminal Client access to administer your server.

Halo PC and CE can experience problems with certain 256mb cards and Windos XP SP2. There is a fix available, please see here .

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix.

Yes. The Windows XP SP2 will automatically open the Internet connection firewall of Windows XP. So outside requests will be blocked by the firewall. Now you need to config the Internet connection firewall of Windows XP to allow WWW File Share Pro to respond outside requests. To learn how to config the Internet connection firewall of Windows XP, please click here.

Yes, please reference EFI Balance User Guide Windows XP Connection Appendix for more information. Since the Service Pack includes security and firewall protection, you will need to make system modifications for EFI Balance and its utilities to operate correctly.

If you have recently installed Windows XP SP2 and your eBooks will no longer work click here for the fix.

Yes, though as with any multiplayer game, you will need to configure the firewall to allow the application to access internet services. This can be done by adding the application to the list of exceptions for the firewall, and opening the required ports 2934 and 2935 (UDP). This Knowledge Base article explains how to configure the firewall in general for multiplayer games: http://support.microsoft.com/

Please consult your software firewall vendor's documentation about how to open up ports 2934 and 2935 (UDP).

BitComet 0.55 or above can work correctly under Windows XP SP2 without patch. However, limiting the connection attempt by the system may result in a slower speed at the beginning of downloading, since fewer peers can be connected at the same time. For those behind a NAT or firewall, the thrid-party [ http://www.lvllord.de/ patch] for tcpip.sys to fix that SP2 issue is still recommended.

Yes, RemoteExec can remotely execute tasks on Windows XP SP 2 workstations. You just need to follow the instructions listed in the document XP SP2 firewall settings for RemoteExec in order to deploy the firewall settings allowing RemoteExec to remotely execute tasks on these computers.

The problem is related to the limits SP2 for Windows XP puts to the number of TCP connections a P2P program can make.

No. It is not possible to run Terminal Services in Application Server mode on Windows Small Business Server 2003. This is a change from Small Business Server 2000. Running Terminal Services in Application Server mode on a domain controller may present a security risk to your network.