Problem maintaining network resource connection

[Guest Bob]

Hi Everyone!

 

Setup: business network with 1 server (Windows Server 2003) acting as domain

controller, file server, and multiple machines running XP Pro SP2. Each

Machine requires domain logon on startup.

 

I'm having a problem with a machine that is connected to this network. When

I first boot the machine it connects fine and can access all shared folders

on the networked machines. After about 30 minutes the mapped drives change

to Disconnected network drives. When I try to access one of the

shared/mapped drives I get a prompt for a username and password. When I

enter the username and password it gives the message that the logon info has

already been used. This being said, the logon info was given when the

machine first logged on during startup and should maintain a connection to

resources as it does when it first boots.

 

Something is timing out and not allowing the machine to reconnect to the

shared resources. Internet access is maintained throughout the problem.

 

Ideas appreciated.....

 

Thanks

[Guest VanguardLH]

Re: Problem maintaining network resource connection

 

"Bob" wrote in message

news:wNCdnfEE663fekLanZ2dnUVZ_h2pnZ2d@comcast.com...

>

> Setup: business network with 1 server (Windows Server 2003) acting

> as domain controller, file server, and multiple machines running XP

> Pro SP2. Each Machine requires domain logon on startup.

>

> I'm having a problem with a machine that is connected to this

> network. When I first boot the machine it connects fine and can

> access all shared folders on the networked machines. After about 30

> minutes the mapped drives change to Disconnected network drives.

> When I try to access one of the shared/mapped drives I get a prompt

> for a username and password. When I enter the username and password

> it gives the message that the logon info has already been used.

> This being said, the logon info was given when the machine first

> logged on during startup and should maintain a connection to

> resources as it does when it first boots.

>

> Something is timing out and not allowing the machine to reconnect to

> the shared resources. Internet access is maintained throughout the

> problem.

 

 

Do you really need to use a mapped drive designator to a networked

host? That means you have to connect and remain connected to that

host even when you aren't accessing that host. Can't you use UNC

paths to the folder on the networked host? That way you only make a

connection at the time you need it. The only time I use mapped drives

is for crappy software that can't understand UNC paths and require a

drive letter designation. I only use a mapped drive letter if I am

forced to use one, and I haven't been forced to use one in many years.

 

You sure the networked host isn't dropping idle connects to it? Read

http://support.microsoft.com/kb/297684/en-us.

 

What power saving scheme do you use on your host? Does it go into

standy or hibernate modes?