I'm trying to figure out how to setup a Unified runtime PC which is connected to the shopfloor and the machine network. The PC has 2 network cards.

Machine network range: 192.168.10.x (Wincc At 192.168.10.122)

Shopfloor network range: 192.168.1.x (Wincc at 192.168.1.9)

Everything is working like I want only I would like to access the webrowser from the shopfloor and the machine network. And it seems that I have to chose if I want to have it working from machine network or shopfloor.

If I confirre my Wincc Unified with "Wincc Unified Configuration" on "adressing the website and identity provider" from the shopfloor IP (192.168.1.9) then it's working when I'm connected to the shopfloor. If I change this to the machine IP its working when I'm connected to the machine network.

The error I receive is that the IPSimatic login is not loading, and after that swaclogin is unavailable.
I'm working with local user management

Any idea's how I could make this work on both network's? 

Thanks in advance! 

Thanks for your answer, I've tried setting it up with use PC name instead of IP adress, but when connected to the machine network (with an Ewon, maybe this is also an issue) I'm stil receiving the Swac login error. 

If I understand correctly it is not possible with the equipment that I have. I would need a DNS server. 

It's not a problem in this project, I can reach the Runtime PC with RDP, but for next projects it would be interesting to consider to use a DNS server on the local machine network. 

Thanks, 

Wim_p

I'm trying to figure out how to setup a Unified runtime PC which is connected to the shopfloor and the machine network. The PC has 2 network cards.

Machine network range: 192.168.10.x (Wincc At 192.168.10.122)

Shopfloor network range: 192.168.1.x (Wincc at 192.168.1.9)

 If you want to access your scada from 2 separate networks you should use a router, not add network cards. In principle your Webserver only goes out from 1 "channel", there are ways to make part of it visible in both networks, but certificates and other stuff are linked to only one IP (as you have found out). This is not really a limitation of Wincc Unified but more of a base concept.
The multiple network card is a feature made with the idea to gather data by the SCADA, then you access your data at a single point.

If you want a quick and (extremely) dirty fix you can just copy your wincc RT device in the project and configure one for each IP. You can have multiple scada on one server, you will need to acquire more licenses, but if it is for testing purposes you can just deal with the popup.

If you want to access your scada via VPN (ewon) you are making your life a lot easier by using IP instead of computer name. I would suggest not even trying implementing DNS, unless you have some competent IT technicians by your side (I don't).

I have not tested it, but in theory if you enable routing in windows (on the server) and then add a static route to your client you should be able to access the second interface via the first one. Keep in mind that this will open up the machine floor network to the shopfloor network and vice versa. or any network connected to the server