- #UNIVERSAL MEDIA SERVER FIREWALL INSTALL#
- #UNIVERSAL MEDIA SERVER FIREWALL MANUAL#
- #UNIVERSAL MEDIA SERVER FIREWALL PATCH#
You should see a grayed out entry that has your Windows Firewall port exceptions you entered in step 4. Click Start, Settings, Control Panel, Network Connections, Change Windows firewall settings. Verify the workstation firewall settings. Run GPUpdate to refresh the Group Policy and GPResult to view the results of the new Group Policy. Because I want all users on the network to get this GPO, I linked the GPO at the domain level and assigned it to the Authenticated Users group. After you enter the correct string, click Next and make sure to allow port exceptions on Windows firewall. For example, if you want to allow any computer on the 192.168.1.0 subnet, the entry would be 2967:UDP:1921.68.1.0/24:enabled:SAVMgmtPort. You can specify entire subnets by using a slash (/) and the number of bits in the subnet mask. You can specify multiple IP addresses in the scope field by separating your entries with a comma. Assuming that your SAV server has an IP address of 192.168.1.1, the entry string for the port exception should be: 2967:UDP:192.168.1.1:enabled:SAVMgmtPort. Double-click Windows Firewall: Define port exceptions, click Show, click Add, and enter the exception string. I suggest only allowing the IP address of your SAV servers in the port exception rule. For additional port information used in SAV Corporate, refer to. If you just want to allow remote management through the Symantec AntiVirus (SAV) Corporate Edition 9.x and 8.x console, open UDP port 2967. You must define the settings for Windows Firewall: Define port exceptions and Windows Firewall: Allow local port exceptions. This setting is located in Computer Configuration, Administrative Templates, Network, Network Connections, Windows Firewall, Domain Profile. Create a GPO to open ports on Windows Firewall.
#UNIVERSAL MEDIA SERVER FIREWALL PATCH#
If you don't download this patch you'll receive the error message “The following entry in the \ section is too long and will be truncated” whenever you try to edit a Group Policy Object (GPO). Download the patch to handle strings longer than 255 characters. adm files, make sure you merge the existing modifications with the updated templates. adm files in c:\windows\inf, then copied the updated template files to c:\windows\inf. You can get the latest ADM templates from. GPMC must be installed on a Windows 2003 or XP workstation.
#UNIVERSAL MEDIA SERVER FIREWALL INSTALL#
Go to to download and install the utility. Install Group Policy Management Console (GPMC). Complete the following steps to let the XP SP2 workstation be managed with the Symantec System Center Console.ġ. You can also use Group Policy to control the Windows Firewall settings. You can use the Windows Firewall INF file to control the firewall's behavior. Because the Windows Firewall is turned on by default with SP2, it prevents the Symantec System Center from communicating with the workstation.
#UNIVERSAL MEDIA SERVER FIREWALL MANUAL#
For example, if you try to start a manual scan on an XP SP2 machine, you'll receive an error message stating that the workstation can't be communicated with even though it's turned on and connected to the network. If you've installed Windows XP Service Pack 2 (SP2) on a machine, you might have noticed that you can't remotely manage the workstation using the Symantec System Center Console. Windows Firewall Proves Problematic for Symantec AntiVirus