Re: Cannot join client PC to domain



Hello John,

Nice to hear, that you find it.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Found it:

http://support.microsoft.com/kb/258500

:(

"Robert Bollinger" <RobertBollinger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:33E1E0AE-98D3-4DA0-A668-E7C9F19740A3@xxxxxxxxxxxxxxxx

some questions...

Do you only have 2 machines?

if you run dcdiag on the server does it pass? (support tools will
need to
be
installed)
have you tired joining like this: testdomain.com ?

I have seen where windows will fail on joining the domain using the
netbios
based domain name (testdomain)
you can also run netdiag and and see if it passes ...

assuming you have done basic troubleshooting, such as verifying
connectivity, pinging etc. this sounds like a dns issue. to me.

I would try joing with testdomin.com (btw, you should never use a
resolvable
.COM, .NET, etc TLD when setitng up your DC).
Also make sure to disable the WIndows server firewall for this test.

RObert

"John Straumann" wrote:

HI all:

I am trying to join a client to a domain in a lab environment. The
server
IP
is set to 192.168.1.150, the client to 192.168.1.151, and I have the
client
primary DNS server set to 192.168.1.150. The server name is server1,
and
if
I open a command prompt on the server and type "nslookup server1"
the
name
resolves correctly. If I do the same thing on the client, I get an
error:
*** server1.testdomain.com can't find server1: Server failed"

and when I try to go into the Client properties to add the client to
the
domain, after I type the new domain info and click "OK" I get the
prompt
for
a username and password for and account with permission to join the
domain,
but when I enter the credentials and click OK again, I get an error:
"The following error occurred attempting to join the domain
"testdomain": The network path was not found"

In DNS on the server I have a Host (A) entry for 192.168.1.150, and
a reverse Pointer.

Can anyone make some suggestions to start tracking this down?

Thanks.

John.



.



Relevant Pages

  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: 70-294 next week
    ... to another DNS ... server for at least ... client, which then ... configuration on the client. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Dual NIC vs Single NIC
    ... |> 135919 DNS Server Search Order Functionality in Windows ... Thank you for helping me to correct the misunderstand of DNS query ... Thank you again for your supplement about the client DNS cache issue. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Dual NIC vs Single NIC
    ... I will again argue that turning off the client DNS cache (0 refresh ... 261968 Explanation of the Server List Management Feature in the Domain ... Internet when the SBS server is offline. ...
    (microsoft.public.windows.server.sbs)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)