Search

9 result(s) for HostNames

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.11 AuditUrlMismatchEventType
  EndpointUrl used in the service call does not match the Server 's HostNames (see OPC 10000-4 for details). This Type has been deprecated and will be removed
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.1 Overview
  shall report the difference and may close the SecureChannel . Servers shall add all possible HostNames like MyHost and MyHost.local into the Server Certificate . This includes IP addresses of the host
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.2.1 Description
  unique. This identifier may be available in multiple locales. A Server may have multiple HostNames . For this reason, the Client shall pass the URL it used to connect
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.5.4.1 Description
  deliberately or accidentally hijack Sessions created by other Clients . A Server may have multiple HostNames . For this reason, the Client shall pass the URL it used to connect
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.6.2.1 Description
  difference and may choose to not open the SecureChannel . Servers shall add all possible HostNames like MyHost and MyHost.mycompany.com into the Server Certificate . This includes IP addresses of the host
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  A.1 Firewalls and Discovery
  internal URLs). Administrators can correct this problem by configuring the Server to use multiple HostNames . A Server that has multiple HostNames shall look at the EndpointUrl passed to the GetEndpoints ... return EndpointDescriptions with URLs that use the same HostName . A Server with multiple HostNames shall also return an ApplicationInstance Certificate that specifies the HostName used in the URL it returns
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.3.1 Overview
  with End Station Components in an industrial network, many end users wish to use HostNames rather than IP addresses. Since the underlying transport protocols ... required. By virtue of using OPC UA transport mechanisms, UAFX makes provisions for using HostNames , as described in the following sections. Requirements to support HostName resolution vary by UAFX Profile
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.3.2 HostName resolution using DNS
  containing the other Controller's HostName . In order to send and receive publications, the HostNames need to be resolved to IP addresses. Each Controller has a DNS client
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.3.3 HostName resolution using multicast DNS (mDNS)
  provides HostName resolution without needing a DNS server. Hosts needing to resolve HostNames issue mDNS queries to the well-known IP multicast address for mDNS. In discovering UAFX Servers , Clients