Re: Connect Computer - Not successful after Numerous Attempts

From: Steve Foster [SBS MVP] (steve.foster_at_picamar.co.uk)
Date: 06/10/04 

Date: Thu, 10 Jun 2004 08:07:57 -0700

Richard wrote:

> I's appreciate any help someone could give me on this.
>
> I have set up a SBS 2003 Network with about four users.
> I used the wizards through Server Management to create
> the user and computer accounts. I was able to get two
> clients up successfully (one that actually renamed the
> client computer name and the other i actually created the
> computer account thru the server)however, I am unable to
> get the third one going.
>
> I have run the client config so many times from a browser
> on the client and that process goes through partially and
> creates a user account on the client named
> __sbs_netsetup__ (ComputerAdmin-Password Protected)
> (Password?). The client never actually finishes the
> configuration and the company web site reflects an error
> connecting to the network. The user account still
> remains on the client. I have deleted and tried again
> but with the same results.

This is a temporary account used for the migration process (you can't
copy a user profile while logged in as that user!).

> When I try to connect to domain through My Computer--
> Properties--Computer Name--Network ID or Change Buttons:
> I get a response stating: "A domain controller for the
> domain X could not be found. Domain Name X might be a
> netbios domain name. If certain that name is not a
> netbios domain name then the following can help:
> following error occurred when DNS was queried for the
> Service Location (SRV) resource record used to locate a
> domain controller for domain X. Error was: DNS Name does
> not exist. Error Code: 0x0000232B RCODE_NAME_ERROR.

That means the desktop is unable to find all the local DNS records it
needs to (principally it can't identify the server as being the DC).

> At the client desktop the dns is pointing to A)our
> SBS2003 DNS Server, B)our Primary DNS Server IP from ISP,
> and C) our Secondary DNS Server IP from ISP. It receives
> its IP through DHCP running from a Firewall Hardware
> Device. Everything in the LAN Connection properties
> appears correct and alike to the other two connected
> computers on the network.
> HELP!

Firstly, get rid of all DNS entries but the SBS. Internal clients
should only point to the SBS for DNS. It will handle forwarding
requests out to the net as needed automatically.

Secondly, check that the SBS <domain.local> DNS zone has all the right
records - there should be a whole bunch of records in the _msdcs
sub-zone. If you don't have _msdcs, you need to fix this - quickest way
is to make sure the SBS points to itself for DNS in the nic properties,
then do "net stop netlogon" immediately followed by "net start
netlogon" from a command prompt. The relevant DNS entries should then
get re-created by the netlogon service. 

-- 
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.