Based on the various forum posts, I would like to consolidate and collect more information in this thread. Please respond here even if you responded elsewhere, it will allow us to more easily find trends if everyone responds here:

If you are having problems with bridged wireless networking:

1) What Mac do you have?
iMac 24" 2.33 with 7600GT

2) What version of Mac OS X are you running?
10.4.10

3) Are you running B, G, N or a combination of wireless networking technologies?
B,G &N on an Airport Extreme

4) What base station are you connected to?
Airpoirt Extreme 802.11N with fast ethernet

5) Have you applied the latest Airport Update from 7/30 and does it help?
Yes, and no.

6) If you are using N networking, if you drop back to G or B networking, does the problem occur?
Yes

OK, I've got some weird stuff happening here.
On my Macbook, first generation I have no problems at all running Fusion with bridged over the wireless.
On the iMac 24 I have no problems running bridged over wireless if I use an Airport Express.

If I switch to the Airport Extreme, using exactly the same settings my connection is killed. I can get an IP address from the Airport, but as soon as I try and do any serious work over the network the connection slows right down and is effectively useless. This affects the Mac as well and its networking gets hammered while i'm doing stuff in Fusion.

I hope this is of some help.

When running in bridged mode, I keep getting the message:

"The wireless network appears to have been compromised and will be disabled for about a minute"."

It also brings down the Cisco 800 WAP at my work for 60 seconds, which was obviously irritating all my colleagues. The error log in IOS shows:

"Aug 23 10:05:30 172.16.11.1 1807: Aug 23 2007 10:05:28 AEST: %DOT11-4-
TKIP_MIC_FAILURE_REPORT: Received TKIP Michael MIC failure report
from the station 001b.63c5.bf65 on the packet (TSC=0x0) encrypted and
protected by pairwise key."

1) What Mac do you have?

MacBook Pro SR 2.4Ghz Core 2 Duo, 4GB RAM.

2) What version of Mac OS X are you running?

Mac OS X 10.4.10 (8R2232)

3) Are you running B, G, N or a combination of wireless networking technologies?

G

4) What base station are you connected to?

Cisco 800

5) Have you applied the latest Airport Update from 7/30 and does it help?

Yes, No

6) If you are using N networking, if you drop back to G or B networking, does the problem occur?

N/A

1) MacBook Pro C2D 2.33GHz 3GB RAM

2) OS X 10.4.10

3) N router with N and G hosts

4) Airport Extreme N, Firmware 7.1.1

5) Yes, No

6) Yes

1. MBP 2.4 (SR)
2. 10.4.10
3. Combination
4. Airport Extreme (802.11n)
5. Yes, no.
6. N/A

Problem doesn't seem to occur (or at least less frequently) with NAT. Haven't tried bridged with static IP.

Hi everyone,

I'm having the same problems as everyone here has stated where I loose network
connectivity for a second and then it comes back. I only know this because I loose all
my SMB shares from my server and I have to reattach them. But that is where my
similarity ends! Everyone here is talking about wireless where as I do NOT run wireless
on this machine. I am straight 1000BaseT to my server, but there is an Airport Extreme
set to 802.11n only for my other machines. I have not tested the Bridge vs. NAT solution
yet but hopefully this week I will. I REALLY love running Fusion in Unity mode but it was
quite annoying this long weekend as I kept loosing my servers. Last night I killed Fusion
and left my SMB connects and *POOF* they were still attached in the morning where as
when Fusion was running I'd get 15 minutes if I was lucky.

1) Aluminum 24" iMac w/3GB

2) OS X 10.4.10

3) Not on this machine. Airport is turned OFF. There is an airport extreme on the network
though.

4) Airport extreme w/802.11n exclusive

5) Latest firmware and software installed, does not help

6) Again, I get dropped off without wireless.. I'm not sure this is a "wireless" issue, you're
just hearing from a large number of wireless people

Many thanks and keep up the GREAT work!! VMware is the best!

Michael Bender
Orlando, FL

Looking further into this problem (bridged networks with the Airport card in SR MBPs). and trying out some of the suggested resolutions, I came across an interesting log entry in the system.log file:

Sep 4 12:21:00 LJR-MBP kernel[0] Your ethernet driver is not compatible with vmware's bridged networking.

Funny enough, after a search I haven't found any other posts citing a reference to this log entry.

Anyone else?

I assume the "bridged network issue" is the one that results in the airport process' high cpu utilization.

1) What Mac do you have?
MBP 2.4Ghz (Santa Rosa)

2) What version of Mac OS X are you running?
10.4.10 with all public updates

3) Are you running B, G, N or a combination of wireless networking technologies?
B and G

4) What base station are you connected to?
Linksys, Cisco, others

5) Have you applied the latest Airport Update from 7/30 and does it help?
applied, no help

6) If you are using N networking, if you drop back to G or B networking, does the problem occur?
not tested

-
any ETA on a resolution to this? This is a major issue, and NAT is not a viable option for anyone using IPSEC or VoIP. This either needs to be resolved or VMware should start offering refunds.

VMware should also step up to the plate and offer all users that purchased this "beta" copy of 1.0 full support until after at least the common bugs are resolved. Of course, this doesn't add value when the support department is incapable of providing meaningful support anyway.

The product is no longer "beta", so why are we suffering through problems that should have been resolved from Beta testing?