Hi. I've been reading some posts on peoples bridged networking issues hoping that they would help me solve my bridged networking but unfortunatley I don't think they have.
I am unable to connect to the net wirelessly using bridged network mode. I can connect wirelessly when I use NAT.
System specifications:
VMware fusion Version 1.1.1 Build 72241.
Windows XP is fully updated.
OSX 10.4.11 fully updated.
Airport extreme base station fully updated, connecting to it wirelessly.
Any help would be appreciated.
I've the same problem....
after upgrade to VMWare Fusion v1.1.1 the Network (connected with cable) not work in Bridged mode!!!
Host is MAC OS Leopard 10.5.1
Guest is Windows XP SP2
How to downgrade to VMWare Fusion 1.1?
please refer the following thread
1) I've not the problem with the Wi-Fi Network but with cable connection...
Before upgrade to v1.1.1 the Bridged working well!
2) If I want to downgrade to v1.1 is enough to remove VMWare Fusion and reinstall the version 1.1?
Thanks for your help. I installed the fix but it did not solve the problem. After I started my VM I got this messages:
"Module version mismatch 4 !
= 5. Please update host.
Virtual device Ethernet0 will start disconnected."
It mentioned in the thread you directed me to that if you still encounter networking problems to include the following information from console.app etc.
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: Initializing module (version 1.1.1fc1, build-65852).
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: VMNet_Start allocated gOSMallocTag
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: Module initialized.
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x3f60700.
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: VMNetConnect: returning port 0x3f60700
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: VMNetDisconnect called for port 0x3f60700
Feb 1 06:14:28 william-woodwards-computer kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x3f60700.
Feb 1 06:15:31 william-woodwards-computer kernel[0]: vmmon: offset 0: 44
Feb 1 06:15:31 william-woodwards-computer kernel[0]: vmmon: offset 1: 12
Feb 1 06:15:31 william-woodwards-computer kernel[0]: vmmon: offset 2: 24
Feb 1 06:15:31 william-woodwards-computer kernel[0]: vmmon: offset 3: 28
Feb 1 06:15:31 william-woodwards-computer kernel[0]: vmmon: offset 4: 40
Feb 1 06:15:32 william-woodwards-computer kernel[0]: vmmon: Warning: XXXMACOS: Implement ioctl APIC_BASE
Feb 1 06:15:33 william-woodwards-computer kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x5c86200.
Feb 1 06:15:33 william-woodwards-computer kernel[0]: vmnet: VMNetConnect: returning port 0x5c86200
Feb 1 06:15:33 william-woodwards-computer kernel[0]: vmnet: VMNetDisconnect called for port 0x5c86200
Feb 1 06:15:33 william-woodwards-computer kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x5c86200.
Feb 1 06:16:26 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 0 -> 19
Feb 1 06:16:26 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 19 -> 0
Feb 1 06:16:26 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 0 -> 19
Feb 1 06:16:29 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 19 -> 83
I'm also trying to get bridged networking to work, NAT works fine.
I am only using a wireless connection at home.
Thanks for your help.
Considering the error message I got when starting the VM (module version mismatch 4!...) I attempted to revert the fix to the original version in terminal. Still getting the same error message when I start the VM.
I then attempted to acess the internet wired (instread of wireless) but no luck. I also tried reverting back to NAT and that didn't work.
I then double checked what I entered in terminal and noticed that I didn't do it properly. I then redid everything in terminal. My VM is now not starting and I am getting this error message, "failed to connect to peer process".
Any help would be appreciated.
Here is some info from the console to add to my reply above. It may be useful, I don't know.
Feb 1 08:57:55 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion ; USER=root ; COMMAND=./boot.sh -stop
Feb 1 08:58:23 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion/kexts ; USER=root ; COMMAND=/bin/mv vmnet.kext.1.1fc1
Feb 1 08:58:50 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion/kexts ; USER=root ; COMMAND=/bin/mv vmnet.kext.disabled.*vmnet.kext
Feb 1 08:59:26 william-woodwards-computer kernel[0]: vmmon: Warning: XXXMACOS: Implement ioctl APIC_BASE
Feb 1 08:59:26 william-woodwards-computer kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x5d63800.
Feb 1 08:59:26 william-woodwards-computer kernel[0]: vmnet: VMNetConnect: returning port 0x5d63800
Feb 1 08:59:26 william-woodwards-computer kernel[0]: vmnet: VMNetDisconnect called for port 0x5d63800
Feb 1 08:59:26 william-woodwards-computer kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x5d63800.
Feb 1 08:59:30 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 0 -> 19
Feb 1 08:59:32 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 19 -> 83
Feb 1 09:10:01 william-woodwards-computer kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x67e8a00.
Feb 1 09:10:01 william-woodwards-computer kernel[0]: vmnet: VMNetConnect: returning port 0x67e8a00
Feb 1 09:10:02 william-woodwards-computer kernel[0]: vmnet: VMNetDisconnect called for port 0x67e8a00
Feb 1 09:10:02 william-woodwards-computer kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x67e8a00.
Feb 1 09:10:53 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 83 -> 19
Feb 1 09:10:54 william-woodwards-computer kernel[0]: vmmon: host clock rate change request 19 -> 0
Feb 1 09:10:55 william-woodwards-computer kernel[0]: vmmon: Cleaned up 99589 virtual main memory pages from VM 0x5ac7004.
Feb 1 09:10:55 william-woodwards-computer kernel[0]: vmmon: Cleaned up 3321 monitor anonymous pages from VM 0x5ac7004.
Feb 1 09:10:55 william-woodwards-computer kernel[0]: vmmon: Cleaned up 6177 user anonymous pages from VM 0x5ac7004.
Feb 1 09:11:55 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion ; USER=root ; COMMAND=./boot.sh --stop
Feb 1 09:11:55 william-woodwards-computer VMware Fusion 72241: Shutting down VMware Fusion:
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Service stop
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Deregistering for power state changes
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Removing module.
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Fast clock thread stopping...
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Fast clock thread stopped.
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Module removed.
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmmon: Service free
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmci: Removing module.
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmci: Module removed.
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmnet: Removing module.
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmnet: VMNet_Stop freeing gOSMallocTag
Feb 1 09:11:55 william-woodwards-computer kernel[0]: vmnet: Module removed.
Feb 1 09:13:06 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion/kexts ; USER=root ; COMMAND=/bin/mv vmnet.kext vmnet.kext.1.1fc1
Feb 1 09:13:34 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion/kexts ; USER=root ; COMMAND=/bin/mv vmnet.kext.disabled.20080201.061424 vmnet.kext
Feb 1 09:14:06 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion ; USER=root ; COMMAND=./boot.sh --start\nsudo ./boot.sh --start.
Feb 1 09:19:37 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion ; USER=root ; COMMAND=./boot.sh --stop
Feb 1 09:19:37 william-woodwards-computer VMware Fusion 72241: Shutting down VMware Fusion:
Feb 1 09:20:15 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion/kexts ; USER=root ; COMMAND=/bin/mv vmnet.kext vmnet.kext.1.1fc1
Feb 1 09:20:22 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion/kexts ; USER=root ; COMMAND=/bin/mv vmnet.kext.disabled.* vmnet.kext
Feb 1 09:20:44 william-woodwards-computer sudo: william : TTY=ttyp1 ; PWD=/Library/Application Support/VMware Fusion ; USER=root ; COMMAND=./boot.sh --start.\nsudo ./boot.sh --start\nsudo ./boot.sh --start
Feb 1 09:38:06 william-woodwards-computer kernel[0]: AppleYukon - en0 link is down
Feb 1 09:38:09 william-woodwards-computer configd[36]: posting notification com.apple.system.config.network_change
Feb 1 09:38:09 william-woodwards-computer configd[36]: rtmsg: error writing to routing socket
Feb 1 09:38:09 william-woodwards-computer configd[36]: rtmsg: error writing to routing socket
Feb 1 09:38:09 william-woodwards-computer configd[36]: posting notification com.apple.system.config.network_change
Feb 1 09:38:14 william-woodwards-computer lookupd[1878]: lookupd (version 369.6) starting - Fri Feb 1 09:38:14 2008
I now get this message when I try to start the VM (it does start though):
"Could not open /dev/vmnet8: No such file or directory
Virtual device Ethernet0 will start disconneced."
I am still unable to connect to the net in bridged mode. May I please have some help with this. I have had only 1 reply from someone at VMWare.
OK. So I reinstalled Fusion and tried the fix again and it didn't work. No internet for both NAT and bridged. May I have another solution please.
I am having the same problem. It appeared when I upgraded to version 1.1.1.
I don't see any replies from VMware staff here, is this forum not monitored by VMware? If so I'm in the wrong place! Anyway, I downgraded back to version 1.1.0 and that fixed the problem. So I think I'll wait until they fix all the bugz...
Exact same problem here on my MacBook. Again appeared after I upgraded
to 1.1.1. This community doesn't seem to be a productive way to to
report bugs. The issue appeared on another thread and both have been
marked "Answered" by virtue of the fact that someone recommended
downgrading to 1.1. Does anyone know a better way to report problems
such as this? This community just seems to be a bunch of users sharing
workarounds, with no connection to the product development team.