Previous Topic: DSM Explorer Can Change the Password Values in OS image DefaultsNext Topic: OS Installation Cannot Detect NFS Server


DSM Agent and Firewall in Windows XP SP2

Symptom:

Some Agent features are blocked by the WindowsXP-SP2 firewall.

Solution:

The default WindowsXP-SP2 installation enables the firewall in WindowsXP-SP2.

Some features like sending a job check request from the GUI, or the Manager itself sending a trigger to start the agent or a remote reboot request from an OS installation order may not work.

It is possible to open the firewall for all Agent features by calling:

“netsh firewall add portopening protocol=UDP port=4104 name=CAM-4104UDP mode=ENABLE scope=ALL profile=ALL”

Note: When you configure the Windows firewall in an organization network using Group Policy of the Active Directory Service, the Group Policy can overwrite the local Windows firewall configuration.

The same call can be added to the OS image of WindowsXP-SP2 when using the OSIM. Please add the call to the file i386\$oem$\c\oeminst\custom.cmd of your WindowsXP-SP2 image.

Open the file in an editor and add the following after the label :agentready:

netsh firewall add portopening protocol=UDP port=4104 name=CAM-4104UDP mode=ENABLE scope=ALL profile=ALL