throckto
asked on
Windows Server 2003 dropping clients
I have windows server 2003 with 6 windows XP clients that are constantly dropping. These dropped connections also cause a NAS to disconnect and have to be rebooted to reconnect.
So far I have tried.
1. Switching from DHCP to fixed IP addresses and turning off DHCP.
2. Disabling the resource conservation features.
3. Switching routers.
4. forcing the NICs to fixed speed settings versus auto-negotiation.
The only thing that has worked so far is logging everyone on using the administrator log on. I tried giving a user administrative priviledges but that did not work, in order to maintain the connection longer than 1 day they have to log in as administrator.
So far I have tried.
1. Switching from DHCP to fixed IP addresses and turning off DHCP.
2. Disabling the resource conservation features.
3. Switching routers.
4. forcing the NICs to fixed speed settings versus auto-negotiation.
The only thing that has worked so far is logging everyone on using the administrator log on. I tried giving a user administrative priviledges but that did not work, in order to maintain the connection longer than 1 day they have to log in as administrator.
ASKER
Thanks I will try that.
Some additional information, even though the client is no longer connceted to the domain I still have internet access. The main issue seems to be that drive mappings are being dropped and then can not reconnect without logging out of the client and loggin back in, then it functions normally until the next morning when it has dropped the drives again. I checked to make sure there were no time restrictions set on users and there aren't any.
Some additional information, even though the client is no longer connceted to the domain I still have internet access. The main issue seems to be that drive mappings are being dropped and then can not reconnect without logging out of the client and loggin back in, then it functions normally until the next morning when it has dropped the drives again. I checked to make sure there were no time restrictions set on users and there aren't any.
Portfast needs to be enabled for XP clients. Otherwise you will see intermittant comms on XP clients.
ASKER
Sorry for the delay in responding, I have been out of town.
I tried the DNS settings, it did not resolve the problem.
On the portfast, the only references that I can find on that is hardware related to switches. There is no option on the existing switch under spanning tree to do anything with portfast.
I tried the DNS settings, it did not resolve the problem.
On the portfast, the only references that I can find on that is hardware related to switches. There is no option on the existing switch under spanning tree to do anything with portfast.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I switched out the router to a better one and enabled portfast and it seems to be functioning now.
Good deal
In short: make sure you use *only* your DC as DNS on *all* domain members (including the DC itself) in the TCP/IP settings. Configure forwarders in the properties of the DNS server pointing to your ISP's or your outer's DNS; the Forwarders section is the *only* place in your network configuration where external DNS servers may appear.
Check these for details:
10 DNS Errors That Will Kill Your Network
http://redmondmag.com/features/article.asp?EditorialsID=413
Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036