Re: connect XP pro to domain

"PAJ" wrote:

On Sun, 30 Mar 2008 08:22:38 +0100, "Misheck"
<mbemisheREMOVETHIS@xxxxxxx> wrote:

My computer is already called misheck1 and has computer account on the
contoso domain. I have logged on the computer as an administrator and tried
to join it to domain and when asked for a username and password I have
entered one that is in The domain controller, domain admin, admin and user
and all these have failed with same result wrong username and password. The
only thing I have noticed is that when I try to join to domain under system
properties and change name and when I select domain and enter (contoso.com)
that comes up with domain controller not found but when I enter (contoso)
which on the server01 pc is the Netbios name for computers before XP thats
accepted and proceeds me to the next screen where I have to enter a username
and password and thats where I get all the error messages.

First try and fix your DNS issues. Hopefully the DNS problem is just
because you are using your ISP's DNS (on the clients).
Change the DNS on the client to point to IP address of the server
(192.168.0.10). As has been suggested ensure you do not have two DHCP
severs running (disable the router one) and the clients should then pick
up the correct settings (including DNS).
Double check you are using a Valid 'domain account' and the password is
correct, because it appears that this is the issue.

This URL may be of some use to you:
http://support.microsoft.com/kb/825036

First thing first. You don't have to create a computer account in the
domain AD. Once you are able to join those XP machines to the domain, their
computer account will be created automatically.
Second, you definately have to check your DNS to be sure it's working
properly. Try test ping your server by using this command: ping -a
192.168.0.10 to see if it resolves the IP address to your server FQDN. If
it's not, then you have a problem with your DNS
.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)