Can't join Win 2000 Pro Client to Win 2000 Adv Server Domain...

[thestriver]

No, you should fix them

Yes I've fixed them OK. However, we r back to the same issue. Network
name cannot be found while joining. In other words, we r back to the
point just before I ran that script from the internet. So we'r going
somewhere it looks like

The reason I said a reinstall would be better...coz...I'm new to this
thats why. I have no issues if we carry on troubleshooting till we get
to a point were we can find something. It is all the more more better
for me as I can learn more in the doing. Thanks.

 

[thestriver]

MUST override that external DNS setting -- optinally transferring the
value
to the DNS forwarder tab.

How do u do this?

 

[Herb Martin]

Herb asked for more info:

Server:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : hclc
Primary DNS Suffix . . . . . . . : hclc.net

This is a BAD thing. You have a server and the Domain
likely named with the same NetBIOS name and since it
is a DC you will have a lot of trouble changing that name.

It may not be the problem you are currently facing but it
isn't a good thing.

Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hclc.net

Ethernet adapter Private:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139A/B/C/D RTL81XX
10/100Mbps Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-00-E8-50-2B-A5

DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1

This should be the ONLY value used for the DNS server
on EITHER NIC.

Ethernet adapter Public:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-11-11-26-8E-71
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 110.7.4.51
Subnet Mask . . . . . . . . . . . : 255.0.0.0

That is a REALLY odd mask did you ISP really give you that
value to use?

255.255.255.0 would be MUCH more likely to be correct --
but there is no way I can actually tell without talking to the
ISP.

It's is difficult to imagine the ISP would use a Class A address
AND not subnet it down to 254 nodes per network OR LESS.

BUT then, that 110 address doesn't seem to be a publicly assigned
range anyway. Whois says not, and it is unroutable from the Internet.

Default Gateway . . . . . . . . . : 110.7.4.1
DNS Servers . . . . . . . . . . . : 213.197.128.5
213.122.63.142
110.7.4.1

There's your problem right there -- as I predicted.

You need to remove these DNS servers from the NIC.

(Put them in the DNS SERVER MMC property for
Forwarding if you wish -- but right them down somewhere
so you will know them if/when you need them.)

Client:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : hclc-client
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RTL8139A/B/C/D RTL81xx 10/100Mbps
PCI Adapter
Physical Address. . . . . . . . . : 00-00-E8-50-2D-4F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.0.0.0

Legal but odd that you have different mask on the
Client and DC -- this is NOT actually a problem but
it looks goofy.

Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

You probably cannot route through the server since it
doesn't seem to have routing enabled, but that wasn't
what you asked about.

From you other message you quoted me and then asked...

How do u do this?

Open the External NIC properties in Network and Dial-up connections, IP
Properties -> erase the DNS entry. (Write them down first.)

Open the DNS MMC (Start->Run->dnsmgmt.msc -- right click on the
SERVER->Properties-->Forwarder tab: Add them there if you wish.
(It's likely a good idea.)

Who is your ISP?

 

[Herb Martin]

No, you should fix them

Yes I've fixed them OK. However, we r back to the same issue. Network
name cannot be found while joining. In other words, we r back to the
point just before I ran that script from the internet. So we'r going
somewhere it looks like

Yes. This time you are going to fix those NIC->DNS server entries.

The reason I said a reinstall would be better...coz...I'm new to this
thats why.

That doesn't make it better to re-install when you are not able to just
change one or two settings and fix the problem.

You would just be flailing -- and likely just type those bad entries
back into the same place unless you first understand how to do it
right. (The only reason that even APPROACHES needing a re-install
is that your DC is named the same as the NetBIOS name of the
Domain. You MIGHT decide to DCPromo->Non-DC, rename
DC, then DCPromo (again) back to DC.)

No need or even value in a full re-install.

I have no issues if we carry on troubleshooting till we get
to a point were we can find something. It is all the more more better
for me as I can learn more in the doing. Thanks.

We JUST STARTED troubleshooting -- I guess the problem the problem
five messages ago, but you just now got around to posting the IPConfig
and confirming my guess.

Just fix the problem.

Then go through my DNS for AD checklist and either check/fix each
item or ask a question until you understand what each item means....


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 /serverC-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: ]

 

[thestriver]

1) Dynamic for the zone supporting AD

