Home All Groups Group Topic Archive Search About

Network Shares are slow to display Contents

Author
10 May 2007 4:26 PM
H. Hudson
We have a Windows 2003 domain controller with a mix of windows XP and windows
2000 computers.  One of the Windows XP computer is very slow to diplay the
contents of the network shares off the Windows 2003 server.  All of the other
computers are just fine.

On the computer with the problem.  We receive the following error in the
event log.

Event Type:    Error
Event Source:    NETLOGON
Event Category:    None
Event ID:    5719
Date:    5/8/2007
Time:        4:52:04 PM
User:        N/A
Computer:    CADDIS-CDALE
Description:
No Domain Controller is available for domain CADDISINC due to the following:
There are currently no logon servers available to service the logon request.
..
Make sure that the computer is connected to the network and try again. If
the problem persists, please contact your domain administrator.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À   

The computer is recieving DHCP just fine, and can resolve names on the
network.  I've tried anther workstation on its network cable - which didn't
have any problems with the network shares.  And i've tried another NIC in the
computer, which still reproduces the problem.

Thanks

Heather

Author
11 May 2007 12:39 AM
Chuck
On Thu, 10 May 2007 09:26:02 -0700, H. Hudson
<HHud***@discussions.microsoft.com> wrote:

Show quoteHide quote
>We have a Windows 2003 domain controller with a mix of windows XP and windows
>2000 computers.  One of the Windows XP computer is very slow to diplay the
>contents of the network shares off the Windows 2003 server.  All of the other
>computers are just fine.
>
>On the computer with the problem.  We receive the following error in the
>event log.
>
>Event Type:    Error
>Event Source:    NETLOGON
>Event Category:    None
>Event ID:    5719
>Date:    5/8/2007
>Time:        4:52:04 PM
>User:        N/A
>Computer:    CADDIS-CDALE
>Description:
>No Domain Controller is available for domain CADDISINC due to the following:
>There are currently no logon servers available to service the logon request.
>.
>Make sure that the computer is connected to the network and try again. If
>the problem persists, please contact your domain administrator.
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>Data:
>0000: 5e 00 00 c0               ^..À   
>
>The computer is recieving DHCP just fine, and can resolve names on the
>network.  I've tried anther workstation on its network cable - which didn't
>have any problems with the network shares.  And i've tried another NIC in the
>computer, which still reproduces the problem.
>
>Thanks
>
>Heather

Heather,

Depending upon how your domain and your LAN is setup, your computer MIGHT
resolve some names just fine.  When you have a domain controller, your name
resolution can only be setup one way.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

Also look at the personal firewall and NetBT setup.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

Finally, look at "browstat status" and "ipconfig /all", from the problem
computer, and from one working computer, and compare the two.  Read this
article, and linked articles, and follow instructions precisely (download
browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My        email         is          AT         DOT
   actual       address    pchuck       mvps        org.
Author
11 May 2007 11:36 AM
Ian
Above is all good advice, also don't overlook the very common LAN-card
powersave bug.

http://mylogon.net/support/psave/