Re: Creating my first user accounts

I am trying to log onto the domain with the clients to have access to shared
files and access the internet. I feel I have done something incorrect in my
user setup such as joining them to the domain or something. this is my first
setup so I am not sure. Thanks for any help.


"Herb Martin" wrote:

"Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:88AC8693-C014-4942-8998-CB37DEFAB872@xxxxxxxxxxxxxxxx
I set up Micrsoft Server 2003. I let the wizards setup DHCP, DNS and AD.
I
created a few user accounts. I have 2 clients and the server connected by
an
inexpensive 10/100 switch. I can log in from any of the computers with
the
administrator account. I cannot log in with any of the created accounts.

Log into what specifically?

Each workstation must be a member of the domain and
you must pull down the menu at the Ctrl-Alt-Del dialog
that allows you to change from Computer to Domain (name)
accounts.

Normal users cannot login on a DC (or server for that matter),
only on workstations in the domain.

DNS is almost always the cause of authentication errors --
what DNS server is set on the clients? (Either in DHCP or
manually on the NIC->IP properties.)

What am i doing wrong? I even copied the administrator account and gave
the
copy a new login name. Only the default administrator account can login.

Where? Login at what machine? DC or workstation or
both? Where are the problems.

The other accounts get the reply, "the domain 'name' is unavailable.
Thanks for any help offered.

It's likely DNS (client side).

Did you alter the DNS server settings, or add the ISP
to your clients' settings? (You must NOT do that.)

All internal AD Client machines must use strictly the
INTERNAL DNS server (set).

Run DCDiag on your DC to check it and review the
following:


--
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



.

Relevant Pages

  • Re: Non-domain connection problem
    ... "Gregg Hill" wrote: ... You said that you "hard coded the DNS server to a known DNS on the ... Connect to Internet from external network ...
    (microsoft.public.windows.server.sbs)
  • Re: Added router, lost web site
    ... Did your ISP create a DNS record for your FQDN? ... > really have a direct connection. ... > Internet connection information: ... > Preferred DNS server: someisp DNS server address ...
    (microsoft.public.windows.server.sbs)
  • Re: Unix Bind and Windows DNS with Dynamic update issues!!!
    ... >> 2) All internal DNS clients NIC\IP properties must specify SOLELY ... >> we are running UNIX BIND as internal and external DNS server. ... > expose your sensitive internal information on the Internet. ... >> internal clients like Windows, Mac etc are pointing to UNIX BIND server to ...
    (microsoft.public.win2000.dns)
  • Re: Unix Bind and Windows DNS with Dynamic update issues!!!
    ... All internal DNS clients NIC\IP properties must specify SOLELY ... we are running UNIX BIND as internal and external DNS server. ... > for all but the largest (in terms of Internet presence) companies. ...
    (microsoft.public.win2000.dns)
  • Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain.
    ... You must have an internal DNS zone for each AD domain that is ... maintained separately from the Internet versions of these zone (if ... You need an INTERNAL DNS server for the zones. ... Herb Martin> tia ...
    (microsoft.public.windows.server.networking)
Loading