Keyboard Shortcuts
ctrl + shift + ? :
Показати всі комбінації клавіш
ctrl + g :
Не доступний для безкоштовних груп.
ctrl + shift + f :
Знайти
ctrl + / :
Сповіщення
esc to dismiss
Лайки
Пошук
Toolbox on a Macbook Pro via Parallels
|
Has anyone been able to successfully run Toolbox on a Macbook Pro via Parallels?
I know this question has been asked in a previous thread from a few years ago, but I was hoping there would be some new info/success stories available.
Toolbox opens just fine and I can see all of the Crestron devices in the system. However, I can't connect to anything, be it through Device Discovery or the Address Book. I've tried every setting suggestion in the old thread and it still won't allow me to connect to any devices. Is this a settings issue on the Macbook Pro side? Or is this a Parallels-Windows issue that hasn't/can't been solved? If so, is anyone using a differnt software-VM combo that will work on my Macbook Pro? Heres what I'm using:
2018 Macbook Pro 15"
OS: Ventura 13.7.1
Processor: 2.9 GHz 6-Core Intel Core i9 processor
Parallels with Windows 10 VM
Thank you in advance for any help or solutions!
|
|
Chris, I have been using Toolbox on my Macbook Pro via VMWare Fusion Player for about 2 years now. It works great, as long as I don't try to connect via USB cable directly to the device. VMWare does not support the driver needed for the USB cable to communicate to the device.
I just saw that Workstation Player and Fusion Player have been discontinued, but VMWare Fusion Pro is free for personal use. It's available from Broadcom. You would need to re-install your Windows, though. |
|
Have been running Parallels on all machines running back to 2014 after I was tired of getting the blue screens of death on Dell computers. Haven’t had any issues other than on my 21 32GB M1 16” MBP with just USB devices. Some devices work no issues and others don’t. Haven’t had to do anything particular to get it all to work.
Pat M
From:
"crestron@groups.io" <crestron@groups.io> on behalf of "Chris Armenta via groups.io" <info@...>
Has anyone been able to successfully run Toolbox on a Macbook Pro via Parallels?
I know this question has been asked in a previous thread from a few years ago, but I was hoping there would be some new info/success stories available. Toolbox opens just fine and I can see all of the Crestron devices in the system. However, I can't connect to anything, be it through Device Discovery or the Address Book. I've tried every setting suggestion in the old thread and it still won't allow me to connect to any devices. Is this a settings issue on the Macbook Pro side? Or is this a Parallels-Windows issue that hasn't/can't been solved? If so, is anyone using a differnt software-VM combo that will work on my Macbook Pro? Heres what I'm using:
2018 Macbook Pro 15" OS: Ventura 13.7.1 Processor: 2.9 GHz 6-Core Intel Core i9 processor Parallels with Windows 10 VM
Thank you in advance for any help or solutions!
|
|
The operative issue here is how you connect to the network. Also, WiFi and Ethernet have two different stories and two different solutions. For the purposes of this message, caution for similar terminology: "MAC" does not mean the same thing as "MacBook". "MAC address" is the unique 12-hex-digit number that is burned into the network adapter at manufacture, and applies to all network adapters, whether WiFi/Ethernet/MacOS/Windows. Anyway -- If you are connecting via WiFi, you are going to struggle to get a Parallels VM to connect to the network without restriction, unless you 1) use an external USB WiFi adapter and 2) let Windows operate it directly by assigning the USB port directly to the VM. This is because your Windows virtual machine is normally going to get a private IP address using NAT, behind the MacBook (as though the MacBook is a router) and it won't have its own IP address on the target network, nor direct access to scan it. There is no way around this, when sharing the MacBook's WiFi adapter. On Ethernet, it's conceptually possible for one Ethernet connection to present multiple hosts (each with their own MAC address) to the network...on WiFi, this is not allowed, each WiFi adapter makes its own connection and gets one IP associated with its single MAC address. So to reiterate the solution, you'd use a second WiFi adapter over USB, which has a separate MAC address, and let Windows drive this second WiFi adapter directly, by assigning the USB port to the virtual machine. The MacBook won't know anything about it, other than that it is just a USB device that is forwarded into the VM. If it's Ethernet, there's less of a struggle, because you are allowed to configure the virtual machine to be "bridged" to the system ethernet connection and have the MacBook present two MAC addresses to the network simultaneously. Bridging is not the default network configuration for Parallels, you must manually configure that in Parallels options. But when successful, you'll have two IP addresses on the local network...one for Mac OS, the other for Windows. Mike On Thu, Nov 14, 2024 at 1:05 PM Chris Armenta via groups.io <info=asounddecisionla.com@groups.io> wrote:
|
|
Oh, right on, great to know. I either missed that possibility completely, or gave up before that became an option. My long term favored solution has just been to dedicate a Windows machine for running Crestron software, and then control it on the MacBook from remote desktop (such as with Jump Desktop or another app that makes remoting into Windows as pleasant as possible). Each thing I "must" use Windows for, generally gets its own dedicated laptop, or one of those cheap fanless mini-PC's you can get on Amazon with Windows pre-installed. Mike Mike, you can run the wifi in bridged mode. I did this for over 10 years on several MacBook's. The only system I ever had an issue with is Ruckus. By default they prevent this. A simple command on the ZD or Master AP and it will work. |
|
I have been running Crestron software on Mac computers since 1990 using a variety on means. I've been using Parallels since Intel Macs and am now running it on an M3 MacBook Pro. USB is problematic, but networking over WiFi or Ethernet works fine, but there are some cavitates. As mentioned previously the default is Shared Networking where Windows has a private address using NAT. However, if you select Bridged Network, Windows will obtain an address on the same subnet as the Mac, either via WiFi or Ethernet, and the menu allows you to select from which or Default, so it is possible to use say WiFi for Wan connectivity and Ethernet for whatever you doing with Toolbox.
However, in all the above options Windows will default to DHCP. So, if you want to discover devices on a particular subnet, especially if you don't have a DHCP server, you will want to dive into Windows and set a static IP address on the same subnet as the static address that you've set on your Ethernet adaptor (when you are in Bridged Network using an Ethernet adaptor). Don't forget to set it back to DHCP when you have finished or you'll wonder why you can connect to anything.
As an aside, I've never has so much freedom with the M3 Mac, I can work all day on Crestron stuff without having to worry about know much battery is left, phenomenal.
Lindsay |
Chris Armenta
Повідомлення
Більше
Додаткові параметри
Більше
to navigate to use esc to dismiss