Hi I experiencing major trouble after upgrading to version 6. i use Parallels for testing and lab, mostly testing deployment of windows 7. On my parallels i run: Server 2008 with active directory in one virtual machine Windows 7 in an other virtual machine Windows PE in a third virtual machine all virtual machines are connected on a shared netwrok This worked very well in ver 5 of parallels and it works in virtual box (which i is forced to use now because of this problem) and fusion. The thing is that i cant get the the win7 machine to join the ad, i cant get the name resolution to work. If i turn of the Ipv6 support och both the server and win7 it works. On Windows PE i cant turn of the ipv6 support so i still cant use parallels as a virtual solution. This worked in ver 5 of parallels and it stopped worked the same moment i upgraded to ver 6. The fact that it works when i turn of ipv6 on my windows machines and the fact that it works in virtual box (without turning of ipv6) lead me to think that it something with the Ipv6 support in parallels ver 6.
(sorry, I deleted by mistake my prev post, it was big and I'm just restoring the key points): A couple of questions: - Are you using Shared networking? - If not, the is VM bridged to WiFi network? Or to wired ethernet?
This could be either 1) an issue with checksumming while transfer between Virtual Machines. It should be fixed in build 11990 (build announcement is here http://forum.parallels.com/showthread.php?t=106638) It is possible to check whether it is this issue by specifying the boot-flag for usual windows (Non PE) VMs "devices.net.force_adapter_type=rtl" - see http://kb.parallels.com/en/9041. Note: it may be needed to reinstall reinstall Parallels Tools 2) Some general (not known so far) issue with IPv6 in Parallels Shared Networking. Unfortunately I've just discovered that it is impossible to turn off IPv6 for ShareddNetworkig, so we in parallels should check this locally if solution 1 doesn't help
one more thing: I just understood that in your case IPv6 DHCP provided by Parallels is not required at all, so for testing purposes it is possible to kill the parallels shared networking process by starting /Application/Utilities/Terminal and executing in it command "sudo killall prl_naptd". PS: To start it back - execute "sudo launchctl start com.parallels.vm.prl_naptd" . This process serves as gateway and DHCP (both v4 and v6)
I have done som further testing Environment Two VM:s on the same network. One VM with Windows server 2008 (active directory, DNS, DHCP) and one VM with Windows 7 (DHCP client). Test: Join the Windows 7 VM to the active directory on the server 2008 VM Testcase 1 (shared network, Parallels dhcp turned off) Result: Fail Comment: The windows 7 client can't find the active directory. It is possible to ping the server on netbios name (ping servername), but its not possible to ping FQDN (ping servername.domain.com) Workaround: Disable Ipv6 support on both server and windows 7. Doing this, the windows 7 client can join the active directory. It is possible to ping both on server name and FQDN Testcase2 (host only network, Parallels dhcp turned off) Result: Pass Comment: This worked as its suppose to work. No problems. However, using host only network will stop access to the outside world, eg Internet. Workaround: To access internet i have installed a Vyatta router (NAT and DNS forwarding) on a third VM. It has one nic on Host only network and the other nic on shared network. The shared network has DHCP turned on. This works, but the downside it that an extra VM is required. I will test the "killall prl_naptd" later today. //Micael Ã…man
Thank you, the case is clear now.. there is no need in killall prl_naptd test since HostOnly works. The problem is DHCPv6 which is not possible to turn off. (sorry, cannot provide estimation when this will be fixed) It could be possible to setup routing on the Win7 VM with AD without third VM...
