With Windows 7 and Server 2008, Microsoft introduced firewall policies that can complicate bench testing and lock out services where a limited network configuration is used.  A common way to handle this scenario in XP and Server 2003 was to simply stop the firewall service.  This no longer has the same effect in current operating systems.

By default, if no DNS server or Default Gateway is available for the network interface, the server will be locked into a Public profile.  This profile, designed to protect the OS, stops essential traffic from many services that may be installed on the system. In order to release a network adapter from the Public profile, access the Local Security Policy console through Control Panel -> Administrative Tools -> Local Security Policy.

Find the Network List Manager Policies on the left pane then the Unidentified Networks in the right pane.  Double click the item to open the setting.

Here, change Location Type to “Private” and the User Permissions to “User can change location.” Click OK to apply the change and close the console.

This change takes two actions.  First, it changes the default profile to Private, which is more accepting of standard firewall rules and services.  Second, it enables the user to change the active profile regardless of the presence of DNS or a Default Gateway. Checking the active profile now shows Private with a link to change the profile if needed.

Learn more about this topic at scansourcecatalyst.com >

Leave a Comment

Previous post:

Next post: