Tech Tip: Increase logon timeout/Include client shares in a DFS root

Windows 2000 Professional: Increase logon timeout

When you log on to a domain, the computer attempts to contact the logon server to authenticate your logon credentials. If the server is unavailable because it's offline, busy, or located on a saturated network segment, your computer might log on with cached credentials. Although this enables you to use your computer, some capabilities will be limited because your credentials haven't been authenticated.

You can take a couple of steps to ensure that a logon doesn't use cached credentials. You can set the following registry key to 0 to disable cached logon:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount

However, you might prefer to simply lengthen the logon timeout period to accommodate a slow connection. To configure the logon timeout, open the Registry Editor and expand the following key:


Add the DWORD value ExpectedDialupDelay to the key, and set it to the number of seconds you want Windows 2000 to wait for a response from the server. You can set the value at anywhere between 0 and 600 seconds.

Note: Editing the registry is risky. Before making any changes, back up the registry so you can restore it if something goes wrong.

Windows 2000 Server: Include client shares in a DFS root

The Distributed File System (DFS) included with Windows 2000 Server enables administrators to build a homogenous file system from multiple servers. The result is a file system that appears under a single namespace and is accessible to users from a single sharepoint. DFS considerably simplifies user access to shared resources, which can cut down on support calls from users who have difficulty finding a particular resource.

If you aren't very familiar with DFS, you might not realize that shares in a given DFS root (or replica) don't have to reside on a server. You can also add a replica from a Windows 9x, Me, 2000, or XP client computer. This capability enables you to bring frequently used client shares into the DFS namespace to make those shares easily accessible by users.

Why should you add user shares this way? For example, if DFS is the underlying file structure for a company Web site, adding user shares to the DFS root enables users to share their files on the Web, and it also allows them to manage their own permissions.

To add a client-based replica to the DFS namespace, simply add the replica as you would for one hosted on a server, but specify the path to the share on the client computer.

Editor's Picks