Novell Home

My Favorites

Close

Please to see your favorites.

Type of Connections in NW3.x / NW4.x

(Last modified: 26Jun1998)

This document (2924115) is provided subject to the disclaimer at the end of this document.

Symptom

What is the * (asterisk) in Monitor.NLM under Connection Information?

Solutions

<<<< From the February 1997 Application Notes article titled "Disconnecting NetWare Clients that Have Automatic Reconnection Enabled." >>>>

Types of NetWare Connections:

Let's look first at the types of connections you can see through the Connection Information option of the server's MONITOR utility. We'll discuss connection types for both NetWare 3.x and intraNetWare/NetWare 4.x.

NetWare 3.x
On NetWare 3.x servers, you can see two types of connections in MONITOR under Connection Information: Not-Logged-In and licensed.

Not-Logged-In Connection. The Not-Logged-In connection type is the initial connection a workstation makes when it is trying to connect to a server. As the NetWare client software loads, the workstation sends an initial "Get Nearest Server" broadcast request to connect to any server on the network. The first server to reply to this broadcast with a "Give Nearest Server" information establishes a temporary connection with the workstation. At this point, the connection appears in the server's connection table as Not-Logged-In.
If the user has specified a Preferred Server either in the NET.CFG file or at the command line and the initial server is not the preferred server, the initial server looks in its Routing Information Table to find the preferred server. It then routes the workstation's request to that server, which responds to the workstation with the nearest route information for direct communication. The Not-Logged-In connection type now appears in the preferred server's connection table. The Not-Logged_In connection (NLI) IS a licensed connection, however, if the server has the current released patches there is a patch that causes the servers connection table to be polled periodically and these connections released. Also, if a user logs in from a workstation that currently has an NLI connection, the same connection number will be used.

Licensed Connection. After the user types in the correct username/ password combination and begins the login process, the user is authenticated to that server. You see the user's name associated with the connection number in the server's connection table, which now takes up a licensed connection.

NetWare 4.x/intraNetWare: In NetWare 4 and intraNetWare, there are three types of connections: Not- Logged-In, Authenticated, and

Authenticated/Licensed.

Not-Logged-In Connection. A Not-Logged-In connection is the same as what you see in NetWare 3.x: the initial attachment of the workstation before authentication or licensing occurs. It is displayed in MONITOR as

"NOT- LOGGED-IN" in the Active Connections window. This could also be a user who has logged out, leaving a Not-Logged-In connection to the server on which his or her default drive was located.
Authenticated Connection. The Authenticated connection is an unlicensed connection that can access Novell Directory Services (NDS) but can't, in its current state, access the server's file or print services. These entries appear in MONITOR's Active Connections windows with an asterisk (*) by their object name.
This type of connection most often occurs when users are browsing the NDS tree to view objects located in an NDS replica held on another server. They can also be from other NetWare servers carrying out NDS synchronization or time synchronization activities. These types of connections do not count against the number of allowable license connections for the server.

Authenticated/Licensed Connection. In NetWare 4.x, the authenticated state occurs when the user enters the correct username and password. From this information, NDS establishes the user's identity and authenticates the user via the security methods found in its encryption algorithms. However, a user's connection doesn't become authenticated and licensed until the user requests access to the server's file and print services. Typically, such requests are initially performed through the container, profile, or user login script. Once the user is authenticated during the initial login process, background authentication establishes connections to any other servers that are designated in the user's login script. An authenticated/licensed connection uses up one of the NetWare server's licensed connections.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 2924115
  • Creation Date: 17Apr1997
  • Modified Date: 26Jun1998
  • Revision:
  • 3
    • NovellNetWare

Did this document solve your problem? Provide Feedback