configure your dns server

  • Thread starter Thread starter NetGear
  • Start date Start date
N

NetGear

Hi,

Did an in-place-upgrade from Winnt 4.0 domain to Windows 2000 active
directory.

The upgrade process lost my network interface card (Intel 1000/XT Gbit
adapter) and I had to cancel the DDNS installation. After cancelled dns
installation I installed the correspond nic driver and rebooted.

After reboot I succesfully installed and configured the dns server. When I
run dcidiag.exe and netdiag.exe I get no meaningful errors. Also the dynamic
updates work correctly. However, when I open the dns mmc, it always opens
with the wizard that tells me that I should configure my dns server.

How can I tell my dns service mmc that the service is already configured?

I'm running a mixed mode domain. It seems that when a Windows 2000 client
authenticates with a Winnt BDC, the client can not see the Directory entry
in the network neighforhood. Is it possible to solve this problem also?
 
In
NetGear said:
Hi,

Did an in-place-upgrade from Winnt 4.0 domain to Windows 2000 active
directory.

The upgrade process lost my network interface card (Intel 1000/XT Gbit
adapter) and I had to cancel the DDNS installation. After cancelled
dns installation I installed the correspond nic driver and rebooted.

After reboot I succesfully installed and configured the dns server.
When I run dcidiag.exe and netdiag.exe I get no meaningful errors.
Also the dynamic updates work correctly. However, when I open the dns
mmc, it always opens with the wizard that tells me that I should
configure my dns server.

How can I tell my dns service mmc that the service is already
configured?


Configure server message is just a cosmetic message (not an error). To make
it disappear, install the WIndows 2000 Support Tools (found on the CDROM
under Suppor folder), then run this command in a cmd prompt:
dnscmd /Config /AdminConfigured 1

I'm running a mixed mode domain. It seems that when a Windows 2000
client authenticates with a Winnt BDC, the client can not see the
Directory entry in the network neighforhood. Is it possible to solve
this problem also?


Not sure what you mean by the "directory entry" in network neighborhood? Do
you mean the server (W2k or NT4?) in the browse list or the client? Keep in
mind, if a machine was just rebooted, it may take upto 15 minutes for the
list to populate the change. If across a subnet (such as having multiple
locations), you will need WINS since Network Neighborhood and the browse
service is based on NetBIOS and NOT DNS.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
"Ace Fekay [MVP]"
In NetGear <[email protected]> posted their thoughts, then I offered mine
Configure server message is just a cosmetic message (not an error). To make
it disappear, install the WIndows 2000 Support Tools (found on the CDROM
under Suppor folder), then run this command in a cmd prompt:
dnscmd /Config /AdminConfigured 1
Thanks!

Not sure what you mean by the "directory entry" in network neighborhood? Do
you mean the server (W2k or NT4?) in the browse list or the client? Keep
in

Sorry. I meant the Active Directory icon in "My network places". If my W2K
users authenticate with BDC, that icon does not apperar there.

Also when W2K user logs on to network via the BDC, the user can not search
the AD. There is a message that says that the directory service can not be
contacted.

When the netlogon happens through the Ad DC, everything works fine. BDC dns
settings point to AD DNS server and there are both A and PTR records created
for them.
 
Do all the clients also only point to the AD's DNS server only?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Interesting issue. I actually haven't come across this. How did you
determine what logon server logged them in? Did you use the %logonserver%
variable?

Also of interest, FYI, once a Win2k or XP machines gets authenticated thru a
W2k domain controller, then the authentication now changes to Kerberos from
NTLM and won't go back to NTLM. To alter that behavior, would require to
disjoin the machine and rejoin the machine while unplugging the W2k DC.
There's actually a tech article on that and was an issue during
migrations/upgrades.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top