HOW TO: Setup mControl Clients (Vista) to talk to mControl Server (WHS)

[Ted Singh]

HOW TO: Setup mControl Clients (Vista) to talk to mControl Server (WHS)

A recommended system for mControl operation utilizes the mControl server on a dedicated machine, while access/operation of mControl happens from other machines on the network.



Further, we recommend the Windows Home Server (WHS) platform as the mControl server because of the following reasons:
(a) WHS is operational 24-7, allowing the mControl system to be used whenever required. This provides great flexibility in your macro operation - they can run anytime.
(b) WHS provides a great console for general administration - mControl Editor and mControl Manager have been designed for this console.
(c) WHS provides great remote access capability. Microsoft even provides a free DDNS service.
(d) Of course, WHS provides great storage and back-up features.

Many people are also using a Windows Media Center on their network - for which we provide a high-fidelity user interface.

This post provides guidelines on how to setup a mControl client/server system. The key steps are:
1. Install mControl on the Server Machine
2. Setup the Server Machine's Firewall (to allow the mControl server to send/receive messages with mControl clients)
3. Setup the Client Machine's Firewall (to allow the mControl client to send/receive messages with the mControl server)
4. Install mControl on the Client Machine
5. Allow Firewall exceptions for mControl Clients.

---

1. Install mControl on the Server Machine
Use the instructions provided in the "mControl Installation" section of the mControl v2 User Manual.

Please note, the installer and installation method differ if you installing on a Vista or XP machine, as compared to a WHS server machine.

2. Setup the Server Machine's Firewall
If you are using a Firewall (which is recommended), you will need to except the mControl Server - so that it can send/receive messages with mControl clients.



To do this, open your Firewall and select the "Exceptions" tab. Click on the "Programs ..." button and browse to mServer.exe. On your WHS machine, mServer.exe is located in the C:\Inetpub\wwwroot\mControl\server directory. On Vista/XP machines, mServer.exe is located in the C:\Program Files\Embedded Automation\mControl\server directory.

3. Setup the Client Machine's Firewall (to allow the mControl client to send/receive messages with the mControl server)
If you are using a Firewall (which is recommended), you will need to except a few ports used by the mControl clients - so that it can send/receive messages with mControl server.



Specifically, the following ports need to be excepted to allow proper operation:
- Port 29990 (TCP) - used by mControl’s internal web server and browser/media center clients
- Port 29994 (UDP) - used by mControl service to send messages (e.g. status msgs)
- Port 29995 (UDP) - used by mControl clients to send messages

4. Install mControl on the Client Machine
You don't need to install the full mControl on your client machines - use the mControl Client Installer to install the necessary software: http://www.embeddedautomation.com/fo...ead.php?t=1129



Near the end of the installation, the installer will provide a list of mControl servers to use - if you haven't done step 3, you may not see any mControl servers. Select the default server and close this selection box to accept the change:



5. Allow Firewall exceptions for mControl Clients
When you run the various mControl clients, your Firewall will ask if you would like to except the program/ports used by the client - select "Unblock" to allow the exception.

mControl Editor (mControlEditorForm.exe):


mControl Vista Media Center Client (Media Center Extensibility Host):