I don’t think, Ive ever run the VMware Standalone Converter, without at least one error message or popup complaining about something! Today I was trying to convert a clients old Windows Server 2003 document management server, when trying to deploy the agent this happened;
Unable to connect to the network share ‘{Sever-name-or-IP} \ADMIN$’.
Solution
It’s a pretty descriptive error, can you map a drive to this machine and open a network share manually? Is the ‘server service’ running? In my case the problem was easily diagnosed;
As I wasn’t about to start enabling SMBv1 on the clients Windows 2019 server! So I simply installed the VMware Standalone converter on one of their existing 2008 members servers instead, and ran it from there.
Related Articles, References, Credits, or External Links
The VPN connection failed due to unsuccessful domain name resolution.
Solution
Firstly, (and obviously) the name you are typing in the AnyConnect window can be resolved can’t it? If not then you might want to consider some employment that does not involve computers.
Secondly (this is what usually trips me up) did you copy and paste the name? If so is there a space on the end?
This name may also be incorrect in the profile.xml that’s associated with this VPN, to check, the location of that file is covered in this article.
Also check that the VPN device, does not need to be connected to on a different port, as per this article.
Related Articles, References, Credits, or External Links
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
Seen when trying to connect the Windows 8 mail client to Exchange 2010 (that is using a self signed certificate).
Error
Unable to connect. Ensure that the information you’ve entered is correct.
Solution
This is a right pain! My Exchange 2010 server is using a self signed certificate, and even though the Windows 8 client trusts my domain CA, and it has imported the cert that Exchange is using, it still would not work.
I Know the cert is OK, Outlook Web Access and Outlook work fine without reporting any certificate errors. I even put the CAFQDN in the Windows 8 hosts file in case it needed to see that (because I read that the problem is related to the client not being able to see the CA’s certificate revocation list).
The only way I found to cure this problem, and let me successfully connect to Exchange, is to remove the self signed certificate and use a purchased certificate.
I upgraded a clients ASA5510 firewall(s) yesterday. Post upgrade he got this error;
The secure gateway has rejected the connection attempt. A new connection attempt to the same or another secure gateway is needed, which requires re-authentication. The following message was received from the secure gateway: No assigned address.
Solution
Thankfully the error is pretty descriptive, the remote client can not get an IP address. So I’m missing an ip local pool command, or that pool is missing from the AnyConnect tunnel-group. To Test;
[box]
WHAT IT SHOULD LOOK LIKE
Petes-ASA# show run | incl pool ip local pool SSL-POOL 172.16.1.1-172.16.1.254 mask 255.255.255.0 address-pool SSL-POOL Petes-ASA#
[/box]
In the example above, I have my address pool, and the second line is that pool being applied to the tunnel-group I’m using for AnyConnect.
If you are missing both (I was post upgrade)
Note: Change the subnet to match your requirements, and DONT use addresses that are in use INSIDE your LAN.
[box]
User Access Verification
Password:
Type help or '?' for a list of available commands.
Petes-ASA> enable
Password: ********
Petes-ASA# configure terminal
Petes-ASA(config)# ip local pool SSL-POOL 172.16.1.1-172.16.1.254 mask 255.255.255.0
[/box]
If you are missing the address-pool command
The IP pool used, is defined in the tunnel group, (in the general-attributes section).
[box]
HERE THE POOL REFERENCE IS MISSING;
User Access Verification
Password:
Type help or '?' for a list of available commands.
Petes-ASA> enable
Password: ********
Petes-ASA# show run tunnel-group
tunnel-group SSL-PROFILE type remote-access
tunnel-group SSL-PROFILE general-attributes
authentication-server-group Windows-IAS
default-group-policy SSL-POLICY
tunnel-group SSL-PROFILE webvpn-attributes
group-alias PROFILE enable
Petes-ASA#
TO ADD IT IN (Take note of the tunnel group name SSL-PROFILE (above))
User Access Verification
Password:
Type help or '?' for a list of available commands.
Petes-ASA> enable
Password: ********
Petes-ASA# configure terminal
Petes-ASA(config)# tunnel-group SSL-PROFILE general-attributes
Petes-ASA(config)# address-pool SSL-POOL
Petes-ASA(config)#
WHAT IT SHOULD LOOK LIKE
User Access Verification
Password:
Type help or '?' for a list of available commands.
Petes-ASA> enable
Password: ********
Petes-ASA# show run tunnel-group
tunnel-group SSL-PROFILE type remote-access
tunnel-group SSL-PROFILE general-attributes
address-pool SSL-POOL
authentication-server-group Windows-IAS
default-group-policy SSL-POLICY
tunnel-group SSL-PROFILE webvpn-attributes
group-alias PROFILE enable
Petes-ASA#
This happened because (pre migration) I had the following command in the firewall config;
[box]
ip local pool SSL-POOL 172.16.33.1 mask 255.255.255.0
[/box]
The firewall was (at that time) running version 8.2, in the past that syntax was fine, now you would need to specify the mask as 255.255.255.255 (to lease one address). During conversion this command was dropped, so it was never added to the tunnel-group either.
Related Articles, References, Credits, or External Links
A while ago I spun up a CentOS server in VMware Workstation, and I could not get it connected to the network, I was in a bit of a hurry, so I blew it away and just built a new server with CentOS 6. This week I’ve been using VirtualBox and spun up a new CentOS 7 server and had the same problem.
Solution
1. Quite why CentOS 7 does this I’m not sure, My NIC is called enp0s3 (run ‘ip addr’ to find yours). Then take a look at;
