Re: Vista x64 and VMware
Re: Vista x64 and VMware
Kerry Brown wrote:
> "Hayabusa" <obscenum@gmail.com> wrote in message
> news:O0o8AwGWIHA.1212@TK2MSFTNGP05.phx.gbl...
>> Kerry Brown wrote:
>>> "RayG" <noone@nowhere.invalid.com> wrote in message
>>> news:503544FC-6DC7-449C-A5A2-55E46ADA6EC7@microsoft.com...
>>>> Kerry Brown wrote:
>>>>> "RayG" <noone@nowhere.invalid.com> wrote in message
>>>>> news:2CDDEDF9-8A0D-4235-93B2-91CDC692AD7E@microsoft.com...
>>>>>> Kerry Brown wrote:
>>>>>>>> No, No malware and not connected to a domain
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> In the Network and Sharing Center is the network Public,
>>>>>>> Private, or Domain? If it's Public or Domain there's your
>>>>>>> problem. If it's Private then try running secpol.msc. Change
>>>>>>> all of the settings in the Private profile to Not configured
>>>>>>> then reboot. If this doesn't fix it then it is very likely you
>>>>>>> do have some malware installed.
>>>>>>
>>>>>> Kerry,
>>>>>>
>>>>>> Ah! I think you may have hit the nail on the head.
>>>>>>
>>>>>> I have VMware installed in this system and it has its IP
>>>>>> addresses in the "Public" space and no matter what I try to do I
>>>>>> cannot get them to stay in the "Private" space. Is there a trick
>>>>>> in Vista that I am missing? Network Properties shows
>>>>>>
>>>>>> 192.168.10 - PC
>>>>>> 192.168.102 - VMware
>>>>>> 192.169.109 - VMware
>>>>>>
>>>>>> and my ethernet adapter is listed in both private and public.
>>>>>>
>>>>>
>>>>>
>>>>> Is Vista running in a virtual machine?
>>>>
>>>> No I have Linux and Solaris in the VM's Vist is the main OS that
>>>> VMWare runs on.
>>>>
>>>
>>>
>>> What happens if you shut down VMWare?
>>>
>>> I don't have a lot of experience with VMWare in Vista. I tried it
>>> with Vista x64 but because the VMWare driver is not signed it got
>>> to be a pain pressing F8 on every boot up to allow the unsigned
>>> driver. I switched to VPC 2007. When I was testing VMWare I didn't
>>> see this problem so it may be something in the way you have
>>> configured networking in the VM's.
>> Not sure what VMware product you refer to but I got VMware
>> Workstation 6.0.2 build-59824 running on Vista Ultimate x64, no need to
>> press F8
>> on boot here!
>> 
>>
>
>
> I didn't see it was VMWare Workstation until later. I was using VMWare
> Server.
Ok I think I have now sorted my problem.
In order to get back to the basix mode of operation you have to run wf.msc
and set all three types (Domain, Public, Private) to unconfigured. When this
is done the basic functionality is restored
What I did to work through this was:
I uninstalled any other firewall/AV S/W
I uninstalled VMWare Workstation
The issue remained the same so it was not VMWare as I would have expected it
to reverse what it did. It was also not the other Firewall AV S/W as that
could not handle the advanced configuration.
Having done installs/uninstalls several times to prove one thing or another
what I also discovered was that my ethernet adapter had associated with it a
169 IP address that was causing it to appear in both public and private
network domains. I looked in all the places I could think of but could not
locate that item. So what I did next was to delete the ethernet card ftom
device manager and reboot letting the system discover the hardware again.
This at least cleared up the 169 address and the ethernet adapter is now in
the private space only. I then installed VMWare nothing changed apart from
the VMWare adapters going into the public space. I then did the same with
other firwall and A/V S/W and again nothing changed.
So whilst I have resolved my problem I have no idea how it got into that
state in the first place.
--
Regards
Ray