Airlink AR315W Manual - Page 43
Connection Log Messages - reset password
View all Airlink AR315W manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 43 highlights
Operation and Status Buttons Connect Disconnect Clear Log Refresh • The most common messages are listed in the table below. • The "Clear Log" button will restart the Log, while the Re- fresh button will update the messages shown on screen. If not connected, establish a connection to your ISP. If connected to your ISP, hang up the connection. Delete all data currently in the Log. This will make it easier to read new messages. Update the data on screen. Connection Log Messages Message Connect on Demand Manual connection Reset physical connection Connecting to remote server Remote Server located Start PPP PPP up successfully Idle time-out reached Disconnecting Error: Remote Server not found Error: PPP Connection failed Error: Connection to Server lost Error: Invalid or unknown packet type Description Connection attempt has been triggered by the "Connect automatically, as required" setting. Connection attempt started by the "Connect" button. Preparing line for connection attempt. Attempting to connect to the ISP's server. ISP's Server has responded to connection attempt. Attempting to login to ISP's Server and establish a PPP connection. Able to login to ISP's Server and establish a PPP connection. The connection has been idle for the time period specified in the "Idle Time-out" field. The connection will now be terminated. The current connection is being terminated, due to either the "Idle Time-out" above, or "Disconnect" button being clicked. ISP's Server did not respond. This could be a Server problem, or a problem with the link to the Server. Unable to establish a PPP connection with the ISP's Server. This could be a login problem (name or password) or a Server problem. The existing connection has been lost. This could be caused by a power failure, a link failure, or Server failure. The data received from the ISP's Server could not be processed. This could be caused by data corruption (from a bad link), or the Server using a protocol that is not supported by this device. 39