I just implemented a change from an old NT4 server to Server 2003 in August.

The problem is that the XP Pro clients disconnect ALL mapped drives around 6 PM daily. The users have to reboot and then the connection comes back.

This did NOT occur with the XP Clients when they attached to the NT4 Server, just the new 2003 Server.

All users map via a logon script when they logon to the server/domain.

There are NO logon time paramaters, all users can access the server 24/7.

I have attmepted the Power Setting/NIC option.

I have also attempted the "autodisconnect" Registry change.

The Server is NOT backing up until the 2/3 AM hours, so I don't think that is it.

Any ideas? Are others having this problem?

I don't have this problem, although the drive will be marked 'disconnected' this is just a resource saving thing, and will reconnect automagically as soon as they are accessed.

Is there any other problem, like can't ping or connect to the server too, or is it just losing the mapped drive?

Peter
(Alert me if you want a reply)

What do you mean

clients disconnect ALL mapped drives around 6 PM daily

When they click on the folder what message appears? access is denied? do you have any other scripts running? that could removing any drive mappings?

If they attempt to reconnect by clicking on the drive it gives an error that the network connection cannot be established. My users HAVE to reboot in order to reconnect.

ALL access to the server shuts down, mapped drives, printing, etc. It is not something the users are doing manually.

We are also having the same problem. We recently purchased 5 new workstations with XP Pro, and 1 new server running Server 2003, all from Dell. Every morning we have to either restart, or click log off and log back in to have access to the software stored on the server. One of the programs we use just goes to a blank screen and there is a flashing cursor. The other says the network connection cannot be established. We turned off our backup software for a week to see if that was the culprit, but that didn't fix the problem. The only thing that stays active is our connection to the internet via. DLS modem connected thru firewall to our gig. switch, so we are pretty sure that the problem lies on the server itself. If you have any ideas please email me at ChuckBerg@msn.com. Thanks!!

Well, I may have the answer!!! But first a little background info.. We have 5 workstations, 1 server, a Gigabit switch, and a external firewall box between the switch and the Sprint DSL modem. Ok, it appears that when Sprint came in to install the DSL modem they changed the modem as first in the DNS search order and our internal server as second. Apparently XP and Server 2003 don't like that so we kept getting disconnected from the server every night. Now that we have reconfigured the DNS search order placing our internal server first we no longer get disconnected. The test has proven out for 2 days and I will keep you posted on our progress if anything changes. The bad news is that it was our outside contracted Tech. that fixed the problem, so I won't be able to walk you thru the fix, but atleast you are now pointed in the right direction. Good Luck!!

Chuck

We are having the identical problem described in this fairly old post about daily disconnection of mapped drives. I would appreciate knowing if original participants or others have had success with the proposed solution of reconfiguring DNS search order.

Thanks,

Rose Jenkins

la solucion es:

Mapped Drive Connection to Network Share May Be Lost

http://support.microsoft.com/kb/297684/EN-US/

pero debe de ser sobre el servidor.

suerte