| September 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
| Aug Oct | ||||||
This site is no longer maintained.
My current weblog.
Thursday, September 12, 2002No difference under any 3.x version of VMware. Host-only and NAT configurations perform just fine. At this point I have to suspect an XP hotfix or one of the (many) driver updates for my NIC, an Intel Pro 10/100. I'm not even going to think about rolling back all of those...
Had a bright idea: Start with a host-only virtual network, disable the VMware DHCP server, add XP's native Bridge feature. Unfortunately, VMware's virtual network driver doesn't support that. Can't use ICS either, my physical LAN uses the IP range it wants, and I can't change that.
Bah. Switching to the NAT config.
Re-installed 3.1, no difference.
Downloading 3.2 RC and backing up my Virtual Machines now...
Considering downgrade to 3.0, in theory I don't need anything from the newer versions.
I am still having the problem described in VMware Networking Weirdness. This seems to have started with my upgrade to VMware 3.1. I never had trouble under 3.0, although it had been a while since I used it. The problem isn't exclusive to my Debian guest, for giggles I booted an old Windows NT 4 guest and it also experienced the same transfer problem.
I've scoured the VMware newgroups and FAQs. Disabled the NAT and Host-only adapters. Tried adding "vnet.sendClusterSize=1" to the guest's config file. Just now I disabled everything on my NIC except TCP/IP and VMware Bridge and rebooted. No difference.
At this point I was thinking I should open a support case with VMware. I head on over to their site, log in, and discover that my expected "Complimentary 30 Days Support" is Expired. Those buggers start the clock on the date of purchase.
Their per-incident rate is $90.
Today I am not a happy VMware customer.
