Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(837369) - Describes the The list of users and computers could not be found error that clients may receive when they connect to the Windows SBS 2003 network by using the http://SBSservername/connectcomputer URL that is built in to Windows SBS 2003.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 837369 - Last Review: December 3, 2007 - Revision: 1.3

"The list of users and computers could not be found" error message during client network configuration in Windows Small Business Server 2003

View products that this article applies to.

SYMPTOMS

When you follow these steps:
  1. You connect to http://servername/ConnectComputer.
  2. You start the Small Business Server Network Configuration Wizard.
  3. You type the username and password, and then you click Next.
  4. You click Connect to the network now to connect a workstation to the Microsoft Windows Small Business Server (SBS) 2003 network.
You receive the following error message:
The list of users and computers could not be found on the server. Make sure that the Small Business Server network adapters are configured correctly.
Back to the top

CAUSE

This behavior generally occurs when the client computer is not configured to use the server that is running Windows SBS 2003 as the Domain Name System (DNS) server. All client computers on the Windows SBS 2003 network must use the Internet Protocol (IP) address of the internal network adapter on the server that is running Windows SBS for DNS resolution. You must not configure an alternative DNS IP address on the client computers. By doing so, you can cause connectivity issues and slow logon times.
Back to the top

RESOLUTION

To resolve this behavior, change the DNS settings on the client to point to the IP address of the internal network adapter on the server that is running Windows SBS 2003. Remove all other DNS entries.
Back to the top

STATUS

This behavior is by design.
Back to the top
APPLIES TO
  • Microsoft Windows Small Business Server 2003 Standard Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
Back to the top
Keywords: 
kbprb KB837369
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Chris - chris NOSPAM-AT-NOSPAM huycom.com Reported as Irrelevant  
Written: 7/16/2004 5:44 AM
I have been experiencing this very problem after suffering a server crash and rebuild. The prescribed remedy here has no effect what-so-ever. I am at my wits end. Has anybody else experienced this stubborn problem. The Server was installed leaving the the DHCP running at the router with DNS not active, DNS is active at the Server only. This system was working nicely prior to the crash but now it is totally damned. Has anybody else been through this agony!

Gary Baldwin - gary NOSPAM-AT-NOSPAM tunit.co.uk Reported as Irrelevant  
Written: 9/16/2004 8:44 AM
Hi Chris, please bear with me, I'm a mac head just delving into the arcane knowledge of sbs but I had the same problem and I resolved it by manually configuring the client XP machines, it was a domain problem... hope this helps

Rod Obi - Mister_tibs2002 NOSPAM-AT-NOSPAM yahoo.com Report As Irrelevant  
Written: 10/22/2004 12:29 PM
That worked great. Added the DNS server IP and it went thru fast. Thanks guys. Lata'

JD - lodarka NOSPAM-AT-NOSPAM hotmail.com Report As Irrelevant  
Written: 11/21/2004 8:44 PM
Perfect! and i didn't have to remove the other DNS entries as the resolution suggests...only had to move the server DNS to the top of the list.

Rob Report As Irrelevant  
Written: 12/10/2004 1:29 AM
Excellent. Worked just like it said it would. I only wasted 2 hours before I found this site!!!!

Lenny Reported as Irrelevant  
Written: 1/3/2005 9:25 AM
I have had the same issues try reinstalling the Client Deployment component on the server by using Microsoft Windows Small Business Server Setup, available in Add or Remove programs.

Mike Reported as Irrelevant  
Written: 2/13/2006 2:04 PM
Good to go. This assisted us and worked perfectly. We also just added the local SBS address at the top of the DNS entries, and it worked fine.

Leo Report As Irrelevant  
Written: 4/30/2006 2:53 AM
Great that was the exact issue, it worked immidiatly.... Thanx mate !!!!!!!

Frank Report As Irrelevant  
Written: 6/4/2006 9:15 PM
Thanks for the great information. I worked great!!!

Steve Report As Irrelevant  
Written: 10/18/2006 6:32 PM
Right on the money. Google brought me right here and changing the DNS to the IP of the server got me right in. Thx!



Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting