General discussion

Locked

Server Disconnect

By CompuBandit ·
While my company is looking for a new permanent computer adminstrator, my company has appointed me to watch the network. Our server is Windows 2000 small business, and the clients are a mix of Windows XP and Windows 2000. We use a database software to keep track of Real Estate Listings in our area. Pictures and the database are stored on the server. Each client's program points to the server for the information. Here comes the problem, if the connection the server is severed, the program will not look for the connection on the server anymore and defaults to root directory for each particular client. Is there something on the server or the client that causes this disconnect after a certain period? I have checked cabling on each of the troubled machines with a Byte Brothers cable tester and each cable that goes to our switch is fine.

Thanks for your reply,

Aaron Nowicki
CS Major at Michigan Tech.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Server Disconnect

by timwalsh In reply to Server Disconnect

Couple of things to check, both on the server an on individual workstations:

Server: There are actually three different Group Policy settings to check on the server. There is the Local security policy (applied against the local computer), Default Domain Policy (applied against all computers/servers in the domain, and Default Domain Controllers policy (applied against the Domain Controllers Organizational Unit (OU) - all DCs).
All three Security Policies can be accessed from either the Administrative Tools folder in your Start Menu, or through Administrative Tools in the Control Panel. Go to Local Policy | Security Options and look for the policy labeled "Amount of idle time required before disconnecting session." If this policy isset to anything other than "Not defined," change it to 0 minutes.
Note: GPOs are applied the order: Local Computer, Domain, OU. Setting applied later in the process will overwrite settings applied earlier (unless the policy setting is "Not defined"). This setting is set to 15 minutes by default.

Win2K client: Look for the same Local Security Policy setting as above on each Win2K client.

WinXP client: The same setting exists in XP except it is worded slightly differently. Look for "Microsoft network server: Amount of idle time required before suspending session."
XP has also added a power management option for NICs. Look at the Properties of your NIC (either through Device Manager or through Network Connections. In Properties, on the Power Management tab, uncheck the box labeled "Allow the computer to turn off this device to save power." This setting is enabled by default.

Hope this solves your problem.

Collapse -

Server Disconnect

by CompuBandit In reply to Server Disconnect

Poster rated this answer

Collapse -

Server Disconnect

by CompuBandit In reply to Server Disconnect

This question was closed by the author

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums