Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » after to try add DC win 2008 into AD server 2003, dns problems
after to try add DC win 2008 into AD server 2003, dns problems [message #325024] Sun, 22 November 2009 18:44 Go to next message
Leopoldo Rios  is currently offline Leopoldo Rios  United States
Messages: 3
Registered: November 2009
Junior Member
Hello. For a situation that has happened.
My domain, Midominio.com example, running on a Server 2003 Standard
Edition, with DNS name resolution server as Active Directory integrated.
So far so good!
The client requested a new server to integrate with Windows 2008 Server
enterprise edition, as additional domain controller.
I then decided to implement:
1) adprep / forestprep
2) adprep / domainprep / gpprep
The system reported ok.
Then on the server 2008, I ran dcpromo / adv TCPIP with the following
configuration:
a) Server 2003 domain controller: ip: 192.168.1.10 / 16; dns:
192.168.1.10
b) Server 2008: ip 192.168.1.8 / 16; dns: 192.168.1.10

After performing the installation, and finishing almost error message
appears, saying he could not find the DNS server.
Please try running DCPROMO / ADV, and now the system reports: who have
been consulted and that non-registration (A) or is there a name server
is not configured ..

Well, the truth is not good to do, if someone can guide me with this I
suspect is not a big problem.

Thank you


--
Leopoldo Rios
------------------------------------------------------------ ------------
Leopoldo Rios's Profile: http://forums.techarena.in/members/157237.htm
View this thread: http://forums.techarena.in/active-directory/1274111.htm

http://forums.techarena.in
Re: after to try add DC win 2008 into AD server 2003, dns problems [message #325074 is a reply to message #325024] Sun, 22 November 2009 20:42 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Leopoldo Rios" <Leopoldo.Rios.4230vb@DoNotSpam.com> wrote in message
news:Leopoldo.Rios.4230vb@DoNotSpam.com...
>
> Hello. For a situation that has happened.
> My domain, Midominio.com example, running on a Server 2003 Standard
> Edition, with DNS name resolution server as Active Directory integrated.
> So far so good!
> The client requested a new server to integrate with Windows 2008 Server
> enterprise edition, as additional domain controller.
> I then decided to implement:
> 1) adprep / forestprep
> 2) adprep / domainprep / gpprep
> The system reported ok.
> Then on the server 2008, I ran dcpromo / adv TCPIP with the following
> configuration:
> a) Server 2003 domain controller: ip: 192.168.1.10 / 16; dns:
> 192.168.1.10
> b) Server 2008: ip 192.168.1.8 / 16; dns: 192.168.1.10
>
> After performing the installation, and finishing almost error message
> appears, saying he could not find the DNS server.
> Please try running DCPROMO / ADV, and now the system reports: who have
> been consulted and that non-registration (A) or is there a name server
> is not configured ..
>
> Well, the truth is not good to do, if someone can guide me with this I
> suspect is not a big problem.
>
> Thank you
>
>
> --
> Leopoldo Rios
> ------------------------------------------------------------ ------------

Run the following on your domain controller, please.

dcdiag /v > c:\dcdiag.txt
netdiag /v > c:\netdiag.txt

Also, please post a full unedited ipconfig /all from the domain controller
and from the Windows 2008 server, please.

If there are any Event log errors on the current domain controller or the
Windows 2008 server, please post the EventID# and Source name.

