Archived from groups: microsoft.public.win2000.active_directory (
More info?)
"thestriver" <searchhere@gmail.com> wrote in message
news:1122837749.183638.53650@f14g2000cwb.googlegroups.com...
> 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.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Facebook
Twitter
Instagram