Preparing SNE for a network that supports DNS but not DHCP - Metasys - LIT-12013352 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - Supervisory Device - SNE10 Network Engine - SNE11 Network Engine - SNE22 Network Engine - SNE Supervisory Network Engine - 12.0

SNE Commissioning Guide

Product name
SNE10 Network Engine
SNE11 Network Engine
SNE22 Network Engine
SNE Supervisory Network Engine
Document type
Commissioning Guide
Document number
LIT-12013352
Version
12.0
Revision date
2022-12-12
Product status
Active

This scenario is not typical of modern networks. The steps are identical to the steps in the Preparing SNE for a network without DHCP and without DNS support when the SNE uses APIPA and Preparing SNE for a network without DHCP and without DNS support when the SNE uses a static IP address.

Using the SNE Ethernet MAC address (from the SNE label), the network administrator can update the DNS server and the assigned computer name. If this is done, you can enter dns-name in Launcher on any computer on the building network.