I am in a corporate environment and some of my users from time to time will receive the error "Server out of resources. Try again later" when the try to login. We are on W2k stations and if you log into the workstation only and then log into the server, it will usually let you in. I have checked the server cache and resources and everything seems ok. It only happens every once in a while and is usually not the same person. Any suggestions would be greatly appreciated.

What is the NetWare client version you're running?

We are running version 4.81.0.1. We have multiple servers and everyone is on the same client, but the people on my server are the only ones having a problem.

Hi, I would suggest upgrading to 4.83sp2. 4.81 & 4.82 have nasty bugs when dealing with NCP traffic from a MS OS. The message of low or failing resources is just one symptom. Others include the inability to authenticate to the server, very slow transfer rates, server to server chaos, and the disconnection from a server without offering the reconnect until reboot. The cause is anything from manually mapped drives to connecting to the server. As XP/2000 has a tendency to "bully" itself through a network enviroment, This works against Novell's operations. Because of this, I'd also suggest disabling messenger and raw sockets. For what that is worth. With that, and the installation of the new client, you should be alright. If not you are still better off. There are manual switches to set that override the defaults and offer more resources to the clients from the server. I agree with Novell in advising against this as it doesn't cure the problem, it only applies a bigger bandaid to excuse wasted resources through a bottleneck. By increasing the bottleneck, it leads to other issues, and does little to remedy the problem. A more detailed explanation is here: http://www.computing.net/netware/wwwboard/forum/4670.html Which is a post before yours entitled "NCP Packets" Without knowing your network intricacies better, I think this should cure you. After all, clients are free, there updated for a reason, and who should know Novell's products better than they do? Furthermore, a simple addition of more ram to the server may not work at all, since the NOS would not allocate the new addition properly without being told to do so. Its worth investigating, but running the old clients are also compromised by recent MS updates. Yet further encouragement to upgrade the clients. Another avenue to pursue would be cabling, routing, and associated hardware. I find this less likely to be the case since you've described clients can connect, only not automatically at boot. From my side, I am technically minded above all all else, and I can only offer what changes *should* happen. HTH, -J

Also, I thought I should clarify: The error that the server is "out of resources" is, as you have verified, bogus. One of the bugs that exists in 4.81 & 4.82 is the glitchy inability to correctly understand what is actually available from the server. If the client cannot "find" resources, it assumes the resources must not exist. The same principle applies to other problems. Just because an error message claims its "Problem #154", and you have seen its false, there is no reason to assume that "Problem #154" is even remotely connected to the true problem. The alterable resource switches I mentioned above only fool the client into seeing some resources in an already abundant environment. This is why I labeled it as a "bandaid", and it would not solve "Problem #154". As the nature of the problem is erroneous and inconsistant, it lacks credibility toward remaining isolated. I thought I'd be specific so as not to confuse through an unexplained issue. HTH, -J

Thanks for all of your help. I will give this a try...

Upgrading clients shouldn't hurt anything. But the start of the process should have been determining if the error message was a netware or microsoft error. Did you check your server client access license count to your user login count? How many users logging into this server? Reason I ask is if you are right at the boarder of license count vs logined user count you can get "can't login at this time messages". So to if your nic/server is busy and can't get to the user authenication. Just some other things to check.