Parallels Desktop for Mac internal build 1966 is ready for download
|
|
|
Oct 28, 2006, 04:37 PM
|
|
|---|---|
mcg Senior Member Join: Apr 2006 Posts: 168 |
Wow, Shared Networking seems great. I can disconnect from the wired LAN, and when the Mac automatically switches to wireless, so does Parallels. And of course I can go in reverse, too. The Mac and the VM can communicate the same as before. So is there any reason whatsoever to use Host-Only Networking, unless you want to <i>prevent</i> the VM from having access to the Internet? In other words, is Shared Networking basically the equivalent of Host-Only plus a smarter Internet Connection Sharing system? Furthermore, now I have two Parallels adapters: Parallels Host-Guest Network (en2) and Parallels NAT (en3). Is that the way it's supposed to look? Should I delete the first one? Thanks guys, this is a great improvement for me. __________________ 15.4" MBP 2.4GHz Core 2 Duo, 4GB, OSX 10.4.9, WinXP/Debain guests |
|
Oct 28, 2006, 05:11 PM
|
|
|---|---|
PROSPEROUS Junior Member Join: Sep 2006 Posts: 5 |
Cut(copy) and Paste of double byte characters from OSX to XP on parallels. I am running XP home edition on a Apple Mac Mini. Upgrading from version 1940-en and everything works great except: Cut(copy) and Paste of double byte characters from OSX to XP on parallels does not work just as the previous versions. Hope that it will be fixed soon. However I have been enjoying the great software which I regularly use for my work. Thank you very much. Regards, |
|
Oct 30, 2006, 03:43 AM
|
||
|---|---|---|
 Andrew @ Parallels Parallels Team Join: Apr 2006 Posts: 1,557 |
