Users Loosing Network Resources

Hi Experts,
This has become a real problem for a customer of mine. They are ready to cancel there service contract if I do not get is resolved. I have a SBS 2003 acting as a Domain Controller. There are 12 workstations all with XP Pro. Most of the time every thing is working well. What happens is the they will lose connection to the server. If they are working on a word document from a network folder the program will lock. They also use AutoCAD and if it happens when they are in a drawing it will lock up. This will not happen at the same time for each workstation. 1 can be locked up and the other is working fine. They say that it seems to happen at the end of the day between 4-5 pm. They have mouse movement and can open programs on the workstation. I checked the event viewer on the XP workstation and see:

ID 40960
The Security System detected an attempted downgrade attack for server cifs/Server.  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.

ID 40961
The Security System could not establish a secured connection with the server cifs/Server.  No authentication protocol was available.

ID 5719
No Domain Controller is available for domain HARTCORN 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.

I have checked

1. Power settings on the network cards
2. Log in times
3. Auto disconnect on the server

Thanks for the help
Who is Participating?
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Also, I would wonder if you had originally attached your workstations to the network correctly because if they didn't have your server's IP for DNS then you wouldn't have been able to.  With SBS you MUST attach worksations with the http://<servername>/connectcomptuer or you won't have the advantages provided by SBS which are listed in this blog post:

To correct this problem, please follow these steps:

The following needs to be done with the client machine:
1.  Log in with THAT machine's LOCAL administrator account.
2.  Unjoin the domain into a WORKGROUP
3.  Change the name of the computer (this is not an option, you must use a name that is unique and hasn't been used before on your SBS)
4.  Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients if it exists
5.  Make sure that the network settings are configured to get an IP address automatically (DHCP enabled)
6.  Reboot

Then on the server, from the Server Management Console:
1.  Remove the client computers if it still shows in the Client Computer screen on the Server Management Console
2.  Add the client with it's NEW name using the Add Computer wizard

Then, go back to the client machine and join the domain by opening Internet Explorer and navigating to http://servername/connectcomputer

While this may seem like a pain to do, it's well worth it in the long run.

Seems like a DNS problem; either your DNS isn't configured correctly, or the server was configured with a single-label AD domain name (just "company" instead of "company.local", and not to be confused with the NetBIOS domain name), or both.

Check if this applies:
Information about configuring Windows for domains with single-label DNS names

And check if your DNS configuration matches these articles (in short: use *only* the SBS as DNS, configure forwarders to point to your ISP's DNS, allow dynamic updates).
10 DNS Errors That Will Kill Your Network

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

Finally, you can install the Support Tools and run netdiag.exe and dcdiag.exe
Windows Server 2003 Service Pack 1 32-bit Support Tools
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Please post a complete IPCONFIG /ALL from your server and a sample workstation in order to help you diagnose the problem.

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

DjJohnnyAuthor Commented:
I will post the SBS questions here ,Thanks.
I made the changes to the DNS on the server,pointing it to it self and changed the work stations to the server for DNS. It has been 2 days and no problems. I will see wat happens in the next week or so and post back
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You should have your workstations using DHCP and DHCP should be provided by your SBS, just FYI.

Now, out of pure curiosity: if my suggestion to check and correct your DNS settings seems to have resolved the issue, why did you accept a comment just asking you to run "ipconfig /all" as answer?
DjJohnnyAuthor Commented:
Sorry Clicked the wrong one
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.