Possible Timeout issue with NLM 1.12 (Networking Products)
At 03 FEB 1999 02:06:23PM Jim Cross wrote:
Currently have a user in Detroit, MI that logs into a primary server located in Troy, MI (about 20 miles away). The user also attaches to a server in Detroit where the Arev application runs from. The Arev application v3.12 is running the NLM 1.12. When she logs into the Arev application, an error comes up indicating that the NLM is not in control of her Arev files. If we have the same user login to a primary server in Detroit and attach the Arev server, she is able to log into Arev with no errors. I am wondering if this may be due to some kind of timeout error. The TSR default settings for /c: is 60, which is the setting we use. The NLM has a default setting of 10 for option /c:, which we are using 30. If these are not the correct settings, what should they be? The mannual say to have the TSR run at at least half the time as the NLM. If this information seems correct, is there any other possible reason that the user could be having trouble getting into Arev. She is running on a Compaq running Window
s 95 and Novell Intranetware 2.5. Thanks in advance for any help that can be given.
At 04 FEB 1999 09:13AM akaplan@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url] wrote:
Could be a SAP thing, so the server is drowning out the NLM stuff, but still connecting to the server.
When they log in direct, does it go through the same path?
akaplan@sprezzatura.com
At 05 FEB 1999 09:12AM Jim Cross wrote:
The paths are different. The path from Detroit to Troy has a lot more traffic than the local connection. Thank you very much for the suggestion. Is there any settings on either the TSR or the NLMs to compensate for this possible problem? Any thoughts would be greatly appreciated.