Re: Cannot add new user in Win 2003 standard



"TerryB" <TerryB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF894E1C-9B67-416D-8EB1-659923294F15@xxxxxxxxxxxxxxxx
Actually I have a strong password. But funny thing, I rebooted and the
problem went away... go figure


Most authentication (and replication) problems in AD
domains are due to DNS issues.

When the problem goes away on reboot you should strongly
suspect that the CLIENT machine is set to use multiple DNS
servers (from different places) that don't return the same info,
e.g., the ISP and the INTERNAL DNS servers.

Internal Clients must use STRICTLY the (internal) DNS server
that can return all of the answers they will need.

Check: NIC->IP properties for the DNS servers or just do
"IPConfig /all" to view the settings (using the latter is
pretty much required if you the machine is a "DHCP client".)

As second, less likely issue is a replication problem where
one of your DCs is not fully replicated or not represented with
all DNS servers (i.e., the DNS servers are not fully replicated).

For these latter issue, check EACH DC with DCDiag and resolve
any problems it suggests (best to always dump DCDiag output
to a text file and just search it with a text editor.)


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

"Trimelater" wrote:

Terry,

Sound like your password is not long or secure enought. Try using 9
characters where you have one letter that is cap and one number or
combination. Not sure if this will help or not.

"TerryB" wrote:

I get the following error when trying to add a new user.

Windows cannot set the password for "user" The specified network name
is no
longer available.

Using Active Directory

I was able to add one user, then after installing and removing
Sharepoint
Services, I was no longer able to add any additional users.

Any Ideas?




.



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • RE: DNS/AD/RPC issues (x posted to .dns)
    ... You are right that an error like this is usually caused by a DNS problem. ... subnet - although replication is not functioning. ... (The DNS server could not bind a Transmission Control ... From DC3SRVR to DC1SRVR ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS in 2003 Domain
    ... Our Forest Root is 2003, and we have a mixture of Win ... > directory partition is available (but not on the 2000 DNS boxes). ... > correct in thinking to set this up though, all DNS servers should be ... along with the default AD replication cycle, since they are part of the AD ...
    (microsoft.public.win2000.dns)
  • Re: Problems with AD & DNS
    ... the IP and dns details on the server are correct. ... This article contains details on how to troubleshoot AD replication issues: ... EventID: 0xC0250827 ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.active_directory)