How To Open A Port In Windows Server 2012

Offset published on TECHNET on October 15, 2013

Hi All, my proper name is Bill and I piece of work in the Windows Server - File Services group.  One of my chief responsibilities is to enhance the Server Director user interface.  Nosotros have only delivered Work Folders as role of the Windows Server 2012 R2 release.  I have been following the forum and there have been several questions almost Work Folders and port conflicts with other IIS Websites.  For this reason I posted this web log for guidance.

Covered in this Article:

• Diagnosing Port Conflict betwixt Work Folders and Windows Server Essentials or other web applications.


• Changing Port Configuration in Piece of work Folders


• In-Identify Upgrade from Windows Server Essentials to Windows Server Standard


• Guidance for Using Hyper-V for Current Enabling of Work Folders and Windows Server Essentials using their default configuration

Sections:

1. PROBLEM Statement


2. OVERVIEW


3. DIAGNOSING Work FOLDERS AND WINDOWS ESSENTIALS PORT CONFLICTS


4. Changing WORK FOLDERS CONFIGURATION


5. NO CONFIGURATION FOR BOTH FEATURES


6. SUMMARY

Using any web application with Piece of work Folders may create port conflicts between the web awarding and Work Folders.  Work Folders uses by default ports HTTPS=443 and HTTP=80.  Most spider web applications utilize the same well known ports.  In the specific case of Windows Server Essentials and Piece of work Folders, both features use the same default ports.  The showtime feature to initialize the ports volition exclusively own them.  This creates a port conflict for one of the features, depending on startup and how the features where configured.

Piece of 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 direction is performed via the Work Folders canvas in Server Manager as well as via Windows PowerShell cmdlets.  Windows Server Essentials is managed via its dashboard and the IIS Management UX.  Both products assume exclusive admission of the SSL port (443) and HTTP port (80).  This is the default configuration for both products.

The administrator has the ability to change both feature configurations when both products are enabled. Irresolute the port conflicts allows for both products to exist installed on Windows Server 2012 R2 Essentials.  If the ambassador does not want to change the default ports, they accept the selection of enabling either Windows Server Essentials feature or Piece of work Folders.  This is at their discretion based on business demand.

If the administrator would like to change the ports on either characteristic, they need to open up the firewall on the server for the specific ports they defined for the feature.  This can exist accomplished by navigating to Control Console and modifying the Windows Firewall configuration.  Further work is necessary in collaboration with a network ambassador to configure the routers as well.  This document will non encompass network configuration.

See: http://msdn.microsoft.com/en-us/library/bb909657(five=vs.90).aspx

In the event where both features are enabled on the aforementioned server with default port configuration the behavior may be subtle and but one characteristic will work.  In the example of Windows Server 2012 R2 Essentials, Windows Server Essentials is enabled out of the box.  This means the ports will have been configured and ownership volition be IIS.  When yous enable Work Folders, the installation will succeed and Server Manager may not be able to manage the Work Folders feature on the Windows Server Essentials server.  If the administrator navigates to the SERVICES main tile they volition meet the following:

The Sync Share Service volition not start if both ports defined in its configuration are being used past another process.  This will be a articulate indication the default ports are not available to Piece of work Folders.  If on the off adventure one of the ports is bachelor the Sync Share Service will go operational.   In that location will be no indication there is an fault.

Please notation if port 443 is used by another process, although Piece of work Folders Service will get-go and be operational, any SSL traffic will non exist directed to Work Folders.  SSL=443 is the default secure port used past Work Folders.  The administrator would have to wait at the port definition in the file c:\windows\system32\SyncShareSvc.config and compare the configuration of websites defined in the IIS UX.  One time they check the port information in IIS they can appraise the conflict.

In the instance both ports are non available the following mistake can exist plant in the system event log.

Using Event Viewer (eventvwr.msc) navigate to the Windows Logs, Organization Channel.  The fault should be from the Service Control Manager.  The error returned volition be in the system aqueduct in the course:   "The Sync Share Service terminated with the following service-specific error:  Cannot create a file when a file already exists" This is the generic message when both ports are non available.

