Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Seeming to hang up after no usage for a period of time
Message
From
25/01/1999 13:45:25
 
 
General information
Forum:
Windows
Category:
Troubleshooting
Miscellaneous
Thread ID:
00174956
Message ID:
00179929
Views:
33
>>>Hi Ed,
>>>
>>>Good day!
>>>
>>>It's me again...
>>>
>>>>>I was wondering if Windows NT has a time out function
>>>>>similar to Novell wherein if a user doesn't use the computer
>>>>>for a while. It basically kicks it out of the network.
>>>>>
>>>>>This happens in my DOS workstations.
>>>
>>>>This is set by account or group, and may be set as a limit on hours that the >user may access the server/domain, or a period of inactivity. There's detailed >information on setting the operating hours and inactivity logout parameters in
>>>>John Savill's NT FAQ, a free reference resource on the net.
>>>
>>>I've looked at the Faq. I saw the ways to setting the operating hours
>>>but couldn't find how to set the period of inactivity. I'm sorry.
>>>Could you be more specific as to how to set the period of
>>>inactivity?
>>>
>>>I've looked at how the group accounts were setup. No measures were placed
>>>made to log off someone beyond a specific period of time.
>>
>>NET CONFIG SERVER can be used to adjust timeouts on Network connections; the syntax to set the autodisconnect delay is:
>>
>>NET CONFIG SERVER /AUTODISCONNECT:< time in minutes>
>>
>>a value of -1 will entirely prevent the disconnection based on inactivity.
>>
>>There's a registry entry that controls this, but I'm not sure exactly where. it can be set as a System Policy user the System Policy editor on a user-by-user or group-by-group basis as well.
>
>I found it:
>
>DISABLING AUTODISCONNECT
>Need a way to disconnect idle LAN sessions after a set number of
>minutes? Windows NT allows you to set an automatic parameter for
>ending LAN connections. You can change the setting either from the
>command line or in the Registry. To make the change in the NT
>Registry, you'll use REGEDT32 to modify the LAN Autodisconnect
>parameter on the following key:
>
>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
>
>The valid value range is 0 to 4294967295 minutes. Setting this value
>to 0 does not disable the setting, as you would think. The best you
>can do in the Registry if you want to disable the value is set it to
>its highest value.
>
>You can also set the number of minutes at a command prompt using the
>Net Config Server command. For example, to set the Autodisconnect
>value to 30 minutes, you would type the following:
>
>Net Config Server /autodisconnect:30
>
>The valid value range is -1 to 65535 minutes at the command line. If
>you set the Autodisconnect option to -1 at the command prompt,
>Autodisconnect is set to the upper value in the registry.

Which will disconnect you in about 8165 YEARS, bringing us headon into the Y10K problem... :)
Fred
Microsoft Visual FoxPro MVP

foxcentral.net
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform