I noticed that ESXi Update 1 does not seem to automatically configure the Guest VM network settings. These are the extra steps that I had to follow:
Category: Network Issues
Here are the security requirements that I often use for creating a Windows share for the Guest account (without a password):
Remove generic password restrictions
Control Panel > Administrative Tools > Local Security Policy > Account Policies
1. Password Policy
a. Minimum password age = 0
b. Minimum password length = 0
c. Password must meet complexity requirements = Disabled
Remove Guest restrictions for User Rights Assignment and Security Options
Control Panel > Administrative Tools > Local Security Policy > Local Policies
1. User Rights Assignment
a. Deny Logon Locally (Remove Guest) – check this….don’t think this is required.
b. Deny access to this computer from the network (Remove Guest)
2. Security Options
a. Accounts: Guest account status = Enabled
Remove Guest password
Control Panel > User Accounts (Windows 7 – Click on the Manage other account link)
1. Click on Guest and remove the password (Windows 7 – you may not need to perform this step)
Note: Please be aware that this will allow anyone access to your Guest share, so be careful about the sharing permissions you set for the Guest user.
At my workplace, I’ve set up an FTP server so that colleagues from across the globe can download some files that I make available for them. I noticed that two people in the same office were downloading the exact same file (10 GB in size) except one was about 10% complete while the other was about 95% complete. I wanted to find out their computer hostnames – usually just an abbreviation of their real names – so that I could let them know that they were both downloading the same file.
I always knew about the ping and nslookup commands. But none these commands would always give me the correct hostname when supplied with an ip address.
ping - a <ip_address>
nslookup -a <ip_address>
While these commands worked for fixed ip addresses, they never seemed to work for dynamic ip addresses, and would always return a dhcp-created hostname, rather than the actual hostname of the machine.
I was delighted when I discovered a command that worked for all cases:
nbtstat -A <ip_address>
This command actually gave me a list of all the network adapters that the host contained. The Local Area Connection adapter had the actual hostname that I was looking for.
I’d always used
pushd to store the location of working directories when writing bat scripts. I didn’t realise that you could also use the
pushd command to access unc paths:
This command creates a new drive for the share. You can use
popd to remove the drive association with the UNC share.
A colleague was having trouble with his Windows XP network connection on his Dell laptop after coming back from China. He was able to access the local intranet at work but could not access the internet. I’d never experienced this before. We tried the usual sorts of commands to renew the ip (eg.
ipconfig /release and
ipconfig /renew). None of these would work. Even after re-installing windows he still wasn’t able to connect to the internet!!
The last resort was to ring up Dell support. They suggested to run the following command:
netsh winsock reset
This fixed the problem.
This command resets the Winsock catalog to the default configuration. The fact that even after re-installing Windows that the network wouldn’t work suggests that this issue was hardware/firmware related.
Experts exchange states that this command can be useful when a malformed Winsock Layered Service Provider (LSP) is installed that results in loss of network connectivity. But they also advise that while this command can restore network connectivity, it should be used with care because any previously-installed LSPs will need to be re-installed.