DNS setup error

[baz]

I am trying to set up a new 2k server on a standalone
network, but appear to have problems loggin on from
clients. Have gone through various checks from KB articles
and on trying dcdiag /fix I got this response:

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: HB\EPOS
Starting test: Connectivity
EPOS's server GUID DNS name could not be resolved
to an
IP address. Check the DNS server, DHCP, server
name, etc
Although the Guid DNS name

(56539415-50c2-4b29-a02e-ad899772dc2e._msdcs.hb)
couldn't be resolved,

the server name (EPOS.hb) resolved to the IP
address (169.254.54.166)

and was pingable. Check that the IP address is
registered correctly

with the DNS server.
......................... EPOS failed test
Connectivity

Doing primary tests

Testing server: HB\EPOS
Skipping all tests, because server EPOS is
not responding to directory service requests

Running enterprise tests on : hb
Starting test: Intersite
......................... hb passed test Intersite
Starting test: FsmoCheck
......................... hb passed test FsmoCheck

Also in the forward zone of the DNS console some artclies
report that I should see SRV files, but cannot see any. I
have reloaded DNS but this has made no difference. Also
hould the Static IP address be the same for the server and
the DNS server?

Please help

 

[David Brandt [MSFT]]

A key question here is when you say "standalone network" do you mean a
workgroup, or was that just a matter of symantics and this is in a domain.

If domain, and this is a dc (your dcdiag below), point the server Only to
itself for dns in ip properties, and if any other address is also in there,
remove it and run the following cmd "ipconfig /flushdns".
Be sure that in the properties of the forward look up zone you created
(mydomainname.com etc) that the allow dynamics is set to yes (when you
create a standard primary zone it will default to no but ad intergrated will
be allow secure only which is ok)
I would Highly recommend that your domain name have a .com, .local, etc on
it (if at all possible since it looked like yours was hb) as with sp4 the
single label dns names won't register unless you make a registry change (see
below for info)
run cmd "ipconfig /registerdns"
Stop/restart the netlogon service or reboot the server and see if you then
see the 4 "_" folders under your forward look up zone (_msdcs, _sites, _udp,
and _tcp).
All other machines in the domain should then be pointed to this server for
dns.

300684 Information About Configuring Windows 2000 for Domains With
Single-Label
http://support.microsoft.com/?id=300684

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

 

[baz]

David,
thanks for replying. Yes, the server is in its own domain
as a DC.
I hadalready tried the various things you suggestted but
these did not reveal the missing SRV labels.
However you were right that I had just called the
domain 'HB'. How would I change the domain name to
say 'hb.local' if this would be ok.

Baz

 

[David Brandt [MSFT]]

It will take some work I'm afraid, and if you've moved to native mode from
mixed mode, with great difficulty.
2k3 allows for domain rename, but 2k doesn't. If still in mixed mode, you
could install an nt4 bdc, remove the 2k dc, then promote the bdc to pdc, and
during the upgrade to win2k select the dns domain name you want. The
current 2k dc will need to be force demoted (article below) or re-installed
and could then be rejoined to the domain as either server or additional dc
(and the former bdc now 2k dc demoted if desired etc)
If there are other win2k dc's in the domain currently, they would need to be
demoted to server prior to the forced removal of the last remaining one.
Note though, that once xp and 2k servers/clients detect that they are part
of a 2k domain, they will not want to authenticate against an nt4 dc anymore
(want kerberos authentication now) so will need to be removed form domain
and then re-joined to re-set them back to using netbios again. Depending on
how many servers/clients you have this could be quite a task.

332199 Using the DCPROMO /FORCEREMOVAL Command to Force the Demotion of
Active
http://support.microsoft.com/?id=332199

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

 

[BD]

I'm pretty much in the same boat here. I upgraded our NT4
domain to 2k and have since switched to native mode. Now
I realize that the second DC is not really a DC until all
of the DNS stuff in straightened out on the first DC. Is
there any way to get this domain name changes from a
single name to a name.local without have to completely
reinstall 2k server and recreate all of the users and
policies? Can I upgrade from 2k server to 2k server
and "start over"?