Quote:
__________________ Best Regards, Andrew @ Parallels |
|
|
Oct 29, 2006, 05:16 AM
|
|
|---|---|
luz Member Join: Apr 2006 Posts: 87 |
How does "shared networking" work? Could someone please explain what the new "shared networking" is actually doing on the IP routing level? I have a setup of VMs with static IPs in a 10.x.x.x subnet which need to interact with each other, and I use Internet Sharing to give those VMs in the subnet access to the Mac's network connection. I'm comfortable with Internet Sharing because I could find out what it is exactly doing (it's a NAT router, implemented with the natd daemon, routing the host-only subnet to the Mac's internet connection. There's an extended man page on natd). The only problem with this is that Apple forgot to have natd restart when network location switches, so I have to manually restart it every time the external IP changes. This is annoying, but usable. It sounds that "shared networking" automatically adapts to changing external connections (and IPs), which would be a good thing. But without knowing how IP things work under the hood I'm reluctant to risk the current setup I technically understand for someting supposedly better, but currently a "blackbox". |
|
Oct 29, 2006, 07:41 AM
|
|
|---|---|
serv Parallels Team Join: Apr 2006 Posts: 247 |
luz, Shared Networking is implemented as NAT service (pvsnatd daemon) running on "Parallels NAT" (most frequently -- en3) network interface. The major benefits of using Shared Networking instead of Host-Only with Internet Sharing: * Simpler setup: no need to turn on OSX Internet Sharing manually. * Automatic adoption to network setup changes: you can switch Mac networking from wireless to Bluetooth modem and the guest OS will have new connections forwarded properly. * Compatibility with VPN software running on the Mac: Shared Networking will work through Mac PPTP connection. * Forwarding of NetBIOS name lookups and mDNS (Bonjour) name lookups (primarily printer discovery) from the guest to local network. However, if you're used to Host-Only with Internet Sharing mode and it completely satisfies your needs you may merely continue using it. mcg, You're right, Host-Only mode provides an isolated network for your VMs. It may be necessary in some cases. And yes, you can disable Host-Only in OSX System Preferences/Network, but why bother?. Note that if you delete en2 configuration completely it will be recovered next time you install or upgrade Parallels Desktop. |
|
Oct 29, 2006, 05:23 PM
|
|
|---|---|
tfcm Junior Member Join: Oct 2006 Posts: 3 |
I Love You Guys!!!! I can't tell you how much I love you guys right now. I might just bring pizza by if I am in the area one day. Being able to use my Verizon ExpressCard on my MacBookPro and Virtualization ROCKS!!!!! Sorry if I sound over the top, but you have just made my life (and business) sooooo much better. Kurt The Family Computer Man Frederick, MD |
|
Oct 31, 2006, 12:49 PM
|
||
|---|---|---|
luz Member Join: Apr 2006 Posts: 87 |
Hello "serv", Many thanks for the explanation for "shared networking". :) :) Quote:
My only question: Would "shared networking" work with a fully static setup (static IP configuration in the guests, and a fixed 10.x.x.x IP assignment for en3)? The only dynamic IP I have is the address on the physical interface to the outside (Ethernet, AirPort, Modem..). Another techie question: can pvsnatd act as DNS forwarder, so that I can set the en3 IP as gateway address AND as DNS address in static guest setups? |
|
|
Oct 29, 2006, 08:07 PM
|
|
|---|---|
tangential Member Join: Apr 2006 Posts: 48 |
I have the same problem (Shared Networking shows up, but is greyed out.) I shutdown all of my VMs, installed the build and rebooted. Shared networking is still greyed out. Any advice? (This is on a MacBook Pro with 2 gig ram.) |
|
Oct 30, 2006, 03:49 AM
|
||
|---|---|---|
Andrew @ Parallels Parallels Team Join: Apr 2006 Posts: 1,557 |
Quote:
__________________ Best Regards, Andrew @ Parallels |
|
|
Oct 30, 2006, 03:56 AM
|
|
|---|---|
michil Junior Member Join: Sep 2006 Posts: 10 |
Still missing full USB Support Hello, Parallels is running perfectly for me but I still m issing full USB support. I have an Data Recorder device connecting via USB. Till 1940 version it was displayed as Data Recording Device in USB device list, but I wasn't able to connect it to the VM (well known error message "device is in use ....wait for ......."). With this new version the device is shown as "compound device" and I'm still not able to connect it to the VM. Kind regards Michael |
|
Oct 30, 2006, 04:03 AM
|
|
|---|---|
Jerry Member Join: May 2006 Posts: 75 |
Just in case someone else has the 'Shared Networking' option grayed out: - I tried the mac restart as per Andrew's suggestion, but it still stayed grayed out. - When I opened the Mac Network prefs, the mac came up with a prompt that a new port (en3) had been detected, and to check its config and click apply to activate. - After doing that. 'Shared networking was still grayed out, so I quit Parallels & started it back up again, and viola, it can now be selected! |
|
Oct 31, 2006, 03:46 PM
|
|||
|---|---|---|---|
tangential Member Join: Apr 2006 Posts: 48 |
Help, Still looking for shared folders..... Quote:
Quote:
I notice that I have another adapter now in ifconfig -a. I gained the en4 adapter, but it is not configured. Here is the output of an ifconfig -a: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 1500 inet6 fe80::216:cbff:fe8b:d06b%en0 prefixlen 64 scopeid 0x4 inet 10.80.8.100 netmask 0xffffff00 broadcast 10.80.8.255 ether 00:16:cb:8b:d0:6b media: autoselect (100baseTX <full-duplex,flow-control>) status: active supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 1500 ether 00:14:51:ec:f6:53 media: autoselect (<unknown type>) status: inactive supported media: autoselect wlt1: flags=41<UP,RUNNING> mtu 1500 fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 2030 lladdr 00:16:cb:ff:fe:4a:ec:84 media: autoselect <full-duplex> status: inactive supported media: autoselect <full-duplex> en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMP LEX,MULTICAST> mtu 1500 inet6 fe80::201:23ff:fe45:6789%en2 prefixlen 64 scopeid 0x8 inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:01:23:45:67:89 media: autoselect status: active supported media: autoselect en4: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 ether 00:10:32:54:76:98 media: <unknown type> supported media: autoselect lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 1500 inet6 fe80::216:cbff:fe8b:d06b%en0 prefixlen 64 scopeid 0x4 inet 10.80.8.100 netmask 0xffffff00 broadcast 10.80.8.255 ether 00:16:cb:8b:d0:6b media: autoselect (100baseTX <full-duplex,flow-control>) status: active supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 1500 ether 00:14:51:ec:f6:53 media: autoselect (<unknown type>) status: inactive supported media: autoselect wlt1: flags=41<UP,RUNNING> mtu 1500 fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 2030 lladdr 00:16:cb:ff:fe:4a:ec:84 media: autoselect <full-duplex> status: inactive supported media: autoselect <full-duplex> en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMP LEX,MULTICAST> mtu 1500 inet6 fe80::201:23ff:fe45:6789%en2 prefixlen 64 scopeid 0x8 inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:01:23:45:67:89 media: autoselect status: active supported media: autoselect en4: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 ether 00:10:32:54:76:98 media: <unknown type> supported media: autoselect What now? Thanks, John |
||
|
Oct 31, 2006, 07:30 PM
|
|
|---|---|
scottdelap Junior Member Join: Apr 2006 Posts: 11 |
I've rebooted. Tried uninstalling and reinstalling and rebooting again. The shared networking option is still grayed out. Suggestions. |
|
Oct 28, 2006, 11:53 PM
|
|
|---|---|
moosa@ismail.com Junior Member Join: Jun 2006 Posts: 4 |
Thanks... in Vista RC2 got this "critical error" message when trying to run a game..."Failed to create Directx device" Not serious just reporting... |
|
Oct 29, 2006, 09:58 PM
|
|
|---|---|
peterwor Senior Member Join: Apr 2006 Posts: 142 |
Shared Networking broken for me in 1966... I love the sound of this new shared networking but for me its broken. I have a MacBook Pro and I'm running on a wireless router with an address of 192.168.1.2 and my OSX machine grabs an IP in the 192.168.1.10X range. I see that the NAT adapter is on the 10.x.x.x network. This appears NOT to work for me. Are you telling me that I have to redo my router to use the 10.x.x.x range? Is something else broekn or do I need to do anything else to fix this? Help? Peter |
|
Oct 29, 2006, 10:23 PM
|
|
|---|---|
mcg Senior Member Join: Apr 2006 Posts: 168 |
You shouldn't have to re-do anything at all on your router. The NAT that Parallels creates in the 10.x.x.x range is completely contained within your MacBook. All of the network traffic from all VM guests, along with your Mac OSX traffic, is piped through your single 192.168.1.10x address. So it sounds like something else is going wrong here. Whatever you do, DON'T change your router. Did you ever get your setup work with Host-Only Networking and Internet Connection Sharing? If so, it should work to edit your VM settings, change the adapter from Host-Only Networking to Shared Networking, and then restart the VM. Try going back to host-only networking+ICS first, get that working again. __________________ 15.4" MBP 2.4GHz Core 2 Duo, 4GB, OSX 10.4.9, WinXP/Debain guests |
|
Oct 29, 2006, 11:02 PM
|
|
|---|---|
alkalifly Senior Member Join: Apr 2006 Posts: 140 |
Shared networking fixes CiscoVPN/natd incompatibilities!! Build 1966 has fixed what had been my number one problem using Parallels, and I could not be happier about it!! :D I need to connect my Mac to my school's VPN service with the Cisco client, which kills the Mac's built in NAT service (natd). This is not a problem with Parallels itself, but rather a problem with the CiscoVPN and/or natd, which I don't really know much about. Parallels has now managed to free their users of this problem by making their own NAT server that plays nice with the CIsco VPN service. I used to have to choose between having the Mac on the VPN or having the VM be able to connect to the Internet (as opposed to just the host machine). Now, with Shared Networking, everything "just works" :) :) :) I can go connect and disconnect the Mac from the Cisco VPN client without causing so much as a hiccup in the VM's connection. Way to go, Parallels!!! __________________ MacBook Pro 2.0 GHz, 2 GB RAM, OS 10.5.4, Parallels Build 5608 |
« Previous Thread | Next Thread »
| Search this thread | Forum jump |
|---|---|
| Thread tools | Display modes |
|---|---|
|
Hybrid Mode
|