This information will towards a diagnosis.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Re: after to try add DC win 2008 into AD server 2003, dns problems [message #325147 is a reply to message #325024] Sun, 22 November 2009 23:23 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Leopoldo,

I agree with Ace about the additional complete information we need. Did you
add the server to the domain before and checked in DNS zones that it is listed?

Any firewall running on the 2008, enabled by default?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello. For a situation that has happened.
> My domain, Midominio.com example, running on a Server 2003 Standard
> Edition, with DNS name resolution server as Active Directory
> integrated.
> So far so good!
> The client requested a new server to integrate with Windows 2008
> Server
> enterprise edition, as additional domain controller.
> I then decided to implement:
> 1) adprep / forestprep
> 2) adprep / domainprep / gpprep
> The system reported ok.
> Then on the server 2008, I ran dcpromo / adv TCPIP with the following
> configuration:
> a) Server 2003 domain controller: ip: 192.168.1.10 / 16; dns:
> 192.168.1.10
> b) Server 2008: ip 192.168.1.8 / 16; dns: 192.168.1.10
> After performing the installation, and finishing almost error message
> appears, saying he could not find the DNS server.
> Please try running DCPROMO / ADV, and now the system reports: who have
> been consulted and that non-registration (A) or is there a name server
> is not configured ..
> Well, the truth is not good to do, if someone can guide me with this I
> suspect is not a big problem.
>
> Thank you
>
> http://forums.techarena.in
>
Re: after to try add DC win 2008 into AD server 2003, dns problems [message #326299 is a reply to message #325147] Tue, 24 November 2009 06:46 Go to previous messageGo to next message
Leopoldo Rios  is currently offline Leopoldo Rios  United States
Messages: 3
Registered: November 2009
Junior Member
Ok. Thanks for you comment.
eliminé el directorio raiz, y volví a generar.
Corrí el c:\netdiag /fix con el siguiente resultado:
C:\WINDOWS\system32\drivers\etc>netdiag /fix

......................................

Computer Name: CENTRAL1
DNS Host Name: central1.dominio.local
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
List of installed hotfixes :
Q147222


Netcard queries test . . . . . . . : Passed
GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'Minipuerto WAN (PPTP)' may not be working
because it
has not received any packets.
[WARNING] The net card 'Minipuerto WAN (PPPOE)' may not be working
because i
t has not received any packets.
[WARNING] The net card 'Minipuerto WAN (IP)' may not be working
because it h
as not received any packets.
GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

Adapter : red

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : server1.dominio.local
IP Address . . . . . . . . : 192.168.1.10
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . : 192.168.1.11
Primary WINS Server. . . . : 192.168.1.10
Dns Servers. . . . . . . . : 127.0.0.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

WINS service test. . . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{F23D0CC0-D2E2-495E-B88E-C6EEA0DDFA1C}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'127.0.0.1'.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{F23D0CC0-D2E2-495E-B88E-C6EEA0DDFA1C}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{F23D0CC0-D2E2-495E-B88E-C6EEA0DDFA1C}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed
information


The command completed successfully

C:\WINDOWS\system32\drivers\etc>

it so happens that I want to add a new DC to the domain. from server2,
trying to integrate to the domain gives me the following error:
Note: This information is intended for a network administrator. If you
do not, notifies the network administrator that you received this
information recorded in the file C: \ WINDOWS \ debug \ dcdiag.txt.

It was properly consulting the DNS resource record for the service
location (SRV) used to locate a domain controller for the domain
dominio.local:

The query was for the SRV record for
_ldap._tcp.dc._msdcs.dominio.local

The application identified the following domain controllers:

server1.dominio.local

The following are common causes of this error:

-Missing host (A) that assign the name of the domain controller to its
IP address or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the
network or are not running.

For more information on how to correct this problem, click Help.

Can help me ?

2009/11/23, TechArena Community <noreply@techarena.in>:

- Mostrar texto citado -
--
Lic. Leopoldo José Rios


--
Leopoldo Rios
------------------------------------------------------------ ------------
Leopoldo Rios's Profile: http://forums.techarena.in/members/157237.htm
View this thread: http://forums.techarena.in/active-directory/1274111.htm

http://forums.techarena.in
Re: after to try add DC win 2008 into AD server 2003, dns problems [message #326322 is a reply to message #326299] Tue, 24 November 2009 07:47 Go to previous message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Leopoldo Rios" <Leopoldo.Rios.425svb@DoNotSpam.com> wrote in message
news:Leopoldo.Rios.425svb@DoNotSpam.com...
>
> Ok. Thanks for you comment.
> eliminé el directorio raiz, y volví a generar.
> Corrí el c:\netdiag /fix con el siguiente resultado:
> C:\WINDOWS\system32\drivers\etc>netdiag /fix
> .....................................
>
> Computer Name: CENTRAL1
> DNS Host Name: central1.dominio.local
> System info : Microsoft Windows Server 2003 R2 (Build 3790)
> Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
> List of installed hotfixes :
> Q147222
>
> Netcard queries test . . . . . . . : Passed
> GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
> [WARNING] The net card 'Minipuerto WAN (PPTP)' may not be working
> because it has not received any packets.
> [WARNING] The net card 'Minipuerto WAN (PPPOE)' may not be working
> because it has not received any packets.
> [WARNING] The net card 'Minipuerto WAN (IP)' may not be working
> because it h
> as not received any packets.
> GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
>
> Per interface results:
>
> Adapter : red
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : server1.dominio.local
> IP Address . . . . . . . . : 192.168.1.10
> Subnet Mask. . . . . . . . : 255.255.0.0
> Default Gateway. . . . . . : 192.168.1.11
> Primary WINS Server. . . . : 192.168.1.10
> Dns Servers. . . . . . . . : 127.0.0.1
>
> AutoConfiguration results. . . . . . : Passed
> Default gateway test . . . : Passed
> NetBT name test. . . . . . : Passed
> WINS service test. . . . . : Passed
>
> Global results:
> Domain membership test . . . . . . : Passed
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{F23D0CC0-D2E2-495E-B88E-C6EEA0DDFA1C}
> 1 NetBt transport currently configured.
> Autonet address test . . . . . . . : Passed
> IP loopback ping test. . . . . . . : Passed
> Default gateway test . . . . . . . : Passed
> NetBT name test. . . . . . . . . . : Passed
> Winsock test . . . . . . . . . . . : Passed
> DNS test . . . . . . . . . . . . . : Passed
> PASS - All the DNS entries for DC are registered on DNS server
> '127.0.0.1'.
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{F23D0CC0-D2E2-495E-B88E-C6EEA0DDFA1C}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{F23D0CC0-D2E2-495E-B88E-C6EEA0DDFA1C}
> The browser is bound to 1 NetBt transport.
>
> DC discovery test. . . . . . . . . : Passed
> DC list test . . . . . . . . . . . : Passed
> Trust relationship test. . . . . . : Skipped
> Kerberos test. . . . . . . . . . . : Passed
> LDAP test. . . . . . . . . . . . . : Passed
> Bindings test. . . . . . . . . . . : Passed
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
>
> Note: run "netsh ipsec dynamic show /?" for more detailed
> information
>
>
> The command completed successfully
>
> C:\WINDOWS\system32\drivers\etc>
>
> it so happens that I want to add a new DC to the domain. from server2,
> trying to integrate to the domain gives me the following error:
> Note: This information is intended for a network administrator. If you
> do not, notifies the network administrator that you received this
> information recorded in the file C: \ WINDOWS \ debug \ dcdiag.txt.
>
> It was properly consulting the DNS resource record for the service
> location (SRV) used to locate a domain controller for the domain
> dominio.local:
>
> The query was for the SRV record for
> _ldap._tcp.dc._msdcs.dominio.local
>
> The application identified the following domain controllers:
>
> server1.dominio.local
>
> The following are common causes of this error:
>
> -Missing host (A) that assign the name of the domain controller to its
> IP address or contain incorrect addresses.
>
> - Domain controllers registered in DNS are not connected to the
> network or are not running.
>
> For more information on how to correct this problem, click Help.
>
> Can help me ?
> --
> Leopoldo Rios

Thank you for posting the results.

I would first highly suggest to remove the DNS address, 127.0.0.1 and change
it to the DC's actual IP address of 192.168.1.10.

I would also suggest to create a reverse zone (under Reverse Lookup Zones)
for "192.168.1.0"

After the above has been completed, please run the following:
ipconfig /registerdns
net stop netlogon
net start netlogon

The re-run:
dcdiag /v
netdiag /v

Also, if you can post the *actual* ipconfig /all, it would be helpful. It
provides additional configuration information for us to review and evaluate.

Ace
Previous Topic:"Schema update failed: Duplicate RDN"
Next Topic:access denied when domain admin move organizational unit objects
Goto Forum:
  


Current Time: Fri Jan 19 00:44:00 MST 2018

Total time taken to generate the page: 0.02706 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software