Novell NetWare 6.5 server located in building #1, IP network
VLAN connection to building #2
Users are separated by context: User A1. A2, A3... in context A, User B1, B2, B3 ... in context B, etc.
All computers using NetWare Client 4.91 SP3
One directory tree, one parent container that holds all context/containers A, B, C....
Many client computers work well. If user A2 logs off, and user B1 enters name in login screen, the context will automatically update from context "A" to context "B"; providing the correct password will allow the user to log on. Each time a user ID is entered, and the tab key is used to proceed to the password entry position, the context will change to match that user's context.
Some client computers, especially older Dell models, will not work this way. If you change user IDs to a user with a different context, the context of the prior user will be displayed, and the login process fails. Sometimes the user can manually enter the correct context information and proceed to a successful login.
On the failing computers, sometimes the user can click the "context" button on the client, and browse to the correct context. Many times, an error message is displayed telling the user that the tree cannot be found.
Each computer has the IP address for the NetWare 6.5 server included in the local hosts file, showing the various names of "server", "Server.Context", etc. Any computer can ping the server by the server name, the server.context name, etc. All traffic runs well, with no degradation.
We have tried various client software, moved network connections (swapping the patch cords between two "working" and "non-working" computers. The problem stays with the specific computer. Internet access and other functionality is responsive.
Any ideas on what would cause some computers in a room to fail to see the tree, or fail to update the context information when changing the user ID?
Start Free Trial
