Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 01 MAR 1999 03:39:03AM Bianca Connelly wrote:

We have a user running an NT network with a hub and some 50 terminals.

Once or twice a day each terminal just drops out of OI back to Win95/98, sometimes while the terminal appears to be idle.

Any suggestions what may be causing this?


At 01 MAR 1999 04:29AM Steve Smith wrote:

Assuming that OI is not the only application that is cutting out:

(a) check and disable the BIOS power management features, bth in the BIOS setup and (if present) in the operating system

(b) using REGEDIT, check that the server and the workstations have no connection timeouts set. The default for NT 4.0 workstations is 600 seconds - long enough for a coffee or lunch break.

http://support.microsoft.com/support/kb/articles/q102/9/81.asp

You can modify the startup parameters for the Workstation service using the Registry Editor. Unless otherwise indicated, these value entries are found in the following Registry path:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
   \Services\LanmanWorkstation\Parameters

KEEPCONN REG_DWORD 1 TO 65535 SECONDS

Default: 600

Specifies the maximum amount of time that a connection can be left dormant. This parameter is the redirector equivalent of the Disc parameter in the Services\LanmanServer\Parameters subkey.

As a general rule, try increasing this value if your application closes and opens UNC files to a server less frequently than 10 minutes apart. This decreases the number of reconnections made to a server.


At 02 MAR 1999 01:47PM Bianca wrote:

Thanks Steve,

That is a very comprehensive answer.

Bianca

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/ec1e605f31febe8e85256727002f8597.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1