Adaptec 1130U2 - Storage Controller RAID)- U2W SCSI 80 MBps Specifications download pdf (Page 27)

Conflict Between vCenter Server and IIS for Port 80

vCenter Server and Microsoft Internet Information Service (IIS) both use port 80 as the default port for direct

HTTP connections. This conflict can cause vCenter Server to fail to restart after the installation of vSphere

Authentication Proxy.

Problem

vCenter Server fails to restart after the installation of vSphere Authentication Proxy is complete.

Cause

If you do not have IIS installed when you install vSphere Authentication Proxy, the installer prompts you to

install IIS. Because IIS uses port 80, which is the default port for vCenter Server direct HTTP connections,

vCenter Server fails to restart after the installation of vSphere Authentication Proxy is complete. See

“Required Ports for vCenter Server,” on page 23.

Solution

To resolve a conflict between IIS and vCenter Server for port 80, take one of the following actions.

Option Description

If you installed IIS before installing

vCenter Server

Change the port for vCenter Server direct HTTP connections from 80 to

another value.

If you installed vCenter Server

before installing IIS

Before restarting vCenter Server, change the binding port of the IIS default

Web site from 80 to another value.

DNS Requirements for vSphere

You install vCenter Server, like any other network server, on a machine with a fixed IP address and well-

known DNS name, so that clients can reliably access the service.

Assign a static IP address and host name to the Windows server that will host the vCenter Server system.

This IP address must have a valid (internal) domain name system (DNS) registration.

Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all

vSphere Web Clients. Ensure that the vCenter Server has a valid DNS resolution from all ESXi hosts and all

vSphere Web Clients.

Ensure that the vCenter Server is installed on a machine that has a resolvable fully qualified domain name

(FQDN). To check that the FQDN is resolvable, type nslookup your_vCenter_Server_fqdn at a command line

prompt. If the FQDN is resolvable, the nslookup command returns the IP and name of the domain controller

machine.

Ensure that DNS reverse lookup returns a fully qualified domain name when queried with the IP address of

the vCenter Server. When you install vCenter Server, the installation of the web server component that

supports the vSphere Web Client fails if the installer cannot look up the fully qualified domain name of the

vCenter Server from its IP address. Reverse lookup is implemented using PTR records. To create a PTR

record, see the documentation for your vCenter Server host operating system.

If you use DHCP instead of a static IP address for vCenter Server, make sure that the vCenter Server

computer name is updated in the domain name service (DNS). Ping the computer name to test the

connection. For example, if the computer name is host-1.company.com, run the following command in the

Windows command prompt:

ping host-1.company.com

If you can ping the computer name, the name is updated in DNS.

Chapter 2 System Requirements

VMware, Inc. 27

1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 225 226

Adaptec 1130U2 - Storage Controller RAID)- U2W SCSI 80 MBps Specifications Page 27

Comments to this Manuals

Adaptec 1130U2 - Storage Controller RAID)- U2W SCSI 80 MBps Specifications Page 27

Comments to this Manuals

Related products and manuals for System management software Adaptec 1130U2 - Storage Controller RAID)- U2W SCSI 80 MBps