This table contains all settings that define the behavior of the COM port in the network.
Note: Please note that all of these parameters can be overwritten by
the remote site if the RFC2217 negotiation is active. Current settings
can be viewed in the status menu.
LANconfig: COM ports / Server / Network interface
WEBconfig: Setup / COM-Ports / COM-Port-Server / Network settings
- Device type Selects a serial interface from the list of those available in the device.
- Port number Some serial devices such as the CardBus have more than one serial port. Enter the number of the port on the serial interface that is to be used for the COM-port server.
- TCP mode Each instance of the COM port server in server mode monitors the specified listen port for incoming TCP connections. Just one active connection is permitted per instance. All other connection requests are refused. In client mode, the instance attempts to establish a TCP connection via a defined port to the specified remote site, as soon as the port is ready. The TCP connection is closed again as soon as the port becomes unavailable. In both cases a LANCOM closes any open connections when the device is restarted.
- Listen port The TCP port where the COM port in TCP server mode expects incoming connections.
- Connect host name The COM port in TCP client mode establishes a connection to this host as soon as the port is in "Ready" status.
- Connect port The COM port in TCP client mode uses this TCP port to establish a connection as soon as the port is in "Ready" state.
- Loopback address The COM port can be reached at this address. This is its own IP address that is given as the source address when establishing connections. This is used to define the IP route to be used for the connection.
- RFC2217 extensions The RFC2217 extensions can be activated for both TCP modes. With these extensions activated, the LANCOM uses the IAC DO COM-PORT-OPTION sequence to signal that it will accept Telnet control sequences. The COM port subsequently works with the corresponding options; the configured default values are overwritten. The port also attempts to negotiate the local echo and line mode for Telnet. Using the RFC2217 extensions with incompatible remote sites is not critical. Unexpected characters may be displayed at the remote site. A side effect of using the FRC2217 extensions may be that the port regularly carries out an alive check as Telnet NOPs are transmitted to the remote site.