Link to home
Start Free TrialLog in
Avatar of 4RunnerBob
4RunnerBobFlag for United States of America

asked on

Netware Client context problem cannot find tree

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?
SOLUTION
Avatar of Wikkard
Wikkard
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of 4RunnerBob

ASKER

We have tried entering the IP address (of the server) in the server name field, but still have problems with the incorrect context.  Although the user can manually enter the correct context in many cases, it should not be necessary.

The clients are configured the same, yet have different results.  Is there anything specific to the older Dell Optiplex computers that could be affecting this?
SOLUTION
Avatar of Bud Durland
Bud Durland
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No I think if there are running same OS and Netware Client version things should be exactly the same.
BudDurland, all clients are configured the same as far as we can tell.  We use the tab key on the computers that work, and the context changes to match the context of the login name.  If we enter a new login name, the context will change when we use the tab key.

The same method does not work on the "failing" computers - the context continues to display the prior user's context.  Wikkard, you are correct that the OS and client versions are the same.  We appreciate the suggestions that both of you have offered so far.  Any other ideas or suggestions?

The "failing" computers are located in building #2, and connect via a VLAN.  Many working computers are also connected via the VLAN in building #2, so we are wondering what could be different between the working and non working computers.  (Remember that swapping patch cords between a working and non-working PC will not change the results, so we suspect that the problem is related to the PC in some way.  Again, these are primarily older Dell Optiplex computers.  Newer Dell PCs work fine.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Alextoft, thank you for the coolsolutions tip, but according to the information on that web page the contextless login option is already part of the NetWare client 4.9x, when used with Windows 2000/XP computers.  Will this work better than the standard functionality of the 4.9x client software?
Additional information:   The site is a school with multiple buildings.  I have noticed that sometimes when the context does not change to match the login ID, it will instead be pointed to another school's NetWare context.  We will be looking for any information on the working/non-working clients that would point to a difference in configuration.
If there are no further suggestions, we would like to close this thread.