Already set to Secure updates.

2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)

I'm sure it specified so...going by ipconfig result on Client in my
message above. I've also made similar the Subnet mask of both, the
Private NIC (See IPConfig result above) & Client to 255.0.0.0. Also,
Enabled Router & Remote Access.

3) DCs and even DNS servers are DNS clients too -- see #2

If I specify the same IP/NIC values that is present now in the server's
Private NIC (See IPConfig result above), to both the NIC's, then will
it allow internet accessibility? I guess you mean to say that both
NIC's have to have the same values in IP/NIC? But will it allow me to
access the internet then?
It could also mean that there is no need for the second NIC if internet
connectivity is not required, correct? But, it is reqd as I need to
access internet also.
Is there a workaround so that I could access the internet as well? FYI,
I have only 1 Server & 1 Client.

4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or
indirectly)

As I mentioned earlier...there is only 1 Server & 1 Client, both
connected through cross over cable. So there is only 1 domain & 1 DNS
Server (Both on the same Win2000 Adv Server)

 

[thestriver]

You have a server and the Domain likely named with the same NetBIOS
name and since it is a DC you will have a lot of trouble changing that
name.

Is there a way to find out the netbios name? In the hindsight, while
installing AD using dcpromo, there was an option to specify a NETBIOS
name & I'd specfified the name as 'HCLC1' coz for some reason it was
accepting the name 'HCLC'

There's your problem right there -- as I predicted.
You need to remove these DNS servers from the NIC.
(Put them in the DNS SERVER MMC property for
Forwarding if you wish -- but right them down somewhere
so you will know them if/when you need them.)

Done + forwarding.

 

[thestriver]

Latest IPConfig Result:

Server:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : hclc
Primary DNS Suffix . . . . . . . : hclc.net
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hclc.net

Ethernet adapter Private:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139A/B/C/D RTL81XX
10/100Mbps Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-00-E8-50-2B-A5

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.1

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.0.1

Ethernet adapter Public:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-11-11-26-8E-71

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.5.5.54

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . : 10.5.5.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

FYI...these are original values from public as is...earlier I had
changed the values to prevent hack as this site is not secured.

Client:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : hclc-client
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RTL8139A/B/C/D RTL81xx 10/100Mbps
PCI Adapter
Physical Address. . . . . . . . . : 00-00-E8-50-2D-4F

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.2

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Note: The SM's are similar for client nic & private nic in server.

Also ran ran both netdiag & dcdiag, however error somes up in the
section where it tries to test the DNS...

DNS test . . . . . . . . . . . . . : Failed
[FATAL]: The DNS registration for 'hclc.hclc.net' is
incorrect on all DNS servers.
PASS - All the DNS entries for DC are registered on DNS server
'192.168.0.1' and other DCs also have some of the names registered.

DC list test . . . . . . . . . . . : Failed
Failed to enumerate DCs by using the browser.
[NERR_BadTransactConfig]

LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC 'hclc.hclc.net'.

 

[Herb Martin]

1) Dynamic for the zone supporting AD

Already set to Secure updates.

Ok.

FYI: You really should adopt a sensible message 'quoting'
strategy. It will make you communication more efficient and
more effective in solving your problems.

2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)

I'm sure it specified so...going by ipconfig result on Client in my
message above. I've also made similar the Subnet mask of both, the
Private NIC (See IPConfig result above) & Client to 255.0.0.0. Also,
Enabled Router & Remote Access.

Ok. But the REAL ISSUE was that this was wrong on your DC.

