Bug 528 – Would be nice to detect and possibly add exceptions for SlimServer in new XPSP2 firewall

Bug 528 - Would be nice to detect and possibly add exceptions for SlimServer in new XPSP2 firewall

Summary:

Would be nice to detect and possibly add exceptions for SlimServer in new XPS...

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Windows Installer
Version:	5.x or older
Platform:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Vidur Apparao

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2004-09-01 13:49 UTC by Kevin Pearsall
Modified:	2008-12-18 11:53 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
registry keys to allow slimserver ports in windows firewall (666 bytes, text/plain) 2004-09-01 13:51 UTC, Kevin Pearsall	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Kevin Pearsall 2004-09-01 13:49:36 UTC

We can check if the firewall is on or off here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile
-- "EnableFirewall" (REG_DWORD)...  0 = firewall off, 1 = firewall on...  either
one is valid here, but if it's set to 1 we should add our ports?
-- "DoNotAllowExceptions" (REG_DWORD)... 0 = allow exceptions, 1 = do not allow
exceptions...  we'd require this to be 0.
-- "DisableNotifications" (REG_DWORD)... 0 = tell the user about events, 1 =
don't tell the user...  obviously we shouldn't touch this.

We can add ports here:
HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\GloballyOpenPorts\List
They're added as REG_SZ strings and the format appears to be:
"<PORT#>:<PROTOCOL>:<REMOTEZONE>:<Enabled/Disabled>:<COMMENT>"
-- Port # = obvious
-- Protocol = tcp or udp, not sure if other settings are valid
-- Remote zone can be "LocalSubNet", * for all IPs...  Not sure if it lets you
specify custom subnets or not, can't find proper syntax for this on the intarweb.
-- Enabled/Disabled is obvious...
-- Comment is obvious...

They seem to take affect IMMEDIATELY after they are imported.  I'll attach a
.reg file that has the right ports and has them enabled...  Just 3483/tcp
3483/udp and 9000/tcp though.  I don't think most people would be using 9090
much so that shouldn't be a big deal...

Comment 1 Kevin Pearsall 2004-09-01 13:51:01 UTC

Created attachment 118 [details]
registry keys to allow slimserver ports in windows firewall

This can be imported silently with regedit.  This is done by:
regedit -s <filename.reg>

Comment 2 Jacob Potter 2004-09-11 07:01:27 UTC

Vidur checked in a fix for this on September 3rd...

Comment 3 Chris Owens 2006-06-16 14:40:31 UTC

There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.

Comment 4 Chris Owens 2008-12-18 11:53:37 UTC

Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.