NetNathan
Lifetime Supporting Member
In my inadvertent ignorance (back in early 1994) I started addressing my GE PLCs in the default field on the the cpu.....3.0.0.?. At that time...may years ago, I did not know that 3.0.0.? was also an Internet range, not an "internal only" range like 192.168.1.?.
Now I have an issue....
Amazon has bought the 3.0.?.? range and is using a few of these addresses for their cloud.
I have hundreds of PLC systems using this 3.0.0.? IP range.
The facility where I have the most problems has 35 PLCs and 38 PCs, all in the 3.0.0.? range. It would be a huge pain to go and change all those IP ranges. This site is always connected to the Internet, because I have LogMeIn access for troubleshooting.
SO....if I am connected to the internet when I am troubleshooting logic, I get address conflicts.
Can I isolate this problem with a Router? Plus.... still have access to the Internet for remote access and the time server?
Now I have an issue....
Amazon has bought the 3.0.?.? range and is using a few of these addresses for their cloud.
I have hundreds of PLC systems using this 3.0.0.? IP range.
The facility where I have the most problems has 35 PLCs and 38 PCs, all in the 3.0.0.? range. It would be a huge pain to go and change all those IP ranges. This site is always connected to the Internet, because I have LogMeIn access for troubleshooting.
SO....if I am connected to the internet when I am troubleshooting logic, I get address conflicts.
Can I isolate this problem with a Router? Plus.... still have access to the Internet for remote access and the time server?