Workstations lose connection to server after 10 hours

[Neil]

Hi,

Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.

A problem that I have is that for some reason users cannot work longer than
10 hours per day as after being logged on for 10 hours, they cannot access
the server (ie: mapped network drives, etc..) and their computer runs slow.
only way is to re-login.

The message that comes up is the "local device name is already in use.. The
connection has not been restored".

Are there any ideas of what would be causing this? some users are getting
frustrated - they usually have documents and CAD drawings open, and have to
save them locally or they loose their work.

This happens when they login to the domain. When they login to their local
computer they can be logged in for days without any problems.

Thanks

[Sean]

Have you ruled out your anti-virus software?

Sean

"Neil" <Neil@discussions.microsoft.com> wrote in message
news:7CE1470C-5638-4D09-A3E6-1EDDCF45C84E@microsoft.com...
> Hi,
>
> Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
>
> A problem that I have is that for some reason users cannot work longer
> than
> 10 hours per day as after being logged on for 10 hours, they cannot access
> the server (ie: mapped network drives, etc..) and their computer runs
> slow.
> only way is to re-login.
>
> The message that comes up is the "local device name is already in use..
> The
> connection has not been restored".
>
> Are there any ideas of what would be causing this? some users are getting
> frustrated - they usually have documents and CAD drawings open, and have
> to
> save them locally or they loose their work.
>
> This happens when they login to the domain. When they login to their
> local
> computer they can be logged in for days without any problems.
>
> Thanks

[Danny Sanders]

I have seen this when the alternate DNS server listed on the AD client is
not part of the AD domain. Usually this alternate DNS server is the ISP's
DNS server.

Is this the case here?

hth
DDS
"Neil" <Neil@discussions.microsoft.com> wrote in message
news:7CE1470C-5638-4D09-A3E6-1EDDCF45C84E@microsoft.com...
> Hi,
>
> Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
>
> A problem that I have is that for some reason users cannot work longer
> than
> 10 hours per day as after being logged on for 10 hours, they cannot access
> the server (ie: mapped network drives, etc..) and their computer runs
> slow.
> only way is to re-login.
>
> The message that comes up is the "local device name is already in use..
> The
> connection has not been restored".
>
> Are there any ideas of what would be causing this? some users are getting
> frustrated - they usually have documents and CAD drawings open, and have
> to
> save them locally or they loose their work.
>
> This happens when they login to the domain. When they login to their
> local
> computer they can be logged in for days without any problems.
>
> Thanks

[cyberdude]

I have also seen this when there is a misconfiguration in the DNS. If for
instance your DC is configured to be the DNS, but there is another primary
DNS that the workstations are looking to.
--
Tom Zucker-Scharff
Systems Administrator




"Neil" wrote:

> Hi,
>
> Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
>
> A problem that I have is that for some reason users cannot work longer than
> 10 hours per day as after being logged on for 10 hours, they cannot access
> the server (ie: mapped network drives, etc..) and their computer runs slow.
> only way is to re-login.
>
> The message that comes up is the "local device name is already in use.. The
> connection has not been restored".
>
> Are there any ideas of what would be causing this? some users are getting
> frustrated - they usually have documents and CAD drawings open, and have to
> save them locally or they loose their work.
>
> This happens when they login to the domain. When they login to their local
> computer they can be logged in for days without any problems.
>
> Thanks

[Neil]

I haven't as yet - All workstations are using Symantec Antivirus 10.0

"Sean" wrote:

> Have you ruled out your anti-virus software?
>
> Sean
>
> "Neil" <Neil@discussions.microsoft.com> wrote in message
> news:7CE1470C-5638-4D09-A3E6-1EDDCF45C84E@microsoft.com...
> > Hi,
> >
> > Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
> >
> > A problem that I have is that for some reason users cannot work longer
> > than
> > 10 hours per day as after being logged on for 10 hours, they cannot access
> > the server (ie: mapped network drives, etc..) and their computer runs
> > slow.
> > only way is to re-login.
> >
> > The message that comes up is the "local device name is already in use..
> > The
> > connection has not been restored".
> >
> > Are there any ideas of what would be causing this? some users are getting
> > frustrated - they usually have documents and CAD drawings open, and have
> > to
> > save them locally or they loose their work.
> >
> > This happens when they login to the domain. When they login to their
> > local
> > computer they can be logged in for days without any problems.
> >
> > Thanks
>
>
>

[Neil]

The DNS setup is as follows:

The DC is not a DNS server.

DNS is currently disabled on the server.

The DC is not the gateway - a modem/router is (ie: 192.168.0.5)

Each workstation points it's gateway and DNS to this modem/router at
192.168.0.5.

This is done through DHCP coming from the modem/router.

So are you suggesting that I manually configure the alternate DNS to the
server?

Or something to do with DNS anyway?

"Neil" wrote:

> Hi,
>
> Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
>
> A problem that I have is that for some reason users cannot work longer than
> 10 hours per day as after being logged on for 10 hours, they cannot access
> the server (ie: mapped network drives, etc..) and their computer runs slow.
> only way is to re-login.
>
> The message that comes up is the "local device name is already in use.. The
> connection has not been restored".
>
> Are there any ideas of what would be causing this? some users are getting
> frustrated - they usually have documents and CAD drawings open, and have to
> save them locally or they loose their work.
>
> This happens when they login to the domain. When they login to their local
> computer they can be logged in for days without any problems.
>
> Thanks

