An IQ Client computer, running IQ for Windows, cannot communicate with an IQ Net Server computer.

Systems Technology Note

Tech Note: 001rev1

 

Products: IQ for Windows

               IQ Net

 

Software: IQ for Windows

                IQ Net

Issue:

An IQ Client computer cannot communicate with an IQ Net Server computer.

 

Resolutions:

*Both the IQ Client and IQ Net Server computers should be running the same version of software.

*Both the client and the host computers should have valid network IP address assigned to them.

*IQ Net Software should only be run on the computer(s) that are connected to the IQ system Interfaces not the IQ Client only computers.

*Client computers need to configure IQ for Windows for Client/Server operations.

*The Client computer’s IQ for Windows “Server Manager” may need to use the IP address of the IQ Net Server instead of the IQ Net Server’s name.

 

To configure Client/Server operation in IQ for Windows for the Client computer:

 

 

1)      Open the Setup|Communications window.

2)      Select the “Servers” button this opens the Server Manager window and displays a list of available IQNet Server computers.

3)      Use “Query” to update the IQ Net Server listing.

4)      Select the IQ Net Server computers the Client is to control/monitor.

5)      Close the window

6)      Select the check box to “Enable” IQ Net operations.

7)      Close the Server Manager.

8)      If the Client computer is not being used as an IQ Net Server also deselect the "Enable" box for "Local RS-232" This will keep the software from trying to perform a local Component Discover/Roll Call.

9)      Select OK to close the Communication Settings window and then select "Close Dataframe"

10)   "Save changes to Untitled?": Select save if you wish to save changes to the Dataframe file or location of the saved file.

11)   Select "Yes" to "Perform Roll Call?"

12)   During the Component Discovery/Roll Call all the IQ Net Servers that were selected “Active” in the Server Manager and the component(s) that are associated with it will be displayed.

13)   After Roll Call the IQ components associated with the selected IQ Net servers should appear in the IQ for Windows “Workplace” screen.

14)   Each of the Client computers will need to have the IP address entered for each of the IQ Net Servers it is to be able to Monitor/Control.

The Server Manager uses a broadcast discovery packet, to resolves the IQ Net Servers on the local LAN by their name and IP address. Being a broadcast packet it is by nature blocked by network routers and the Server Manager will not find any IQ Net Servers on the other side of a Router.

If there is a Router separating the IQ Client and Server computers:

 

1) Make sure all the servers and clients are running the same version of software.

2) Start all the IQ Net server computer(s)

3) Start IQ for Windows software on a Client computer.

a)   In the Setup|Communication window select the “Enable” box for IQ Net and then press the "Servers" button to open the Server Manager.

b)   The Server Manager will show all IQ Net servers that are on the same side of a network router as the Client computer.

c)    To access IQ Net Servers on the other side of a network router: select the "Add" button and enter the IP address of an IQnet Server computer into the "Name" column only.

  (Perform this step for each IQ Net Server that is to be seen by the Client)

d)    Select the "Active" box .

e)    Close the Server Manager

f)     If the client is not also being used as a IQ Net server deselect the "Enable" box for "Local RS-232" This will keep the software from trying to perform a local Component Discover/Roll Call.

g)    Select OK to close the Communication Settings window and then select "Close Dataframe"

h)    "Save changes to Untitled?": Select this if you wish to save changes to the Dataframe file or location of the saved file.

i)    Select "Yes" to "Perform Roll Call?"

j)    During the Component Discovery/Roll Call you will see all IQnet Servers that were selected Active in the Server Manager of that Client and the component(s) that are associated with it.

k)      After Roll Call the IQ components associated with the added IQ Net server should appear in the Workplace screen.

l)        Each Client computer would need to have this done, in it’s IQ for Windows software, for each of the IQ Net Servers it was to Monitor/Control.

Optional:

There is a way force the IQ for Windows Client software to recognize the IQ Net Server by the computer’s network name.

           

            1)      Open the “hosts” file located in the C:/windows/system32/drivers/etc” directory in a text editor, such as “Notepad”.

2)      Scroll down to the end of the text and start a new line.

3)      Type in the IP address of the IQ Net Server computer then Hit the tab key

4)      On the same line enter the IQ Net server’s computer name.

 

Note: The Name of the IQ Net Server computer can be verified on the IQ Net Server by selecting:

                           Start|Control Panel|System|Computer Name

 

                5)      Save the file.

6)      Each Client computer would need to have this entry done for each IQ net Server it was to Monitor/Control.

 

Note: The network “ PING ” command can be used on the Client Computer to check for communication with the Server Computer. If there is no response than there is a network issue. If the Server computer responds to a Ping and the IQ for Windows software on the Client still cannot see the Server than there is probably a Name to IP resolution issue in finding the IQ Net Server.