Hi Slychiu,I have installed Parallels only Mac, and comfort is running. However, I don’t seem to be able to connect to the comfort system. I do not think it can see it.I am getting the message:Failed to connect to UCM - Please check the UCM connection settings.Are you able to help me?
Are you using eth03 or USB?
Does the Mac have 2 network adaptors? Comfort server manager looks for the 1st network adaptor and may not see the ETH03? If you can get the IP address by usng CS manager on a PC, and fix it, then use that same IP address on the Mac for ETH03
I am using ETH03 and I had it working on a windows based machine. I no longer have that machine hence using a macbook. I am using a static IP address in the comfigurator.
I am not sure what you mean by comfort looking for the 1st network adaptor.
I am still getting the same messages which is quite frustrating.
Your Parallels may block the Comfort server manager for some reason.
Do you remembetr the IP address that you setup and used before on the windows machibe. If you did not change it, it should still work even though you did not see the Comfort server manager IP address
For those running Windows 10 on Mac using Parallels, and cannot see ETH03 in Comfort Server Manager;Try changing the network mode from Shared to Bridged. This allows the IP addresss to be in the same network as the home network so CS Manager can talk to ETH03.
FWIW - I use a Macbook Air and iMac to access Comfort and run Comfigurator on Parrallels. I have found the key is working out what address and port Comfort is using to access the LAN. I suggest you get a Mac-based IP scanning tool (I use LanScan) that can accurately conform which IP address is being used. Run a scan and you should see Comfort in the list of LAN IP addresses being used. If you still have your old Windows PC also try to confirm the default access port has not changed (1001). Then fire up Parallels on the Mac, open Comfigurator and go to the Options / Settings / UCM Connection and make sure its set to LAN and that the IP address and port are correct. Parallels can be quirky accessing the LAN so also check that the network adapter is enabled under Windows AND Parallels.
Thanks Peter, yes, you only need CS manager to find out what IP address is ETH03 using. You dont need it after that.
The problem with Parallels is that it creates a Virtual Network adaptor with a different networkk eg 10.0.0.x from the LAN eg 192.168.0.x . CS Manager scans the the home LAN and does not see the ETH03. The solutio that I tested with mreneuk is to change the netwokr adaptor settings from Shared to Bridged. This causes the virtual machine to access the local network through one of the network adaptors, treating the virtualk machine as standalione computer in the local network. This allows CS Manager to find the ETH03