Please disregard. I have successfully enable wireless networking.

Message was edited by:
kpaul

If you are having problems with bridged wireless networking:

1) What Mac do you have?
MBP core 2 duo with 3MG RAM

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?
4 Macs on the network: 1 MBP core 2 duo-802.11n, 2 MB's-802.11n, 1 MBP core duo-802.11g

4) What base station are you connected to?
Airport Extreme V2 802.11n

5) Have you applied the latest Airport Update from 7/30 and does it help?
Yes, before I downloaded the Beta version and now the full version and, no, it doesn't help.

6) If you are using N networking, if you drop back to G or B networking, does the problem occur?
Not sure, but I don't want to mess with my network and don't have time.

Other info:
I had no network connection in VMware when Windows was set to get an IP automatically. Airport uses 10.0.1.x IP address scheme and VMware had an IP address scheme of 192.168.15.x. Windows had internet access, but no access to the Airport network. I assigned a static IP of 10.0.1.212, which is outside the normal range of IP's assigned by the Airport Extreme. With a static IP, both the network and internet became accessible. Soon after, I lost connection with both the MBP and VMware Windows PC to the network. Regaining network connectivity was inconsistent. Stopping and starting Airport worked once, but restarting the MBP was required in another instance.

All the occurred on Sunday 8/05/07 with the BETA version, but it happen again today (Monday 8/06/07) with the final release. All this renders VMware virtually useless.

Bob

I just updated to GA and the issue persists.

Device list before joining GA-based VM to network:

[code]Int. MAC Address IP Address
br0 00:19:B9:04:FC:5A 192.168.69.100
eth2 00:17:F2:4B:A9:1D 192.168.69.150[/code]

Device list after joining VM to network:

[code]Int. MAC Address IP Address
br0 00:0C:29:A6:FA:A2 192.168.69.53
br0 00:17:F2:4B:A9:1D 192.168.69.53
br0 00:19:B9:04:FC:5A 192.168.69.100
eth2 00:17:F2:4B:A9:1D 192.168.69.150[/code]

Hi All,

Since giving my bridged VM a static IP address, I have had no problems at all with the wireless interface. Could indicate a problem with the DHCP part of the virtual interface.

Hope this helps

richard

1) MacBook Pro 2.2Ghz/Santa Rosa
2) 10.4.10
3) N
4) D-Link Extreme
5) Applied- doesnt help
6) Havent tried this.

I'm temporarily using NAT and it works. Waiting for the fix

-a

NAT, Bridged, and Host-Only networking is all leaving me with "limited or no connectivity", so there might be something bigger at play here with my configuration, too.

I'm still experiencing problems where my Bridged wireless connection will drop, forcing me to toggle my host's airport on/off.

1. MBP CoreDuo (not Core2Duo), 17"
2. Mac OSX 10.4.9
3. Wireless G
4. Linksys WRT54GL, firmware v4.30.9
5. Have not applied Apple's 7/30 Airport Patch
6. Not using N

Notes: Using Fusion 51348. I can pretty reliably cause the drop if I make heavy use of Vault (generates lots of traffic, I assume).

I've been playing around with VM 1.0 and still have Bridged network issues. Connection status is very erratic, sometimes after booting up I have internet connectivity, others I don't. I have tried uninstalling/reinstalling VM tools, no luck.
I shut down NOD32, still o luck. I ran the windows repair network connection and sometimes it found an error saying an old LSP was installed and preventing accessing the network, uninstalling this service only partially disables Nod32.

This is really annoying. I wouldn't like to swith to NAT, since by doing that I will lose my bonjour pinter and the ability to access my networked disks attached to the Airtport Extreme

Hope you guys come up with a solution real soon