vmware vsphere client console black

Posted on 2014-12-22
Last Modified: 2015-01-01
Hello Experts,

I'm getting a blank screen when I attempt to view my VM through console screen.

I'm following the recommendations from the following knowledge base:

However, each time I add permissions I get the following error message

Can someone help me please


Question by:cpatte7372
  • 12
  • 6
LVL 119

Accepted Solution

Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40512979
By Default with Default Permissions without changing them as an Administrator, you should be able to view the console.

Is Port 902 TCP being blocked?

e.g. telnet <ip address> 902

if you get no connection, it's blocked.

The console is a custom version of VNC via Port 902.

Author Comment

ID: 40512983
Hi Andrew,

I have just rebooted server. I will try that suggestion when it comes back

Author Comment

ID: 40512990
Hi Andrew,

When I telnet I get the following error message:

220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported, NFCSSL supported
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

LVL 119
ID: 40513000
Okay, that is how it should respond.

and you still get a black screen on ALL VMs ?

also check that you can resolve the ESXi server IP Address by hostname, and fqdn

so check with ping and tracert to hostname and iP Address

Author Comment

ID: 40513056
Hi Andrew,

I'll check.

I should mention that I don't have this problem when connecting from home.

Author Comment

ID: 40513072
Hi Andrew,

The server hasn't been defined with an fqdn.

I am hiring it online from 'Bare Metal Servers'

Author Comment

ID: 40513076
and you still get a black screen on ALL VMs ?

LVL 119
ID: 40513098
so, if you have got a fqdn, created one!

edit your hosts file and add

and then use the vSphere Client to connect to

Author Comment

ID: 40513188
So Andrew,

I added the following;


But when I ping the name its not resolved

Author Comment

ID: 40513190
I don't understand why I don't have the same problem from my home?
LVL 119
ID: 40513221
name resolution, DNS.

if you ping

it should resolve and ping

create a simpler DNS name

Author Comment

ID: 40513232
Hi Andrew,,

So I creates as shown below,

but still won't resolve the name

# Copyright (c) 1993-2009 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
#          # source server
#              # x client host

# localhost name resolution is handled within DNS itself.
#       localhost
#      ::1             localhost
LVL 119
ID: 40513263
just put the word....

64.xx.xx.xx server

ping server

does it resolve to server, and ping.....

you may also want to do a

ipconfig /flushdns

Author Comment

ID: 40513264

I added the following:


Author Comment

ID: 40513272
OK, I'll try that

Author Comment

ID: 40513284

I tried exactly
C:\Users\Pattec01>ping server
Ping request could not find host server. Please check the name and try again.
LVL 119
ID: 40513296
Are you editing the hosts file?

are you saving the hosts file?

are you editing the hosts file as Administrator ?

something weird or not correct with your hosts files.

host file is normally located in windows in


so if you do....

type c:\windows\system32\drivers\etc\hosts

what do you get ?

Expert Comment

by:Dawid Fusek
ID: 40514133
hi mate,

The black screen on VI/vSphere Console can be caused due to the following reasons
1. As Andy suggests, issues related to DNS/FQDN of host/guest
Verify the DNS/FQDN of both ESXi host and guest
2. ESXi host may need to restart management agent services (kb1003490)
Check the other VMs hosted by the same ESX/ESXi host.If they don’t have issue this may not be the cause
- here also sometimes happens that VM Console are working when You concect directly to ESXi host but not working when You connect via vCenter Server connection, then it's a problem with vCenter Server (fw, services. lack of memory or disk space).

3. Video memory of VM is too small for WDDM video driver
  (C:\Program Files\Common Files\VMware\Drivers\wddm_video\)
I suggest video RAM increase to 32-64 MB (kb1016770), it sometimes happens that older vm's (or virtual appliances) may have as little as 4MB which is too small to work correctly in most cases
4. Firewall blocking ports 902/903 (kb749640)
- fw may do it on the ESXi host (do it when you access it via HTTP Proxy or sometimes via VPN or other LAN segment):
To enable port "on proxy", do this
   Log in to ESXi, open /etc/vmware/config
   add line -
   vmauthd.server.alwaysProxy = "TRUE"
 service mgmt-vmware restart    (it will restart all management services on ESXi host)

- FW may do it on your workstation
So check local fw rules, maybe disable fw for a while to test it with disabled fw (Enable FW again after test !!!)

- using a WWW/HTTP proxy server on a management workstation
/set in Control Panel/Internet Options/Connections/LAN Settings/Proxy Server/Address
/set as via GPO as a windows system proxy (check by command "netsh winhttp show proxy")
check without a proxy

- company FW may also block access to these ports, so contaxt an corporate FW admins

Are this problem come to other vm or 1 particular vm?

Are you connect via vCenter Server or directly to ESXi? if via vCenter Server, do You check directly to ESXi? is the situation the same?

To troubleshoot this you can also connect via RDP to some VM on that ESXi (but not to that which you have a problem) and then install vSphere Client here and then connect to Console again and check if it working, if working ok the problem is rather closer to yous workstation/FW/DNS or LAN/FW, but if not working the problem may be closer to ESXi itself, DNS or vCenter Server or VM video ram.

best regards

Author Closing Comment

ID: 40527083
Thanks Andrew

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
VMware vCloud Director - Automatic SNAT Creation 2 84
vm server with sound card 3 76
backup strategy concern 5 79
Error upgrading from esxi 5.5 to 6.5 15 84
HOW TO: Install and Configure VMware vSphere Hypervisor 6.5 (ESXi 6.5), Step by Step Tutorial with screenshots. From Download, Checking Media, to Completed Installation.
HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
Teach the user how to install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question