[Danny Sanders]

> Each workstation points it's gateway and DNS to this modem/router at
> 192.168.0.5.


This is the problem right here.

AD absolutely requires a DNS server set up for the AD domain. This DNS
server must support SRV records.

> The DC is not a DNS server.
>
> DNS is currently disabled on the server.


Suggest you install DNS on this server.
See:
http://support.microsoft.com/kb/814591/en-us
Point this server to itself only in the properties of TCP/IP for DNS. Use
the actual IP address not 127.0.0.1.



Point all your AD clients to this DNS server only.
See:
http://support.microsoft.com/kb/825036/en-us

For Internet access configure your AD DNS server to forward requests and
list the modem/router as the forwarder.
See:
http://support.microsoft.com/kb/323380/en-us
I would forward to the modem/router instead of the ISP like this article
says.


hth
DDS

"Neil" <Neil@discussions.microsoft.com> wrote in message
news:3906B2A0-A45B-4E14-A503-1F50B2F44B7D@microsoft.com...
> The DNS setup is as follows:
>
> The DC is not a DNS server.
>
> DNS is currently disabled on the server.
>
> The DC is not the gateway - a modem/router is (ie: 192.168.0.5)
>
> Each workstation points it's gateway and DNS to this modem/router at
> 192.168.0.5.
>
> This is done through DHCP coming from the modem/router.
>
> So are you suggesting that I manually configure the alternate DNS to the
> server?
>
> Or something to do with DNS anyway?
>
> "Neil" wrote:
>
>> Hi,
>>
>> Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
>>
>> A problem that I have is that for some reason users cannot work longer
>> than
>> 10 hours per day as after being logged on for 10 hours, they cannot
>> access
>> the server (ie: mapped network drives, etc..) and their computer runs
>> slow.
>> only way is to re-login.
>>
>> The message that comes up is the "local device name is already in use..
>> The
>> connection has not been restored".
>>
>> Are there any ideas of what would be causing this? some users are
>> getting
>> frustrated - they usually have documents and CAD drawings open, and have
>> to
>> save them locally or they loose their work.
>>
>> This happens when they login to the domain. When they login to their
>> local
>> computer they can be logged in for days without any problems.
>>
>> Thanks

[Neil]

Thanks Danny,

Will try all that.

Neil

"Danny Sanders" wrote:

> > Each workstation points it's gateway and DNS to this modem/router at
> > 192.168.0.5.
>
>
> This is the problem right here.
>
> AD absolutely requires a DNS server set up for the AD domain. This DNS
> server must support SRV records.
>
> > The DC is not a DNS server.
> >
> > DNS is currently disabled on the server.
>
>
> Suggest you install DNS on this server.
> See:
> http://support.microsoft.com/kb/814591/en-us
> Point this server to itself only in the properties of TCP/IP for DNS. Use
> the actual IP address not 127.0.0.1.
>
>
>
> Point all your AD clients to this DNS server only.
> See:
> http://support.microsoft.com/kb/825036/en-us
>
> For Internet access configure your AD DNS server to forward requests and
> list the modem/router as the forwarder.
> See:
> http://support.microsoft.com/kb/323380/en-us
> I would forward to the modem/router instead of the ISP like this article
> says.
>
>
> hth
> DDS
>
> "Neil" <Neil@discussions.microsoft.com> wrote in message
> news:3906B2A0-A45B-4E14-A503-1F50B2F44B7D@microsoft.com...
> > The DNS setup is as follows:
> >
> > The DC is not a DNS server.
> >
> > DNS is currently disabled on the server.
> >
> > The DC is not the gateway - a modem/router is (ie: 192.168.0.5)
> >
> > Each workstation points it's gateway and DNS to this modem/router at
> > 192.168.0.5.
> >
> > This is done through DHCP coming from the modem/router.
> >
> > So are you suggesting that I manually configure the alternate DNS to the
> > server?
> >
> > Or something to do with DNS anyway?
> >
> > "Neil" wrote:
> >
> >> Hi,
> >>
> >> Setup: 1x Windows SBS 2003 Server, 25 Windows XP Workstations.
> >>
> >> A problem that I have is that for some reason users cannot work longer
> >> than
> >> 10 hours per day as after being logged on for 10 hours, they cannot
> >> access
> >> the server (ie: mapped network drives, etc..) and their computer runs
> >> slow.
> >> only way is to re-login.
> >>
> >> The message that comes up is the "local device name is already in use..
> >> The
> >> connection has not been restored".
> >>
> >> Are there any ideas of what would be causing this? some users are
> >> getting
> >> frustrated - they usually have documents and CAD drawings open, and have
> >> to
> >> save them locally or they loose their work.
> >>
> >> This happens when they login to the domain. When they login to their
> >> local
> >> computer they can be logged in for days without any problems.
> >>
> >> Thanks
>
>
>