2: Introduction
WiPort® NR Embedded Device Server User Guide
10
Protocol Support
The WiPort NR device server uses the TCP/IP protocol stack for network
communications. Other supported protocols include:
ARP, UDP, TCP, ICMP, Telnet, TFTP, AutoIP, DHCP, HTTP, and SNMP for
network communications and management.
TCP, UDP, and Telnet for connections to the serial port.
TFTP for firmware and web page updates.
IP for addressing, routing, and data block handling over the network.
User Datagram Protocol (UDP) for typical datagram applications in which devices
interact with other devices without maintaining a point-to-point connection.
SMTP for e-mail transmission.
Configuration Methods
For the unit to operate correctly on a network, it must have a unique IP address on
the network. There are three basic methods for logging into the device server:
DeviceInstaller
: View the current WiPort NR configuration using a Graphical User
Interface (GUI) on a PC attached to a network. (See
Web Manager
: Through a web interface, configure the WiPort NR embedded device
server and its settings using the WiPort NR Web Manager. (See
Serial & Telnet Ports
: There are two approaches to accessing Serial Mode. Make a
Telnet connection to the network port (9999) or connect a terminal (or a PC running a
terminal emulation program) to the unit’s serial port. (See
Addresses and Port Numbers
Hardware Address
The hardware address is also referred to as the Ethernet address or the MAC
address. The first three bytes of the Ethernet address are fixed and read 00-20-4A,
identifying the unit as a Lantronix product. The fourth, fifth, and sixth bytes are unique
numbers assigned to each unit.
Example:
00-20-4A-14-01-18
Note:
Make note of the MAC address. It is needed to locate the WiPort NR
embedded device server using the DeviceInstaller™ utility.
IP Address
Every device connected to an IP network must have a unique IP address. This
address is used to reference the specific unit. The WiPort NR embedded device
server is automatically assigned an IP address on DHCP-enabled networks as it is
DHCP-enabled by default.