Get-WebBinding is a handy command for showing IIS website port bindings on your server.  In this item example nosotros want to come across all the IIS website bindings active on your server.

> get-WebBinding ß command on left will requite you the following output:

Example 1 - both ports in use past IIS website:

The Piece of work Folders SyncShareSvc will not outset because both default ports are being used by IIS.

Example 2 – i port used by IIS website – SSL PORT:

Every bit mentioned in the previous section, if Work Folders has access to i port the service SyncShareSvc will come.  Work Folders uses port 443 as the default.  In example 2 Work Folders service would first and look  operational.  The output of Become-WebBinding would show the ambassador Work Folders would not function every bit defined in the default configuration.

If neither port is in use past another web application, the list above would exist empty.

On the Server Manager Service Chief Tile locate the SERVICES tile.  Locate the SyncShareSvc.  Verify it is stopped.  If information technology is non stopped, select the SyncShareSvc and stop information technology.

Navigate to the directory on the server where work folders feature is enabled.

>cd c:\windows\system32

Edit the file with your favorite editor (file proper name = SyncShareSvc.config)

Locate the section below and brand the changes to your port designation

For this
instance you desire to change SSL Port from 443 to 12345.  Change the port number and close the file.   Because the sync service does not run under the system designation information technology does not accept the privileges to access unlike ports other than the default. Information technology runs under LOCAL SERVICE.  Because of this designation the administrator has to run some other command.   In an elevated command window blazon the following command:

Netsh http add urlacl url=https://*:12345/ user="NT Dominance\LOCAL SERVICE"

Navigate to SERVICES tile in Server Managing director and start the service SyncShareSvc.

Since the Piece of work Folders configuration on the client defaults to either HTTPS=443 or HTTP=lxxx there is boosted configuration to override the default ports.  The administrator volition need to change the URL for connecting to the Windows Server hosting the clients sync share.  Normally all that would be necessary is the URL of the server.  Since the port has changed there is an additional parameter in the URL which is – colon port number ":#".  This  number matches the configuration in the configuration file on the server SyncShareSvc.config.   See example of the PC client configuration below:

NOTE: When the administrator changes the default ports for Work Folders they cannot use the auto discovery procedure.  They tin communicate the new URL using Group Policy or a standard email communication with the URL and new port definition.

IIS References for Configuration Changes

For Windows Server Essentials port configuration see the Windows Server Essentials documentation using the IIS management UX.

http://world wide web.iis.net/configreference/arrangement.applicationhost/sites/site/bindings/binding

The administrator has some other selection for running both Windows Server Essentials and Piece of work Folders on the same server.  In that location are posts on-line which already recommend an in-identify license upgrade from Windows Server Essentials to Windows Server Standard.  This has a twofold improvement.  It allows for greater usage of Windows Server Essentials and has a license for two Hyper-V machines.  The administrator would then disable Windows Server Essentials in the main host and user the two Hyper-Five machines one for each characteristic.  Windows Server Essentials in ane VM and Work Folders in the other. They can both utilize their default configurations and piece of work meantime on the single host.

You lot can upgrade in place from Windows Server 2012 R2 Essentials to Windows Server Standard.  --- Windows Server Standard is the only in-place upgrade.  You cannot use the command below to upgrade to Windows Server Storage, Windows Server Datacenter etc. The command for upgrading from Windows Server 2012 R2 Essentials to Windows Server 2012 R2 Standard is:

dism /online /set up-edition:ServerStandard /accepteula /productkey:<Product Key>

From < windows2012 essentials upgrade to windows 2012 server standarddataenterprise >

In that location are several ways to configure Work Folders in an environment which already has established web applications. You take the ability to change the ports of either application.  In the instance of an IIS application y'all can use the existing IIS UX.  In the instance of WorkFolders you tin can follow this guide. The ambassador also has the ability to run Piece of work Folders in a separate VM which has the benefit of leaving their current configuration equally is and installed Piece of work Folders with default settings.

Source: https://techcommunity.microsoft.com/t5/storage-at-microsoft/windows-server-2012-r2-8211-resolving-port-conflict-with-iis/ba-p/424985

Posted by: rollinsonews1937.blogspot.com

Share this post