For example, instead of APIPA reassigning the PC into something on the 169.254.1.0 /20 subnet, could we assign the PC into something on a 10.101.x.x subnet?
In case this is a dumb question, maybe someone else has another idea for a solution?
I have a Windows PC that will be straddling two different networks. When operations personnel use it on power systems devices, I need the laptop to be on a 10. Subnet. When theyre done using it, it needs to be returned to the IT network to receive regular Windows updates and security patches on a DHCP network.
I can't implement DHCP on the operations network because of how communication is configured between the various relays, transformer monitors, breaker monitors, etc...
I'm trying to make this as simple for operations people as possible. Training them to reconfigure their Network adapter back and forth everytime can result in too much human error.
No comments:
Post a Comment