Re: novice: problem adding second domain
From: Joe Ross (joeross252_at_hotmail.com)
Date: 02/05/04
- Next message: SergeL: "Wireless Router inside Network behind firewall"
- Previous message: Joe Ross: "Re: novice: problem adding second domain"
- In reply to: Joe Ross: "Re: novice: problem adding second domain"
- Next in thread: Kevin D. Goodknecht [MVP]: "Re: novice: problem adding second domain"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 5 Feb 2004 13:13:59 -0500
Kevin-
Currently, the new server is not part of any domain. Should I try to join
it to the existing domain before attempting to make it into a DC?
Just a thought
-joe
"Joe Ross" <joeross252@hotmail.com> wrote in message
news:uuoUVKB7DHA.2812@TK2MSFTNGP11.phx.gbl...
> See inline...
>
> "Kevin D. Goodknecht [MVP]" <admin@nospam.LSAOL.COM> wrote in message
> news:ePd0uzA7DHA.2168@TK2MSFTNGP12.phx.gbl...
> > In news:%238a1MZA7DHA.2752@TK2MSFTNGP09.phx.gbl,
> > Joe Ross <joeross252@hotmail.com> posted a question
> > Then Kevin replied below:
> > :: Is the new server using the current DC for DNS only in its NIC?
> > :: It must.
> > :
> > : I'm not certain I understand what you're saying.
> > :
> > : If you are asking if the NIC on the new server (it only has one), has
> > : it's TCP/IP DNS Server set to the IP of the existing DC...the answer
> > : is yes. I had to do that to get past the initial issues I was
> > : experiencing.
> > :
> > You got it that is it. You may need to flush the DNS cache with ipconfig
> > /flushdns.
>
> I tried this and it did not help.
>
> > IF that doesn't resolve the issue run nslookup (Netdig would be better
you
> > can get it here: http://www.mvptools.com/) on the new server to see if
it
> > can get DNS resolution from the current DC and if it is pingable and if
> > ports 53 UDP and TCP are open between them.
>
> I downloaded NetDig. What should I be checking? It comes up with the IP
of
> the current domain controller as the "Server" which seems to be correct.
I
> typed in yahoo.com and the status comes back as NOERROR with a query time
of
> 63ms and what appears to be a valid response. If I try to lookup any
> machines in the current DC's domain (including the DC itself), I get a
> failure:
>
> *************************
> opcode: QUERY, status: SERVFAIL, id: 23
> flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>
> QUESTION SECTION:
> flcscsrv01. IN A
>
> Query time: 63 ms
> Server : 192.168.30.10:53 udp (192.168.30.10)
> When : 2/5/2004 12:58:48 PM
> Size rcvd : 28
> *************************
>
> The current DC is pingable by IP but not by name from the new DC.
>
> > This is going to be a new domain in an existing forest or new domain
> > controller in an existing domain?
>
> I would like this to be a new domain in an existing forest.
>
> > Also looking at the error look in the Directory service Event log for
1656
> > events at start up on your DC you may be missing these reg entries.
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC\ClientProtocols]
> > "ncacn_np"="rpcrt4.dll"
> > "ncacn_ip_tcp"="rpcrt4.dll"
> > "ncadg_ip_udp"="rpcrt4.dll"
> > "ncacn_nb_tcp"="rpcrt4.dll"
> > "ncacn_http"="rpcrt4.dll"
> >
> > When I was getting RPC is unavailable I had these missing, I made the
> > entries and I no longer get the RPC is unavailable.
>
> I have no 1656 entries in the existing or (soon to be) new DC.
>
> Thanks again!
> -joe
>
>
- Next message: SergeL: "Wireless Router inside Network behind firewall"
- Previous message: Joe Ross: "Re: novice: problem adding second domain"
- In reply to: Joe Ross: "Re: novice: problem adding second domain"
- Next in thread: Kevin D. Goodknecht [MVP]: "Re: novice: problem adding second domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
