|
Problems or Messages |
Solutions |
|---|---|
|
“The domain in the credentials is invalid or blank” |
This error occurs when the Credential Format is incorrect. Try the discovery using a local admin account with the user name syntax: hostname\LocalAdmin Or try the discovery with a domain admin account with the user name syntax: domain\DomainAdmin |
|
“Unable to connect to Windows server...Access is denied.” |
A Non-admin account is used when trying to add a workload—Use an admin account or add the user to the administrators group and try again. WMI connectivity failure. For each of the following possible resolutions, attempt the solution and then perform the WMI Connectivity Test again. If the test succeeds, try adding the workload again. Possible resolutions are: |
|
“Unable to connect to Windows server...The network path was not found.” |
Network connectivity failure—perform the Network Connectivity Test. If it fails, ensure that Forge and the workload are on the same network. Reconfigure the network and try again. |
NOTE:If the VMware Infrastructure Client is already installed, skip to Step 3.
From a workstation other than your Forge appliance, open a Web browser and navigate to the ESX Server’s IP address (the first IP address you configured when you set up your Forge appliance).
Click the link, then follow the instructions to download and install the software. Ignore any SSL warnings.
Login using the ESX Server (Appliance Host) IP address and the username/password you setup.
The VIC Inventory UI is displayed.
Select the Forge VM in the inventory list on the left.
Click on the Console tab.
Click > , type in cmd and press Enter.
A terminal window is displayed.
Type ping server_ip and press Enter to ping the workload.
NOTE:If the VMware Infrastructure Client is already installed, skip to Step 3.
From a workstation other than your Forge appliance, open a Web browser and navigate to the ESX Server’s IP address (the first IP address you configured when you set up your Forge appliance).
Click the link, then follow the instructions to download and install the software. Ignore any SSL warnings.
Login using the ESX Server (Appliance Host) IP address and the username/password you setup.
The VIC Inventory UI is displayed.
Select the Forge VM in the inventory list on the left.
Click on the Console tab.
From the Forge Management VM, click > , type Wbemtest and press Enter.
In the type in the name of the machine you are trying to discover with \root\cimv2 appended to it. For example, if your machine name is win2k type:
\\win2k\root\cimv2
Enter the appropriate credentials using either the hostname\LocalAdmin or domain\DomainAdmin format.
Click to test the WMI connection. If an error message is returned a WMI connection cannot be established between Forge and the workload being added.
Log into the workload that you would like to protect.
Click > .
Type dcomcnfg and press Enter.
On a Windows NT/2000 server machine, the DCOM Configuration dialog is displayed. Click the Default Properties tab and ensure that is checked.
For Windows 2003, the Component Services window is displayed. In the folder of the console tree of the Component Services administrative tool, right-click on the computer for which you want to check if DCOM is enabled and then click . Click the Default Properties tab and ensure that is checked.
If DCOM was not enabled, please enable it and restart the Windows Management Instrumentation Service (if rebooting the server is not possible) and try adding the workload again.
There are three potential blockages for the RPC service:
Windows Service
Windows Firewall
Hardware Firewall
For the Windows Service, ensure that the RPC service is running on the workload. To access the services panel, run services.msc from a command prompt. For a Windows firewall, add RPC exception.For hardware firewalls, you can try:
Putting Forge and the workload on the same side of the firewall
Opening up specific ports between Forge and the workload (see Table 7-1)
Opening up all the ports
Table 7-1 Required Source Ports