Server is Not Recognizing the FQDN

[Guest]

Hello,

I need some help. We currently have 3 DC's in our network. I had all three
of them in the Domain Controllers Organizational Unit in Active Directory. I
needed to change some Group Policies on our Terminal Services Server, so I
followed some instructions from Microsoft to move the TS Server into it's own
OU. I created the "Terminal Services" OU, moved the server into it, and
created it's own set of Group Policies. Everything appeared to be working
fine. However, now our Exchange server (also the PDC) no longer recognizes
it's FQDN, and I am receiving a DNS error 414 "The DNS Server machine
currently has no DNS domain name".

Here are the things that I have tried:

I removed the Primary DNS suffix from the Computer and rebooted. I then
replaced the Primary DNS suffix, and rebooted again.

I deleted the DNS records that showed the server as ServerX, rather than
ServerX.domainname.com, I flushed and registered DNS using the ipconfig
command, I then stopped and started both the Netlogon and DNS services.

I then used Article ID 888048 from Microsoft and followed all of the steps
to resolve this problem (including recreating registry entries).

Finally, I removed the check marks from the Register DNS Information from
the Loal Area Connection properties and again flushed and registered DNS, and
stopped and started Netlogon and DNS. I then put the check marks back in and
completed the above commands again.

Has anybody ever had this problem? Does anybody know how to fix it?

Thanks in advance for any help you can offer.

 

[Herb Martin]

Hello,

I need some help. We currently have 3 DC's in our network. I had all
three
of them in the Domain Controllers Organizational Unit in Active Directory.
I
needed to change some Group Policies on our Terminal Services Server, so I
followed some instructions from Microsoft to move the TS Server into it's
own
OU.

It is generally a (very) bad idea to move a DC outside
of the DC OU -- if you mean that this TS is also a DC
I would (strongly) advise against such moves.

In theory this should be possible, but my experience, and
communications with others on these newsgroups, confirms
this does NOT give good results.

I created the "Terminal Services" OU, moved the server into it, and
created it's own set of Group Policies. Everything appeared to be working
fine. However, now our Exchange server (also the PDC) no longer
recognizes
it's FQDN, and I am receiving a DNS error 414 "The DNS Server machine
currently has no DNS domain name".

Here are the things that I have tried:

I removed the Primary DNS suffix from the Computer and rebooted. I then
replaced the Primary DNS suffix, and rebooted again.

You mean on the NIC? This isn't effective for DCs
and if it were should NOT be used to make such
changes.

The Computers REAL NAME is in the System Control
Panel (and usually cannot be changed for a DC).

I deleted the DNS records that showed the server as ServerX, rather than
ServerX.domainname.com, I flushed and registered DNS using the ipconfig
command, I then stopped and started both the Netlogon and DNS services.

IPConfig /registerDNS is INSUFFICIENT for a DC.

You must stop/start the NetLogon Service to correct a
DC but you really shouldn't be messing with these settings
on a DC IF they were WORKING.

I then used Article ID 888048 from Microsoft and followed all of the steps
to resolve this problem (including recreating registry entries).

Finally, I removed the check marks from the Register DNS Information from
the Loal Area Connection properties and again flushed and registered DNS,
and
stopped and started Netlogon and DNS. I then put the check marks back in
and
completed the above commands again.

Has anybody ever had this problem? Does anybody know how to fix it?

Is this a DC? Put it back they way it was (working) and
use a separate server for the Terminal Server.