DNS Issues

[vish]

Hi Guys

My PDC server name is XX_CORP_BDC2 and domain name is
DOM_CORP

4 months back I upgraded my PDC server to windows 2000 and created
the active directory with same server name and domain

name . I unable
to

change my server name in dns supported format because all my users
storing and accessing files like this format \\xx_corp_bdc2\file name
. So still the server name exist with non
supported DNS character ( - )

3) In that same server DNS server was created and it is active
directory integrated with dynamic updated setting.

4) After that we are facing problem is that we can't add any member
server (win2k server) or win2k professional to that domain but we can
add NT 4.0 server or NT4.0 workstation suceessfully. If

you going to
add

Win2k server it will ask the user name and password and after enter the
user name and password it gives the error that network path not found .
I tried with Netdom utility also i got the same error.

5) I added the win2k member server or professional to the another
win2k
resource domain DOM-ARTHUR and with NETDOM MOVE command , I moved the
win2k member server to that upgraded domain DOM_CORP . This way I can
add the Win2k server or win2k professional to the domain DOM_CORP but I
can't directly add the win2k server or win2k professinal to that domain
DOM_CORP but I can move Win2k member server or professional from one
domain to DOM_CORP domain.

6) I run the diagnosed tool Dcdiag .exe in the domain

DOM_CORP and
I

am
getting the following error

"
DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\XX_CORP_BDC2
Starting test: Connectivity
XX_CORP_BDC2'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

(fdba96f1-0634-4742-881a- 0fed9ef21c36._msdcs.DOM_CORP)
couldn't
be

resolved, the server name

(xx_corp_bdc2.DOM_CORP) resolved to

the IP

address (172.16.0.30) and was pingable. Check that the IP
address is

registered correctly with the DNS server.
......................... XX_CORP_BDC2 failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\XX_CORP_BDC2
Skipping all tests, because server XX_CORP_BDC2 is
not responding to directory service requests

Running enterprise tests on : DOM_CORP
Starting test: Intersite
......................... DOM_CORP passed test Intersite
Starting test: FsmoCheck
......................... DOM_CORP passed test FsmoCheck "

I am on conclusion that this problem due to DNS but I
unable to find out the solution to resolve this problem.

Second problem I am facing in my domain is I can't add the global
group or user into the local group .Because of this problem in share
point portal server I can't add domain server's global group or user
account into the portal server . and while adding i getting the
following error

" Processing of object user failed with the following error . The
RPC server is unavailable."

I had searched the internet to findout the solution for above
problem but my bad luck there was no solution on the internet for this
problem.

I used the below utility from resource kit and succeed in that
operation but it is difficut to manage because my global groups are
created in this way like g_b&m Infouser and this can't be add through
command prompt , the reason is that the space between g_b&m infouser
and every time managing groups by command prompt is not possible
cusrmgr.exe -m \\ remotecomputer -alg localgroup -u globalgroup


Can your side expert give me the solution for following two problem
1) Adding win2k member server and win2k professional to my main domain
DOM_CORP
2) Adding global group into the local group

Thanks and regards

Vishal

 

[Ace Fekay [MVP]]

In

Hi Guys

My PDC server name is XX_CORP_BDC2 and domain name is
DOM_CORP
name . I unable
to
you going to
add
DOM_CORP and
I
be resolved to
an
(xx_corp_bdc2.DOM_CORP) resolved to


Thanks and regards

Vishal

The cardinal rule is to only use your own internal DNS server and no others.
No ISP's or any other external DNS server. This needs to be followed for
every machine in your network, DCs, member servers and clients. If you use
an ISP's, lots of things go wrong, such as what you're esperiencing.

If you want Internet name resolution, use a forwarder:
http://support.microsoft.com/?id=300202

If grayed out, delete the root zone. The article shows how too.

Once this is done, restart your machine and then try again and guarantee the
errors will go away.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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