VMware VI Client error ‘Unable to connect to the MKS: Failed to connect to server {ESX-Host}:902’

KB ID 0000815 

Problem

Seen when connected to the VMware VI client software, and attempting to open a console session with a virtual machine.

Solution

This is a pretty generic error, for whatever reason the client software cannot connect to the KMS (Keyboard, Mouse, and Screen).

In NEARLY every case this is a communication issue, either the machine running the client software cannot resolve the name of the ESX host that is hosting the virtual machines, or TCP Port 902 is being blocked by a firewall.

1. If you can’t simply pop the correct name in your DNS, then add the name and IP to the machines, (the one running the VI client software) host file. You will locate this in;

[box] C:WindowsSystem32Driversetc [/box]

2. Open it with Notepad, and add the IP and name of your ESX host(s), Note: I’m also putting the name and IP of my Virtual Center server as well. Save the file and try again.

3. You should now be able to connect.

It’s NOT DNS!

If you can happily resolve the name and are sure that the port is not being blocked, then have you made any IP changes? Is the default gateway on the ESX Server set correctly? And finally restart the management agents on the host, either from the console, or by running ‘/sbin/services.sh restart’.

I’ve also fixed this error by shutting down the machine > removing it from the inventory > then browsing the storage, to locate the .vmx file > then simply import it back again.

Related Articles, References, Credits, or External Links

NA

Sharing Files from Ubuntu to Windows

KB ID 0000412

Problem

If you have only a few files to share, you might want to consider using Dropbox, however if you want to share your files over the network then you need to install samba and configure it.

Solution

 

Related Articles, References, Credits, or External Links

Special Thanks to Morbuis1 Over at the Ubuntu Forms for the help.

Samba Install Error

 

Exchange 2010 Install Error – ‘Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server’

KB ID 0000577 

Problem

I had a nice clean install on a greenfield site today, Exchange 2010 Standard c/w SP1 on Server 2008 R2, so I was not happy when this happened!

Error:
The following error was generated when “$error.Clear();
if ($RoleStartTransportService)
{
start-SetupService -ServiceName MSExchangeTransport
}
” was run: “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”.

Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

Solution

A quick google on this error, turned up loads of posts that said, “This is because you’ve disabled (Unticked) IPv6 on the properties of the nerwork card”, like so;

However as you can see, mine had NOT BEEN DISABLED

Every post and answer that had been accepted said either, retick this box, or manually start the Microsoft Exchange Transport service, this also failed. Turns out the problem WAS related to IPv6, This server was multi homed (I don’t know if that’s relavant).

What Fixed it for me:

1. On the Exchange server, Start >In the Search/Run box type regedit {Enter}.

2. Navigate to:

[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Tcpip6 > Parameters [/box]

Create a new 32 BIT DWORD value called “DisabledComponents”, and set its value to 0xffffffff (Hexadecimal) or 4294967295 (Decimal).

3. Finally locate the server’s hosts file (C:WindowsSystem32Driversetchosts) and make sure if there is an IPv6 entry for ::1 it has been commented out (i.e. the line has a hash symbol at the start of it).

 

Related Articles, References, Credits, or External Links

NA

Cisco ASA – View The Contents of an Object and Object-Group

KB ID 0001043 

Problem

My colleague loves the ASDM, I put up with it and prefer command line. We were troubleshooting a problem the other day and he said, there this is why I prefer the ASDM, just ‘hover’ over an object-group and it will show you the contents of it.

Now if (like my test firewall above) you only have a few hosts, then I don’t see the point, but if you have a very complicated config with hundreds of object-groups and thousands of hosts, even troubleshooting why host ‘x’ can’t get to server ‘y’ on port ‘z’ can be a painstaking process.

So I dropped to CLI and tried to do the same;

[box]

Petes-ASA(config)# show object-group Obj-ALL-PROD-DMZ
                                   ^

ERROR: % Invalid input detected at '^' marker.

Petes-ASA(config)# show object-group network Obj-ALL-PROD-DMZs 

                                           ^

ERROR: % Invalid input detected at '^' marker.

[/box]

 

Solution

View Contents of an Object Group

Turns out you need to use the ‘id’ parameter, or it won’t work;

[box]

Petes-ASA(config)# show object-group id Obj-ALL-PROD-DMZs

object-group network Obj-ALL-PROD-DMZs

network-object 192.168.110.0 255.255.255.0

network-object 192.168.121.0 255.255.255.0

network-object 192.168.130.0 255.255.255.0

network-object 192.168.141.0 255.255.255.0

network-object 192.168.140.0 255.255.255.0

network-object 192.168.210.0 255.255.255.0

network-object 192.168.220.0 255.255.255.0

Petes-ASA(config)#

[/box]

I’ve been using that a lot this week.

View Contents of an Object

If you try an to the same this for an object, you will get nothing, you need to add the run keyword as follows;

[box]

Won't Work!
Petes-ASA# show object id Internal_RDP_Server    
object-group Internal_RDP_Server does not exist
Petes-ASA# 

Use 'run'
Petes-ASA# show run object id Internal_RDP_Server
object network Internal_RDP_Server
 host 192.168.100.10

[/box]

Related Articles, References, Credits, or External Links

Original article written 25/03/15