EtherNet IP Configuration Problem from Secondary Port

Hi everyone, there are FANUC ARC Mate 100iD welding robots in our welding section. We managed to get the log data (especially errall.ls file that records made works) recorded by these robots via Ethernet and then ftp. While doing this process, we connected an Ethernet directly connected to our system to the empty port of the Ethernet ports on the controller (The controller has 2 ethernet ports, one was empty, other one is used for robot communicating). However, the connection of the robot to the controller is lost after a short while. After this connection is removed and the machine is turned on and off, the error is fixed. Our server is mainly using 0 group of IP address range, robot is using it too, in other CNC machines, I solved the problem via adding 1 group of IP address, I believe that if I can assign a 1 group of IP address which can be 192.168.1.104, we can connect the robot to our server. Thank you in advance for your help.

console image

Edit: In Host Comm page, pressing F3-PORT didn't make any port change, I also tried to assign new port in the SETUP RIPE page, changed the Port #: 1 to 2, but it resets to 1 and the 192.168.1.104 to old value automatically when I tried to press any key or exit the panel. Couldn't find a save option of assignment of 2nd port.

Quote from DylanNOEL

Can you post photos of the configuration port 1 and 2 ?
Thanks

Unfortunately I couldn't even switch to Port #2 to configure, F3-PORT button didn't any port change. The fact is if server ethernet connected to other port of robot's secondary ethernet port, could override the robot-controller connection. The 192.168.0.13 is my PC's IP address, I connected another ethernet cable to robot's secondary ethernet port, coming from 8-port switch, has same connection with my PC, but the robot is using also 192.168.0.XX IP address which could override themselves, I want to assign a 192.168.1.XX IP address in order to prevent the override, but couldn't switch to Port# 2 to configure. Pressing F3-PORT didn't make any page change while on "Robot name:" section. After I connected my server's ethernet, I can successfully communicate the controller with my PC. But after, the robot and the controller connection goes down. I uploaded Port#1 configuration page below:

The thread is still unresolved

Quote from Guccio

try using a different subnet mask for the second port. So that these cards are not in the same network.

The problem is that I can't switch to Port#2 page to configure ip.

Quote from pdl

Are you positive that the F3 "PORT" key does not switch to port #2?

Yes I am. However I don't know if there are any option to enable Port#2 in case of the secondary ports are not enabled by default.

Quote from Sergei Troizky

What is the controller model?
Can you post picture(s) of the controller Ethernet ports, with their numbers clearly visible?

The controller is FANUC System R-30𝑖B Mate Plus, I added detail pictures as attachment below.

The system

Ethernet ports before connecting server cable (The ports is behind of Fronius MHP-400i)

Ethernet ports after connecting server cable

Inside of the port cover before connecting server cable

Fronius MHP-400i

The bench

After connecting server cable, the connection between robot and the controller is down, but server connection is established.

I uploaded the pictures via drag-and-drop now. Bottom port P1 represents the robot-controller connection. Upper one is P2, which is an empty port.

Ethernet ports before connecting server cable (The ports are at behind of Fronius MHP-400i)

Ethernet ports after connecting server cable

After a couple of seconds, the Fronius connection is down, the robot won't weld anymore, but server connection (the controller between the pc) is on and can access to its files via ethernet.

Can't switch to Port#2 by pressing F3-PORT button while the cursor at the "Robot name:" , can't switch also the cursor is at anywhere.

I would establish both connection without override, if I could switch to Port#2 to configure external EtherNet.