To check IP address of PLC, servers, workstation in a network to connect NTP time synchroniser

[SA07]

Hi

We intend to install an NTP time synchronizer to synchronise time on servers, PLCs, workstations.

We must check the IP address of all equipment on the network. In fact we have 3 networks.

To do so we will use the following procedure:

1. Open command prompt in Windows
2. Type “ipconfig” press enter. Present ethernet connection details for server will show.
3. Type “arp -a” press enter. List of connected IP addresses will show.

We have 2 power plants exporting to the utility grid.

While doing this procedure, is there a risk that this disturbs our network and causes our power plants to stop?

After having checked the IP addresses, we will set the time synchronizer and then connect it to our networks.

Is it advisable to do so while our power plants are operating or this may cause the power plant to stop? Or is it better to do so while the plants are stopped?

In case we make a mistake and use IP addresses already in use what will happen when we connect the time synchronizer?

 

[MacGyverS2000]

This question is more readily answered by your IT guy(s)... we have no idea how your network is set up nor what requirements need to be met to avoid killing a system or dropping it from the network.

Dan - Owner

http://www.Hi-TecDesigns.com

 

[IRstuff]

Ostensibly, in a properly configured network, there should neither a stoppage nor glitching for something so minor

TTFN (ta ta for now)
I can do absolutely anything. I'm an expert!

https://www.youtube.com/watch?v=BKorP55Aqvg

faq731-376 forum1529 Entire Forum list

http://www.eng-tips.com/forumlist.cfm

 

[FreddyNurk]

If your addresses and subnets are statically defined then there should be records available of what they are, consult these records before doing anything.
If there's a DHCP server on the network it'll provide an address automatically, although this is likely not the ideal approach for an NTP server.
If you have an AD server on your network and you run authentication against AD then you'll likely already have an NTP service on your network.

However, as MacGyverS2000 has stated, the first port of call is to ask whoever (IT/OT) is responsible for your equipment networks.
I'd not use arp for establishing devices on the network either, something like nmap (probably ping scan only unless IT has disabled ping...) would give better results.

EDMS Australia

 

[esperantes]

Your IT people should be in a position to help you. Don't expect eng-tips.com to do your work. Get competent people on board.
Esperantes

 

[FreddyNurk]

For what it's worth, arp is a communication protocol used to match MAC addresses to IP addresses for a specific machine. Thus, from what I can tell, if the machine on which you're running arp does not have a connection to another machine or device, then its arp table will not contain those IP addresses. Hence it can't be used for the purpose you describe, i.e. to establish what IP addresses are in use on the network.

nmap can be used for this purpose (subject to certain caveats), but it can also be used for a lot more and can raise the ire of the IT department if you don't consult them first.

EDMS Australia