Emerson Exchange 365

• Not Answered

NTP Server IP address

Our Proplus is looking at a NTP server on the network, all other nodes look to the ProPlus to get the time. Some of them look to the Primary NIC IP, some of them look to the Secondary  NIC IP.

What determines this IP address. I can't see anything in setup that does this.

Thanks

Eric Stephens

• 22 Feb 2018 3:40 PM
• Cancel

4 Replies

• Abhinav Thakur

  

  • 22 Feb 2018 3:46 PM

  If you're asking where you can locate the NTP IP Address, you can find it by expanding your Pro Plus station in the physical network and right clicking on Remote Network and then clicking on properties. On the advanced tab should be the IP address the Pro Plus looks to for time.

  • Cancel
• Eric Stephens

  

  • 22 Feb 2018 3:53 PM

  In reply to Abhinav Thakur:

  No, I want to know WHAT determines the IP Address in diagnostics. When I look at a node in diagnostics (not the ProPlus) it displays the NTP Server machine (ProPlus) and also the Primary or Seconday network IP Address. What determines the primary or secondary. The only thing in the Physical Network properties is the ProPlus no IP.

  • Cancel
• chip.burge

  

  • 22 Feb 2018 4:26 PM

  In reply to Eric Stephens:

  Abhinav is correct as far as where the lowest stratum NTP servers are configured for the DeltaV network. Either hostnames or IP addresses will work for DeltaV master time nodes - but it seems you are looking for a more general answer about name resolution.
  
  Windows resolves host names at the highest level by checking down the binding order of the NIC cards and then following this sequence for each NIC:
  
  Host name resolution generally uses the following sequence:
  
  1. The client checks to see if the name queried is its own.
  2. The client then searches a local Hosts file, a list of IP address and names stored on the local computer.
  
  NOTE: The Hosts file location depends on the operating system:
  
  Windows NT %Systemroot%\System32\Drivers\Etc
  Windows 95 <drive>\<Windows folder>
  Windows for Workgroups <drive>\<Windows folder>
  Windows 3.1 <drive>\<Windows folder>
  MS-Client 3.0 <Boot volume>\Net
  Lan Manager 2.2c Client <Boot volume>\Net
  
  Where %Systemroot% is the folder in which Windows NT is installed, <drive> is the drive on which the OS is installed, and <boot volume> refers to a boot floppy disk or drive C.
  
  A sample hosts file, Hosts.sam, is installed with the TCP/IP protocol showing the proper format.
  3. Domain Name System (DNS) servers are queried.
  4. If the name is still not resolved, NetBIOS name resolution sequence is used as a backup. This order can be changed by configuring the NetBIOS node type of the client.
  
  Stolen from support.microsoft.com/.../microsoft-tcp-ip-host-name-resolution-order
  
  TLDR: NETBIOS/SMB if you're in a workgroup, DNS if you're in a domain

  • Cancel
• Matt Stoner

  

  • 22 Feb 2018 4:28 PM

  In reply to Eric Stephens:

  Take a look at KBA NA-0200-0147 and specifically section 1.3.
  
  You also may want to check the NIC binding order on the workstations are setup properly with Secondary first, Plant Lan second, Primary third and any other NICs after.

  • Cancel