3) DCs and even DNS servers are DNS clients too -- see #2

If I specify the same IP/NIC values that is present now in the server's
Private NIC (See IPConfig result above), to both the NIC's, then will
it allow internet accessibility?

Yes, of course. If you setup the DNS server correctly (e.g., as I
instructed or even if you let it recurse itself.)

I guess you mean to say that both
NIC's have to have the same values in IP/NIC?

No, what I said is they must ONLY specify the internal DNS
server (set). The 'other' NIC can specify the same, another
internal DNS (you don't have one though), or just be left
blank in some cases.

But will it allow me to access the internet then?

Of course -- as long as the INTERNAL DNS server can resolve the
Internet -- and you cannot "mix" them in any case so it isn't a real
choice.

It could also mean that there is no need for the second NIC if internet
connectivity is not required, correct? But, it is reqd as I need to
access internet also.

Resolves INTERNET DNS this way:

DC --> Internal DNS (happens to be on same DC) --> Resolves the
Internet (through forwarding to ISP or recursion using Root Hints.)

Is there a workaround so that I could access the internet as well? FYI,
I have only 1 Server & 1 Client.

Yes. You can use NAT (Part of RRAS) on the Server or perhaps better
go out and buy one of those little $20-80 "router/firewall/hubs" and hook
both machines to it so they are not exposed directly on the Internet.

4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or
indirectly)

As I mentioned earlier...there is only 1 Server & 1 Client, both
connected through cross over cable. So there is only 1 domain & 1 DNS
Server (Both on the same Win2000 Adv Server)

Right. But it emphasizes that your internal DNS CLIENTS (all internal
machines really) must resolve ALL internal names and use only the
INTERNAL DNS Server (set) which can resolve all of these names.

Did you go through the repair procedures after fixing the Server NIC?

Did you actually fix the server NIC yet?

(I saw your DCDiag output above, but there is no point in going through
half of my checklist, stopping and not telling me if you did the OTHER
things indicate instead of making me tall you each one in a new round
of several messages and replies.)

You need to REGISTER the DC in it's DNS server database -- DCDiag /FIX
and/or NetDIAG /fix and Restarting NetLogon and then if necessary
reading the article and just FIXING the registration.

 

[thestriver]

Of course -- as long as the INTERNAL DNS server can resolve the
Internet -- and you cannot "mix" them in any case so it isn't a real
choice.

After removing & forwarding the external nic dns names ...internet is
accessible now.

Yes. You can use NAT (Part of RRAS) on the Server or perhaps better
go out and buy one of those little $20-80 "router/firewall/hubs" and
hook
both machines to it so they are not exposed directly on the Internet.

Forwarding has helped accessibility to internet now. So, NAT not reqd I
guess.

Did you go through the repair procedures after fixing the Server NIC?

I had run both dcdiag /fix & netdiag /fix. A few errors there though.
The results r in the previous message. What are the 'repair procedures'
that need to be done now after fixing the server NIC?

Did you actually fix the server NIC yet?

Are you referring to running dcdiag or netdiag..then I've already done
that. Plz clarify.

You need to REGISTER the DC in it's DNS server database -- DCDiag /FIX
and/or NetDIAG /fix and Restarting NetLogon and then if necessary
reading the article and just FIXING the registration.

Already done. Infact whenever I modify anything, I go through this
ritual of flush, register, stop & start netlogon, to refresh & update
the dns.

(I saw your DCDiag output above, but there is no point in going through
half of my checklist, stopping and not telling me if you did the OTHER
things indicate instead of making me tall you each one in a new round
of several messages and replies.)

I'd religiously followed that checklist you had given in earlier
message, 1 after the other

Its the same news on Client--Network name cannot be found ---while
joining !!!

Is it reqd at this stage to have a look at dsa.msc & find out the users
& client I've added there & their properties?
y is the errors & warings coming up in dcdiag & netdiag result in
mesage above? I've done everthing till date that you have told?