Thanks for the suggestion. Stopped VM, Fusion. Ran sudo command in terminal. Started Fusion, VM. Unfortunatle same problem as before. When Windows starts up, the bar graph (for wifi) shows up as an icon at the bottom of the screen, it tries connecting -- or is busy anyway -- and then changes to an icon showing a screen with ethernet cable with a red X, with the error that no adapter was found.

Hi, I_C, thanks for the suggsetions. Ran the ps-aux and saw the four dhcp tasks. Have tried bridged, didn't change anything.

The only device that had driver problems was the ethernet controller (no driver). It was not identified (just generic).

At this point I created a new VM that did not point to boot camp, but used the iso to create a new VM. It HAS internet connectivity. I checked the ethernet controller, it was an Intel MT 100/1000 pro. I VMed back to boot camp. Identified ethernet controller as Intel pro MT 100/1000. Could not find driver in system 32, but did find it elsewhere and used it as driver for ethernet device (this process copied driver to system 32). Alas, even after restarting with the driver-loaded ethernet device, it made no difference.

I noticed on bootcamp proper, the icon for wireless is a bar graph. On VM it is a PC with an ethernet plug. On bootcamp VM, it starts trying to connect with teh bar graph, but when it fails, it switches over to the pc/ethernet plug icon (with a red x). Maybe there is an incompatability in this area with bootcamp trying to use different software from VM for the purposes of wifi?

Thanks for your suggestions. Since I have a working VM, I could walk away from thi sproblem, but I think it is worthwhile for other users to resolve this.

I must say that the VM of boot camp REALLY SUCKS. It is MUCH slower than booting into boot camp. The VM machine (non boot camp) works great.