跳到主要內容

Introduction of vmWare TCP Port


port 80
vCenter Server requires port 80 for direct HTTP connections. Port 80 redirects requests to HTTPS port443. This is useful if you accidentally use http://server instead of https://server.

port 389
This port must be open on the local and all remote instances of vCenter Server. This is the LDAP portnumber for the Directory Services for the vCenter Server group. The vCenter Server system needs tobind to port 389, even if you are not joining this vCenter Server instance to a Linked Mode group. Ifanother service is running on this port, it might be preferable to remove it or change its port to differentport. If needed, you can run the LDAP service on any port from 1025 through 65535.If this instance is serving as the Microsoft Windows Active Directory, change the port number from 389to an available port from 1025 through 65535.

port 443
The default port that the vCenter Server system uses to listen for connections from the vSphere Client.To enable the vCenter Server system to receive data from the vSphere Client, open port 443 in thefirewall.The vCenter Server system also uses port 443 to listen for data transfer from the vSphere Web AccessClient and other SDK clients.If you use another port number for HTTPS, you must use : when you log in to thevCenter Server system.

port 636
For vCenter Linked Mode, this is the SSL port of the local instance. If another service is running on thisport, it might be preferable to remove it or change its port to different port. If needed, you can run theSSL service on any port from 1025 through 65535.


port 902
The default port that the vCenter Server system uses to send data to managed hosts. Managed hostsalso send a regular heartbeat over UDP port 902 to the vCenter Server system. This port must not beblocked by firewalls between the server and the hosts, or between hosts.

port 902/903
Ports 902 and 903 must not be blocked between the vSphere Client and the hosts. These ports are usedby the vSphere Client to display virtual machine consoles.

port 8080
Web Services HTTP. Used for the VMware VirtualCenter Management Webservices.

port 8443
Web Services HTTPS. Used for the VMware VirtualCenter Management Webservices.

留言

這個網誌中的熱門文章

如何在AD網域中刪除已不存在的Exchange Server 物件

個人在建置VM時,多裝一台Exchange Server 2010, 之後直接刪除此VM, 造成AD網域中, 此物件仍然存在在EMC(Exchange Management Console)之中, 如下圖所示: 因此, 要將此物件從EMC中移除, 必須要AD DS內將此物件刪除. 接下來所有操作皆在DC上執行(找其中一台DC即可) 1. 登入一台網域控制站 2.在開始/執行, 輸入'adsiedit.msc'指令 啟動ADSI編輯器 3.在工具欄內點ADSI編輯器後按右鍵,選擇'連線到'項目. 4.在連線設定畫面中,在連線點的對話框中,選取熟知的命名內容, 按下拉式選單, 選擇'設定',後按確定. 如下圖所示: 5.在左側展開CN=Configuration [domain] → CN=Services → CN=Microsoft Exchange → CN=[organization] → CN=Administrative Groups → CN=Servers後, 如下圖所示: 在中間視窗框中, 將欲刪除的Exchange Server 物件按右鍵刪除, 如下圖所示 刪除之後, 回到EMC後, 可以發現, 被刪除的Exchange Server已消失不見. 如下圖所示:

強制移除網域控制站

程序 1:僅限 Windows Server 2003 SP1 或更新版 Service Pack 按一下 [開始],指向 [程式集],指向 [附屬應用程式],然後按一下 [命令提示字元]。 在命令提示字元中,輸入 ntdsutil ,然後按 ENTER。 輸入 metadata cleanup ,然後按 ENTER。系統管理員可以根據所提供的選項執行移除,但在進行移除之前,必須先指定其他設定參數。 輸入 connections ,然後按 ENTER。此功能表是用於連線至發生變更的特定伺服器。如果目前登入的使用者沒有系統管理權限,可以先指定使用不同的認證,再建立連線。如果要執行這項操作,請輸入 set creds DomainNameUserNamePassword ,然後按 ENTER。如需 null 密碼,請輸入 null 做為密碼參數。 輸入 connect to server servername ,然後按 ENTER。您應該會收到已成功建立連線的確認訊息。如果發生錯誤,請確認連線所使用的網域控制站是否可以使用,以及您所提供的憑證在伺服器上是否擁有系統管理員權限。 注意 如果您嘗試連線到同一個想要刪除的伺服器,當刪除步驟 15 中提及的伺服器時,您可能會收到下列錯誤訊息: 錯誤 2094。無法刪除 DSA 物件 0x2094 輸入 quit ,然後按 ENTER。[中繼資料清除] 功能表便會出現。 輸入 select operation target ,然後按 ENTER。 輸入 list domains ,然後按 ENTER。隨即出現樹系的網域清單,每個網域都有相關的編號。 輸入 select domain number ,然後按 ENTER,其中 number 是與網域相關的編號,而您要移除的伺服器為該網域的成員。您所選取的網域是用來判斷要移除的伺服器是否為該網域的最後一個網域控制站。 輸入 list sites ,然後按 ENTER。隨即出現網站清單,其中每個網站都有相關的編號。 輸入 select site number ,然後按 ENTER,其中 number 是與網站相關的編號,而您要移除的伺服器為該網站的成員。您應該會收到列出所選擇網站與網域的確認訊息。 輸入 list servers in site

File Explorer (explorer.exe) Crashes in Windows 8.1- Fix It

Reference from : http://www.registryrecycler.com/blog/2013/11/file-explorer-crashes-in-windows-8-1-fix-it/ Although, Windows 8.1 has adroitly been covering the left overs of Windows 8, it also has some enduring issues that need to be addressed. One of these issues is a frequently crashing File Explorer. Not all, but a few subscribers of this new update are experience the glitch and are in search of an appropriate solution. To discourse this issue in correct direction, we would need to know the prior causes in specific to respond accordingly. Given below in this article are some genuine reasons, why the explorer crashes promptly on being launched and their relevant workarounds. Cause and Solution 1 The first reason that we can think of, is third party handlers of cloud storage integrated with your File explorer. These have the potential to hinder an explorer work properly, as it can be assumed that third party extensions may have compatibility issues with Windows 8.1 explo