Implement middleware server and proxy communication for Windows workgroups
- Last UpdatedOct 18, 2024
- 1 minute read
To make user account setup easier for small systems (for example, for demo or proof-of-concept systems), MES supports using Windows Workgroups instead of Active Directory to manage user accounts. Refer to the following subtopics to ensure proper communication between the MES middleware and client middleware proxies when using Workgroups.
Adding Client Node User Accounts to the MES Middleware Server Node
If your network is using Windows Workgroups to manage user accounts rather than an Active Directory domain controller, MES user accounts on the client nodes must also be added to the node where the MES Middleware Server is located. This will allow those MES users on the client nodes to perform operations through the MES middleware.
You can add users to the MES Middleware Server node using the Computer Management applet, which can be accessed from the Administrative Tools applet in the Control Panel. In the Computer Management applet, go to System Tools, Local Users and Groups, and then Users or Groups. You can right-click Users or Groups and then select Help to get more information on adding a user account and assigning it to a group.
After adding the client user accounts to the Middleware Server node, restart all affected nodes.
Reinstating TCP Communications Between Nodes
If TCP is being used for middleware-to-middleware proxy communication and the TCP connection is lost between a client node and the Middleware Server node, try restarting both nodes. This should reinstate the TCP connection.