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
29/01/1999 08:01:33
 
 
To
29/01/1999 07:39:44
Jocylyn Sy
Freelance Programmer
Cebu, Philippines
General information
Forum:
Windows
Category:
Troubleshooting
Miscellaneous
Thread ID:
00174956
Message ID:
00181723
Views:
15
>Hi Ed,
>
>>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.
>
>Thanks for the information!
>
>Although I have issued the command, Net Config Server
>/autodisconnect:-1, it seemed to have fixed only 1 of the 4
>DOS computers hanging up. It seems I have to looked at the
>registry.
>

It's worth a look; I'd also check to see if there's something in the LAN configuration on the DOS computers that's initiating the autodisconnect. If the server has set the autodisconnect to (basically) infinity, something else is forcing the systems off, and since at least one system responded, I'd check the configuration of the three that didn't to the one that did.

>Btw, what is the minimum requirement for DOS computers in a
>Windows NT environment?

Enough memory to load the NDIS drivers, network client and DOS; memory requirements are probably dictated more by the application rather than DOS itself. I'd guess that with a reasonably recent version of DOS, the absolute minimum RAM would be in the neighborhood of 256K, depending on the DOS version and NIC drivers in use. It's doubtful that anything beyond edlin would run in that configuration, but the system should be able to boot and load the necessary drivers into real memory and still have 400+K available on a machine with 640K and no extended/expanded memory.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform