Windows XP & Service Pack 2

ALL versions of our software are compatible with XP-SP2 or any other firewall (hardware or software), however, you will have to properly configure the firewall to allow the necessary traffic to pass through.

Using DameWare Development products in conjunction with XP SP2

http://www.dameware.com/support/kb/article.aspx?ID=300068

When a remote machine is running XP SP2 (or even SP1 with the ICF Firewall enabled or ANY type of firewall software), then by default this is more than likely blocking the necessary ports required by our software. In order to resolve this issue, you don't have to disable the firewall, however, you will need to modify the default firewall settings.

Basically, all you should have to do is Open which ever TCP port that you choose for the Client Agent Service to listen on, and then adjust the Scope in the SP2 firewall to match your network topology (i.e. all Computers, Local Subnet only, or define a custom Scope). Provided the MRC Client Agent is already installed & running on the remote machine, then only a single TCP port is used. The default port used by the MRC application and Client Agent to make a connection is TCP 6129, but you can configure both the MRC Application and the Agent to use any one of the 65,000 valid TCP ports. You just need to make sure it matches at both ends in order to make a connection. In other words, if you attempt a connection on TCP 6129, but the Client Agent on the remote machine is listening on 4129, then it's not going to work, and you may receive a Winsock 10060 error.

All the Views in the NT Utilities program (i.e. Users View, Event Log View, etc), as well as the Mini Remote Control program's ability to remotely install, start, stop, or remove the Mini Remote Client Agent Service uses the Operating System's installed protocols, basically File & Printer Sharing (i.e. 137-139/445). You would also have to make sure you adjusted the Scope for each of these ports properly in the SP2 firewall as well.

Also, just FYI, Microsoft defines File & Printer Sharing as:

UDP 137

UDP 138

TCP 139

TCP 445

Please also make sure to configure the Scope properly for each port you define in the SP2 firewall (i.e. ALL, Same Subnet, or Custom Subnet). This is extremely important, and if you do not configure it properly, then you will not be able to connect.

Please also make note if you were attempting to use the software over the Internet that many ISPs (Internet Service Providers) also block these ports over their network. Unfortunately, there are no provisions for modifying these ports because these ports are required by the Operating System itself.

Also, according to Microsoft configuring the SP2 firewall can be accomplished in many different ways, including pushing out an INF file, via Group Policies, or even via the Command Line. You may also be able to connect to the remote machine using the Mini Remote Control program's RDP (Remote Desktop) functionality, and then make the necessary changes to the Windows Firewall settings, to allow the MRC program to connect. By default when you install SP2, I believe the Remote Desktop ports are already open in the Windows Firewall settings.