Can computer join domain without a DNS Server - How?

  • Thread starter Thread starter Ohaya
  • Start date Start date
O

Ohaya

Hi,

I have Win2K Advanced Server, configured as a DC. I have another Win2K
Pro machine that I want to join/add to this domain.

I have not configured a DNS server on the DC, and I'd prefer not to.

I have added the Win2K Pro machine to "Computers", and have a User, on
the DC, but when I try to join the domain, I get "The domain name xxx is
invalid or does not exist".

I found some older posts, and I've added entries in my hosts file:

192.168.0.6 DCName #PRE #DOM:MYDOMAIN.COM
192.168.0.6 "MYDOMAIN.COM \0x1b" #PRE

And, I've done the "nbtstat -c"

My "nbtstat -R" looks like:

Local Area Connection:
Node IpAddress: [192.168.0.3] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
DCNAME <03> UNIQUE 192.168.0.6 -1
DCNAME <00> UNIQUE 192.168.0.6 -1
DCNAME <20> UNIQUE 192.168.0.6 -1
MYDOMAIN.COM <1C> GROUP 192.168.0.6 -1
MYDOMAIN.COM <1B> UNIQUE 192.168.0.6 -1

I thought that getting the '<1B>' was the trick to get this working, but
still, no joy :(.

Can anyone tell me how I can accomplish this?

Thanks in advance!!

Jim
 
Dns is a requirement for an Active Directory domain. It is not hard to configure at
all. The workstation is looking for the _srv records such as
_ldap._tcp.dc._msdcs.yourdomain.com and can not find them which is why it can not
join the domain. Run dcdiag on your domain controller to see all the failed tests
that will show without dns installed. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
 
Steven,

I have the impression, from posts like:

http://groups.google.com/groups?hl=...ie=UTF-8&oe=UTF-8&q=cannot+join+domain+lmhost

that it is possible to configure things so that this would work, without
setting up a DNS server.

FYI, here's what's I'm getting in Netsetup.log:

10/28 18:20:03 NetpValidateName: checking to see if 'MYDOMAIN.COM' is
valid as type 3 name
10/28 18:20:18 NetpCheckDomainNameIsValid for MYDOMAIN.COM returned
0x54b
10/28 18:20:18 NetpCheckDomainNameIsValid [ Exists ] for 'MYDOMAIN.COM'
returned 0x54b


Can anyone tell me what else I need to do to get this working?

Thanks,
Jim


Dns is a requirement for an Active Directory domain. It is not hard to configure at
all. The workstation is looking for the _srv records such as
_ldap._tcp.dc._msdcs.yourdomain.com and can not find them which is why it can not
join the domain. Run dcdiag on your domain controller to see all the failed tests
that will show without dns installed. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

Ohaya said:
Hi,

I have Win2K Advanced Server, configured as a DC. I have another Win2K
Pro machine that I want to join/add to this domain.

I have not configured a DNS server on the DC, and I'd prefer not to.

I have added the Win2K Pro machine to "Computers", and have a User, on
the DC, but when I try to join the domain, I get "The domain name xxx is
invalid or does not exist".

I found some older posts, and I've added entries in my hosts file:

192.168.0.6 DCName #PRE #DOM:MYDOMAIN.COM
192.168.0.6 "MYDOMAIN.COM \0x1b" #PRE

And, I've done the "nbtstat -c"

My "nbtstat -R" looks like:

Local Area Connection:
Node IpAddress: [192.168.0.3] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
DCNAME <03> UNIQUE 192.168.0.6 -1
DCNAME <00> UNIQUE 192.168.0.6 -1
DCNAME <20> UNIQUE 192.168.0.6 -1
MYDOMAIN.COM <1C> GROUP 192.168.0.6 -1
MYDOMAIN.COM <1B> UNIQUE 192.168.0.6 -1

I thought that getting the '<1B>' was the trick to get this working, but
still, no joy :(.

Can anyone tell me how I can accomplish this?

Thanks in advance!!

Jim
Click to expand...
Click to expand...
 
A windows 2000 Domain requires DNS no if ands or buts about it. You may "and
that is a big may" be able to get it to half ass work by hacking it all over
the place but I can 100% guarantee that you will have an endless list of
problems. Installing DNS is far less time consuming then issues you will
create by not doing so. I am still in awe of how you ran DCpromo on the AD
server with out a DNS server.


Ohaya said:
Steven,

I have the impression, from posts like:

http://groups.google.com/groups?hl=...ie=UTF-8&oe=UTF-8&q=cannot+join+domain+lmhost

that it is possible to configure things so that this would work, without
setting up a DNS server.

FYI, here's what's I'm getting in Netsetup.log:

10/28 18:20:03 NetpValidateName: checking to see if 'MYDOMAIN.COM' is
valid as type 3 name
10/28 18:20:18 NetpCheckDomainNameIsValid for MYDOMAIN.COM returned
0x54b
10/28 18:20:18 NetpCheckDomainNameIsValid [ Exists ] for 'MYDOMAIN.COM'
returned 0x54b


Can anyone tell me what else I need to do to get this working?

Thanks,
Jim


Dns is a requirement for an Active Directory domain. It is not hard to configure at
all. The workstation is looking for the _srv records such as
_ldap._tcp.dc._msdcs.yourdomain.com and can not find them which is why it can not
join the domain. Run dcdiag on your domain controller to see all the failed tests
that will show without dns installed. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

Ohaya said:
Hi,

I have Win2K Advanced Server, configured as a DC. I have another Win2K
Pro machine that I want to join/add to this domain.

I have not configured a DNS server on the DC, and I'd prefer not to.

I have added the Win2K Pro machine to "Computers", and have a User, on
the DC, but when I try to join the domain, I get "The domain name xxx is
invalid or does not exist".

I found some older posts, and I've added entries in my hosts file:

192.168.0.6 DCName #PRE #DOM:MYDOMAIN.COM
192.168.0.6 "MYDOMAIN.COM \0x1b" #PRE

And, I've done the "nbtstat -c"

My "nbtstat -R" looks like:

Local Area Connection:
Node IpAddress: [192.168.0.3] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
DCNAME <03> UNIQUE 192.168.0.6 -1
DCNAME <00> UNIQUE 192.168.0.6 -1
DCNAME <20> UNIQUE 192.168.0.6 -1
MYDOMAIN.COM <1C> GROUP 192.168.0.6 -1
MYDOMAIN.COM <1B> UNIQUE 192.168.0.6 -1

I thought that getting the '<1B>' was the trick to get this working, but
still, no joy :(.

Can anyone tell me how I can accomplish this?

Thanks in advance!!

Jim
Click to expand...
Click to expand...
Click to expand...
 
Hi! Ohaya,

Why would you like without DNS?
Of course, You can make it without DNS
in case your network is so small with few PC's
and simple one.
With DNS it is much much easier for you to make it, I believe.)
Why do you hate DNS?

By Ormand,
 
Ormand et al,

I guess I should've possibly explained my situation a bit more.

It's not that I "hate DNS" :).

It's just that I am trying to set up a very small test network, and I'm
trying to configure the Win2K Server machine to be as close to the
configuration that is set up at a company that I'm working with (they
don't have DNS Server setup on their DC).

I was/am worried that, if I install DNS Server on the Win2K server, this
may affect some things that I'm testing, so I'm trying to avoid it if I
can, so when I found that article that I posted a link to (but haven't
been able to make work), I was hopeful.

So, to summarize, I understand that the easiest way to go would be to
install DNS on the Win2K Server.

It also appears to be possible to do this without doing that, and you
indicate the same also. I've posted info that I thought would be
helpful in diagnosing what I'm doing wrong. Can you or anyone else help
getting this working?

Thanks,
Jim
 
Hi,

Well, I decided to image my drive (so I could get back if something went
awry), and installed DNS, and was able to join the domain.

But now, I am still having a problem with using MMC snap-in to remotely
control IIS, which I'll post separately.

Thanks!
 
Back
Top