nxfilter port conflict windows 2012 server

This is the default configuration for both products. Both products assume exclusive access of the SSL port (443) and HTTP port (80). Windows Server Essentials is managed via its dashboard and the IIS Management UX.

Work Folders is available in Windows Server 2012 R2 Essentials as part of the File and Storage Services role. Work Folders uses the IIS Hostable Web Core feature and all management is performed via the Work Folders canvas in Server Manager as well as via Windows PowerShell cmdlets. This creates a port conflict for one of the features, depending on startup and how the features where configured. The first feature to initialize the ports will exclusively own them. In the specific case of Windows Server Essentials and Work Folders, both features use the same default ports. Most web applications use the same well known ports. Work Folders uses by default ports HTTPS=443 and HTTP=80. Using any web application with Work Folders may create port conflicts between the web application and Work Folders. Guidance for Using Hyper-V for Current Enabling of Work Folders and Windows Server Essentials using their default configurationĭIAGNOSING WORK FOLDERS AND WINDOWS ESSENTIALS PORT CONFLICTS In-Place Upgrade from Windows Server Essentials to Windows Server Standard For this reason I posted this blog for guidance.ĭiagnosing Port Conflict between Work Folders and Windows Server Essentials or other web applications.Ĭhanging Port Configuration in Work Folders

I have been following the forum and there have been several questions about Work Folders and port conflicts with other IIS Websites. We have just delivered Work Folders as part of the Windows Server 2012 R2 release. One of my main responsibilities is to enhance the Server Manager user interface. Hi All, my name is Bill and I work in the Windows Server - File Services group.

First published on TECHNET on Oct 15, 2013

Nxfilter port conflict windows 2012 server