Citect 7.2 sp5

[Smm206]

Hello

I am using Citect version 7.2 service pack 5 and Windows 7.

I have created a project. Currently, the project on the server is running without any issues. On the client side within the web browser, there are no problems and it runs in local mode. By local mode, I mean the local mode of the internal network. However, now I want to use two modems with public IPs as a bridge between these two systems. I have made the settings and set the modem on the server side to DMZ mode. The network is established and the two computers, the server and the client, can see each other. But when I run the project through the browser client, the project files are loaded and the project is executed. However, live data is not received and it operates offline. And after a few moments, it gives a hardware lock error. The firewall is turned off in Windows and on the modems. All ports are open.

I really don't know where the problem lies because the project works in local network mode without any special settings.

Please advise if someone has experience in this area.

[olivier_vallee]

Hi @Smm206 ,

This is a very interesting scenario. I'd suggest the following as a start:

1. Test you can ping IP address from both ends.

2. Telnet from client to server side on specific ports (2080, 2082, 2084, 2085 are default ports for Citect)

3. Use Wireshark in local, then try in the modem setup and see if any obvious differences with packet traffic.

4. Make sure to use IP Address in your project, as name resolution might not work over this type of network.

Also, see the Web Client help here:

https://gcsresource.aveva.com/plantscada/WebHelp/vijeo720/default.htm#Using_the_Web_Client.html

Wishing you the best of luck getting this working.

Kind regards

Olivier

[Smm206]

Hello

Thank you very much for your response.

I have rechecked these issues. The server modem is set to DMZ mode, and I have also disabled the firewalls on both the modem and the server to ensure a completely open path. Both the server and client systems can ping each other. I can even access the server via Remote Desktop from the client system, and I have shared a folder between the two systems.

Interestingly, when I make changes to the graphical pages in the server's Citect project, refreshing the project page in the client browser shows the latest graphical updates. However, no live data is displayed, and after a short while, a hardware lock error appears.

I have installed Telnet Client on the client side and Telnet Server on the server side. When I run:
```
telnet (Server IP)
```
from the client, the screen goes black, indicating that the connection is OK. The same happens for ports 2082 and 2085. However, for ports 2080 and 2084, I get the following error, even though the settings are the same and all firewalls are off:
```
Connecting To (Server IP)...Could not open connection to the host, on port 2080: Connect failed
```
I have even restarted the Telnet service on the server.

In a local network setting, there are no errors (software or hardware lock) between the server and client. When connected locally to the server, I enter the IP address (which is within the server's network range) in the browser without any issues. But when I try to do this through the modem network, I have to enter the modem's SIM card IP (which is in DMZ mode and port-forwarded to the server's local IP). I wonder if the issue is that the Citect software itself cannot establish a connection with the server, even though the network connection is fine.

Is there a specific configuration needed in Citect.ini? Because it works perfectly with the same settings in a local setup between the server and client. Or is there a particular setting required in IIS? Since the latest project update downloads on the client side, but no live data is displayed.

I apologize for the lengthy explanation; I really need to resolve this issue.

[olivier_vallee]

Hi @Smm206,

I'd recommend checking on the Server side, to make sure the expected ports are open. E.g. if running a RATIO system, make sure ports for Report, Alarm, Trend and IO are each open and in listening state (see info on "netstat" command on Google for help to do it).

I definitely think this is a networking issue, where the client process, doesn't know how to communicate with the Server as definied in the the project.

Please see this section of the help for informaiton on Address Forwarding:

https://gcsresource.aveva.com/plantscada/WebHelp/vijeo720/default.htm#../Subsystems/ParametersVijeoH...

I believe you need to configure this on the Citect.ini file on the Client side, and define the appropriate IP/Port that will allow any communications to go through to the Server side.

Let me know how you go.

Kind regards

Olivier

[Smm206]

 

Hello,

Thank you for your response.

I have checked everything. In the above picture, I have two scenarios:

1. In Scenario 1, the project works perfectly fine in the web client mode and communicates with the server effortlessly, without any additional configurations on the server, client, IIS, or modem.

2. However, in Scenario 2, when the communication between the client and server happens through two modems, unfortunately, the connection between the client and server becomes incomplete. The project downloads on the client-side, but it fails to establish a connection with the server.

Here are the steps I have taken:

- All firewalls on the server, client, and both modems are turned off.
- There are no restrictions between the client and server.
- I tested with Remote Desktop and shared folders between both systems, and there were no issues.
- I can ping between the two systems.
- The default ports for Citect are open, even with the firewalls turned off.

The only issue is the live communication between the client and server.

Please provide a solution to resolve this problem based on the picture.

Thank you.

[olivier_vallee]

Hi @Smm206,

It is difficult for me to suggest the solution, without deeper understanding of the network routing between the two sides. When you ping 192.168.8.3 from the client, you get a response? Could you also try TraceRT command from command prompt, to see what hops the route takes?

I've not personally setup a system like this, but if there is any Network Address or Port mapping that is going on, the Address Forwarding citect.ini parameter should help. But you would need to better understand the end IP and Port, that the Client should request, and set the parameters accordingly.

Finally, further clarity may be gained by running Wireshark on the client side. To understand what packets are being sent, and what is happening (e.g. is a connection being made or no ACKs coming back?).

I assume you also have 192.168.8.1 set as the Default Gateway on the client?

Kind regards

Olivier

[Smm206]

Hello,

Thank you for your response.

In the local mode, the project runs without any issues by entering the IP address defined in the server project.

In the public network mode, I have placed the server-side modem in DMZ mode, so the server computer is identified on the public network with the public IP of the SIM card.

On the client computer browser in local mode, I enter the IP 192.168.8.3, and since the client computer's IP is in the same range as the server's IP, the connection is established easily.

However, in the public network mode, to access the server computer, I have to enter the public modem's IP on the server side. Due to the DMZ mode on the server-side modem, all traffic is directed to IP 192.168.8.3.

I feel that the problem is here because I am entering an IP from a different range, and while the IIS service sends the latest project update, the internal project source on the client side still works with IP 192.168.8.3, whereas the requests enter the server system via IP 110.50.30.9.

Perhaps I need to configure some settings in the IIS service on the server side or use the URLREWRITE service to redirect the requests to the address 192.168.8.3?

Please provide an example for address forwarding.

[olivier_vallee]

Hi @Smm206,

As previously communicated, you would need to define address forwarding parameters in the citect.ini on the Client side, with the following format:

[AddressForwarding]
<Cluster>.<ServerName>=<ipaddress>:<port>

So assuming you have the following defined in your project:
Cluster Name: Cluster1

I/O Server Name: IOServer1

Alarm Server Name: AlarmServer1

Report Server Name: ReportServer1

Trend Server Name: TrendServer1

You could try the following setting in your citect.ini on the client:

[AddressForwarding]
Cluster1.IOServer1=110.50.30.9:2082

Cluster1.AlarmServer1=110.50.30.9:2080

Cluster1.ReportServer1=110.50.30.9:2084

Cluster1.TrendServer1=110.50.30.9:2085

You could also try defining the machine name in the project configuraiton, for the network address (instead of IP Address). Then use an LMHOST file to direct to the IP 110.50.30.9.

Please also give Wireshark a try, it will help you understand what is happening at the packet level.

Kind regards

Olivier