Versuch zwecklos
http://communities.vmware.com/thread/29 ... 5&tstart=0
Microsoft has changed the way networking drivers are handled in newer versions of Windows..
Previously these drivers would have a header that defined ARP/DHCP/Ethernet, so your card for example could emulate ethernet traffic. Now Windows states in their docs that the drivers are to show up as a raw IP. This change makes it so your card can not emulate an ethernet adapter, which is causing the issue you are seeing in Workstation.
und
Our developers have been working on your issue and have found that it is a change from Microsoft that has caused the problem.
"So it looks like the end story is that bridging is only doced to with with Ethernet devices, and this device isn't Ethernet so it can't work and isn't supported. It's regrettable this couldn't have been determined more readily before now but it would have helped to have access to the driver. The driver reports itself as a CDMA-based WWAN device (IF_TYPE_WWANPP2), with a media type of NdisMediumWirelessWan and a physical media type of NdisPhysicalMediumWirelessWan. Older versions of Windows had more of a requirement for ARP/DHCP/Ethernet so drivers either supported or had emulation for Ethernet but newer versions of Windows have gotten rid of these requirements and MSFT seems to be going in the direction of requiring that production drivers not support it either"
Due to Microsofts change, we will not be able to fix the issue you are having. Unfortunately you will need to adjust your setup to find a solution that will work for you.