Domain naming and DNS

[CJHarmon]

I inherited an NT4.0 domain that was upgraded to 2K and
underscores were used in the server's names and domain.
When I do a NETDIAG, it passes the DNS test, but gives the
DNS_ERROR_NON_RFC_NAME. Any suggestions on a 3rd party
tool to handle changing names. I am looking closely at
this problem as I purchased a 3rd party tool to push out
updates, etc., and am getting RPC Server Unavailable error
messages. The company is stumped; therefore, everything
in Microsoft RPC errors points to DNS even though I am
able to resolve names easily.

Any Help would be greatly appreciate.

 

[Steve Duff [MVP]]

Renaming domains can be done in theory at least
using the Win2K domain rename tool available at
Microsoft downloads. The one there now shows Win2003,
and I don't know what's happened to the older one
for Win2K -- hunt around.

Renaming domain controllers isn't possible unless
you have another server handy or are still running
AD compatibility-mode for NT. Start with this link:

http://support.microsoft.com/?id=296592

Before you start doing this though, I'd want to in fact verify
that the underscores really are the issue. Active Directory
uses underscores extensively, and non-RFC names
really shouldn't be a Big Deal to any software that
purports to run on Win2K domains. (It can be a big deal
to downlevel software and client o/s-en.)

Steve Duff, MCSE
Ergodic Systems, Inc.

 

[Ace Fekay [MVP]]

To add, the problem could be a space in the name, as was commonly used in
MAC or Win9x/NT days. Spaces will generally cause this error too.

If Aram can check the Event log error message, it usually tells you what IP
address is the culprit.

--
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

 

[Michael Johnston [MSFT]]

The underscores are probably not the source of the RPC errors. You can typically ignore the netdiag repor that indicates this is a non RFC name. Windows
2000 allows for this. What are the exact errors shown when RPC fails? Make sure that all machines only point at the Windows 2000 DNS server only. Verify
that the DNS server has the proper forward lookup zone and this zone allows dynamic updates.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.