Question Locked

dropping clients after ten hours

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We recently have switched our clients to a Windows 2003 server. It seems that after 10 hours the clients are losing their connection. I have checked all the policies and do not see anything that would apply. Can anyone help. Thanks.

5 replies

by xt john

are they just clients within your network logging into your domain? or terminal services clients? There are time out settings for TS clients, if sessions are idle, to disconnect after a certian time, etc.

by louisl

When I say clients I am referring to the PC's in our office that are connected to our server directly they all have static IP's. Thanks

by mike

I just had the exact same type situation, and it turned out to be a DNS issue, not Active directory. it seems that with the static IP's set, the DNS server was set to an external box(Firewall/spamfilter/dhcp server/gateway) and dns for all clients were set to that box. They were able to find the server initially, but failed to re-authenticate later, at which time the clients started looking to netbios for the server instead of dns. Turned out his internal domain was named the same as his hosted domain for his web page, and the clients looked to dns to reconnect to the domain, and found the wrong one (External instead of internal).

I set up DNS on the server to forward all dns requests except the internal domain, and set all clients to use the server's DNS instead of the gateway's and the issue stopped happening, and all clients were able to re-authenticate to the domain.

by ctal

I set up DNS on the server to forward all dns requests except the internal domain, and set all clients to use the server's DNS instead of the gateway's and the issue stopped happening, and all clients were able to re-authenticate to the domain.

This discussion is closed to new replies.