AGREGAR W2003 A DOMINIO W2000

hola de nuevo Javier...

tengo la red montada asi desde hace 5 o 6 años.. tambien tengo montado el
servidor como DHCP y la verdad es q no he tenido problemas de red nunca...

que rango es util entonces para usar?

he hecho lo q me has dicho y ahi t paso el resultado:

NETDIAG



Computer Name: SERVIDOR
DNS Host Name: servidor.fsandamaso
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
List of installed hotfixes :
KB329115
KB820888
KB822831
KB823182
KB823559
KB823980
KB824105
KB824151
KB825119
KB826232
KB828035
KB828741
KB828749
KB834707-IE6SP1-20040929.091901
KB835732
KB837001
KB839645
KB840315
KB840987
KB841356
KB841533
KB841872
KB841873
KB842526
KB893803v2
Q147222
Q828026


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



Per interface results:

Adapter : INTEGRADA

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : servidor
IP Address . . . . . . . . : 169.254.0.10
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . : 169.254.0.3
Dns Servers. . . . . . . . : 169.254.0.10


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
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
[WARNING] Cannot find a primary authoritative DNS server for the
name
'servidor.fsandamaso.'. [RCODE_SERVER_FAILURE]
The name 'servidor.fsandamaso.' may not be registered in DNS.
PASS - All the DNS entries for DC are registered on DNS server
'169.254.0.10
'.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
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
[WARNING] Failed to query SPN registration on DC 'servidor.fsandamaso'.


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


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


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.

The command completed successfully


DCDIAG /test:registerinDNS

Starting test: RegisterInDNS
This domain controller cannot register domain controller Locator DNS
records. This is because it cannot locate a DNS server authoritative for
the zone fsandamaso. This is due to one of the following:

1. One or more DNS servers involved in the name resolution of the
fsandamaso name are not responding or contain incorrect delegation of the
DNS zones; or

2. The DNS server that this computer is configured with contains
incorrect root hints.

The list of such DNS servers might include the DNS servers with which
this computer is configured for name resolution and the DNS servers
responsible for the following zones: fsandamaso

Verify the correctness of the specified domain name and contact your
network/DNS administrator to fix the problem.

You can also manually add the records specified in the
%systemroot%\system32\configetlogon.dns file.


. servidor failed test RegisterInDNS

<<<DNS Host Name: servidor.fsandamaso>>>

OK, tu estructura de nombre FQDN no es la adecuada...en esos casos hay que
tener cuidadito y revisar esto:

Information about configuring Windows for domains with single-label DNS
names
http://support.microsoft.com/kb/300684/en-us

A parte, lo normal e seguir un estandar en redes internas de toda la vida,
luego evidentemente cada uno hace lo que quiera, son redes del tipo
10.0.0.0, máscara 255.0.0.0.
172.16.0.0, máscara 255.255.0.0
192.168.0.0 máscara 255.255.255.0

Tu direccionamiento interno, que no está mal, simplemente me sorprende que
hayas elegido ese rango, se correspnde a esto por estandard, de ahí que me
haya extrañado tanto:

http://support.microsoft.com/kb/220874



Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"Pepe" escribió en el mensaje
news:

hola de nuevo Javier...

tengo la red montada asi desde hace 5 o 6 años.. tambien tengo montado el
servidor como DHCP y la verdad es q no he tenido problemas de red nunca...

que rango es util entonces para usar?

he hecho lo q me has dicho y ahi t paso el resultado:

NETDIAG



Computer Name: SERVIDOR
DNS Host Name: servidor.fsandamaso
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
List of installed hotfixes :
KB329115
KB820888
KB822831
KB823182
KB823559
KB823980
KB824105
KB824151
KB825119
KB826232
KB828035
KB828741
KB828749
KB834707-IE6SP1-20040929.091901
KB835732
KB837001
KB839645
KB840315
KB840987
KB841356
KB841533
KB841872
KB841873
KB842526
KB893803v2
Q147222
Q828026


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



Per interface results:

Adapter : INTEGRADA

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : servidor
IP Address . . . . . . . . : 169.254.0.10
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . : 169.254.0.3
Dns Servers. . . . . . . . : 169.254.0.10


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
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
[WARNING] Cannot find a primary authoritative DNS server for the
name
'servidor.fsandamaso.'. [RCODE_SERVER_FAILURE]
The name 'servidor.fsandamaso.' may not be registered in DNS.
PASS - All the DNS entries for DC are registered on DNS server
'169.254.0.10
'.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
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
[WARNING] Failed to query SPN registration on DC 'servidor.fsandamaso'.


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


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


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.

The command completed successfully


DCDIAG /test:registerinDNS

Starting test: RegisterInDNS
This domain controller cannot register domain controller Locator DNS
records. This is because it cannot locate a DNS server authoritative
for
the zone fsandamaso. This is due to one of the following:

1. One or more DNS servers involved in the name resolution of the
fsandamaso name are not responding or contain incorrect delegation of
the
DNS zones; or

2. The DNS server that this computer is configured with contains
incorrect root hints.

The list of such DNS servers might include the DNS servers with which
this computer is configured for name resolution and the DNS servers
responsible for the following zones: fsandamaso

Verify the correctness of the specified domain name and contact your
network/DNS administrator to fix the problem.

You can also manually add the records specified in the
%systemroot%\system32\configetlogon.dns file.


. servidor failed test RegisterInDNS

hola Javier

he estado mirando el doc. y no sabia q era tan importante el nombre FQDN

ahora tal y como lo tngo, con los errores que me salen del netdiag y el
dcdiag tendre algun problema con el w20003 cuando le pase los roles o algo o
antes tendria que tocar el registro como pone el doc. para que registre
dinamicamante los dns? se q me has dicho q haga las pruebas antes en un
laboratorio pero lo cierto es q no tngo esa opcion..de ahi tantas preguntas
antes de hacer nada... a ver como me las apaño

cuando tenga todo pasado al w2003 si cambio el nombre FQDN del DNS por
"miempesa.com" por ejemplo, tngo que cambiar algo en los clientes o no haria
falta?

en cuanto al rango de red, la verdad es que no se porque lo utilizé...tengo
otra red en la que uso el rango 192.168.x

antes staba en otra empresa en la que usabamos este rango y el otro
indistintamente y supongo que se me quedo...

Si en el DHCP del nuevo w2003 creo un nuevo rango como alguno de los que me
dices, en los clientes al validarse que pasará? tendria que hacer un ipconfig
/renew en todos o cogeria los datos del nuevo dhcp?

Javier..de verdad que te agradezco muchisimo tanta ayuda..


"Javier Inglés [MS MVP]" wrote:

<<<DNS Host Name: servidor.fsandamaso>>>

OK, tu estructura de nombre FQDN no es la adecuada...en esos casos hay que
tener cuidadito y revisar esto:

Information about configuring Windows for domains with single-label DNS
names
http://support.microsoft.com/kb/300684/en-us

A parte, lo normal e seguir un estandar en redes internas de toda la vida,
luego evidentemente cada uno hace lo que quiera, son redes del tipo
10.0.0.0, máscara 255.0.0.0.
172.16.0.0, máscara 255.255.0.0
192.168.0.0 máscara 255.255.255.0

Tu direccionamiento interno, que no está mal, simplemente me sorprende que
hayas elegido ese rango, se correspnde a esto por estandard, de ahí que me
haya extrañado tanto:

http://support.microsoft.com/kb/220874



Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"Pepe" escribió en el mensaje
news:
> hola de nuevo Javier...
>
> tengo la red montada asi desde hace 5 o 6 años.. tambien tengo montado el
> servidor como DHCP y la verdad es q no he tenido problemas de red nunca...
>
> que rango es util entonces para usar?
>
> he hecho lo q me has dicho y ahi t paso el resultado:
>
> NETDIAG
>
>
>
> Computer Name: SERVIDOR
> DNS Host Name: servidor.fsandamaso
> System info : Windows 2000 Server (Build 2195)
> Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
> List of installed hotfixes :
> KB329115
> KB820888
> KB822831
> KB823182
> KB823559
> KB823980
> KB824105
> KB824151
> KB825119
> KB826232
> KB828035
> KB828741
> KB828749
> KB834707-IE6SP1-20040929.091901
> KB835732
> KB837001
> KB839645
> KB840315
> KB840987
> KB841356
> KB841533
> KB841872
> KB841873
> KB842526
> KB893803v2
> Q147222
> Q828026
>
>
> Netcard queries test . . . . . . . : Passed
> GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
> GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_GEN_FAILURE]
> [WARNING] The net card 'Minipuerto WAN (IP)' may not be working because
> it h
> as not received any packets.
> [WARNING] The net card 'Minipuerto WAN (Monitor de red)' may not be
> working
> because it has not received any packets.
> GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
>
>
>
> Per interface results:
>
> Adapter : INTEGRADA
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : servidor
> IP Address . . . . . . . . : 169.254.0.10
> Subnet Mask. . . . . . . . : 255.255.0.0
> Default Gateway. . . . . . : 169.254.0.3
> Dns Servers. . . . . . . . : 169.254.0.10
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> No remote names have been found.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
> 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
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'servidor.fsandamaso.'. [RCODE_SERVER_FAILURE]
> The name 'servidor.fsandamaso.' may not be registered in DNS.
> PASS - All the DNS entries for DC are registered on DNS server
> '169.254.0.10
> '.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
> 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
> [WARNING] Failed to query SPN registration on DC 'servidor.fsandamaso'.
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Passed
> IPSec policy service is active, but no policy is assigned.
>
> The command completed successfully
>
>
> DCDIAG /test:registerinDNS
>
> Starting test: RegisterInDNS
> This domain controller cannot register domain controller Locator DNS
> records. This is because it cannot locate a DNS server authoritative
> for
> the zone fsandamaso. This is due to one of the following:
>
> 1. One or more DNS servers involved in the name resolution of the
> fsandamaso name are not responding or contain incorrect delegation of
> the
> DNS zones; or
>
> 2. The DNS server that this computer is configured with contains
> incorrect root hints.
>
> The list of such DNS servers might include the DNS servers with which
> this computer is configured for name resolution and the DNS servers
> responsible for the following zones: fsandamaso
>
> Verify the correctness of the specified domain name and contact your
> network/DNS administrator to fix the problem.
>
> You can also manually add the records specified in the
> %systemroot%\system32\configetlogon.dns file.
>
>
> . servidor failed test RegisterInDNS
>
>
>

Tu rango de subred no hace falta que lo cambies para nada, era sólo un
apunte socio; el tema del laboratorio, lo siento pero no me creo que no
puedas montarte uno con VirtualPC/VirtualServer o VMWare (todos gratuitos)
para probar :-)))

Lo del nombre FQDN es un tema muy importante y que desde el principio se
explica y se debe entender, si no corres el riesgo de que el dominio pueda
presentar ciertos problemas; puedes hacer lo que dice el artículo; y te
recomendaría, después de haber migrado a 2003, plantearte el renombrarlo
como dios manda, pero teneindo especial cuidado, ya que ese paso sí es más
crítico y requiere de muchas más pruebas:

Windows Server 2003 Active Directory Domain Rename Tools
http://technet.microsoft.com/es-es/...05948.aspx

Domain Rename - Rename a Windows 2003 Forest with Exchange 2003 installed
http://www.msexchange.org/tutorials...ename.html

How Domain Rename Works
http://technet2.microsoft.com/windo...x?mfr=true

Microsoft Exchange Server Domain Rename Fixup (XDR-Fixup)
http://www.microsoft.com/downloads/...x?FamilyId$B47D4A-C4B9-4031-B491-29839148A28C&displaylang=en


Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"Pepe" escribió en el mensaje
news:

hola Javier

he estado mirando el doc. y no sabia q era tan importante el nombre FQDN

ahora tal y como lo tngo, con los errores que me salen del netdiag y el
dcdiag tendre algun problema con el w20003 cuando le pase los roles o algo
o
antes tendria que tocar el registro como pone el doc. para que registre
dinamicamante los dns? se q me has dicho q haga las pruebas antes en un
laboratorio pero lo cierto es q no tngo esa opcion..de ahi tantas
preguntas
antes de hacer nada... a ver como me las apaño

cuando tenga todo pasado al w2003 si cambio el nombre FQDN del DNS por
"miempesa.com" por ejemplo, tngo que cambiar algo en los clientes o no
haria
falta?

en cuanto al rango de red, la verdad es que no se porque lo
utilizé...tengo
otra red en la que uso el rango 192.168.x

antes staba en otra empresa en la que usabamos este rango y el otro
indistintamente y supongo que se me quedo...

Si en el DHCP del nuevo w2003 creo un nuevo rango como alguno de los que
me
dices, en los clientes al validarse que pasará? tendria que hacer un
ipconfig
/renew en todos o cogeria los datos del nuevo dhcp?

Javier..de verdad que te agradezco muchisimo tanta ayuda..


"Javier Inglés [MS MVP]" wrote:

<<<DNS Host Name: servidor.fsandamaso>>>

OK, tu estructura de nombre FQDN no es la adecuada...en esos casos hay
que
tener cuidadito y revisar esto:

Information about configuring Windows for domains with single-label DNS
names
http://support.microsoft.com/kb/300684/en-us

A parte, lo normal e seguir un estandar en redes internas de toda la
vida,
luego evidentemente cada uno hace lo que quiera, son redes del tipo
10.0.0.0, máscara 255.0.0.0.
172.16.0.0, máscara 255.255.0.0
192.168.0.0 máscara 255.255.255.0

Tu direccionamiento interno, que no está mal, simplemente me sorprende
que
hayas elegido ese rango, se correspnde a esto por estandard, de ahí que
me
haya extrañado tanto:

http://support.microsoft.com/kb/220874



Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"Pepe" escribió en el mensaje
news:
> hola de nuevo Javier...
>
> tengo la red montada asi desde hace 5 o 6 años.. tambien tengo montado
> el
> servidor como DHCP y la verdad es q no he tenido problemas de red
> nunca...
>
> que rango es util entonces para usar?
>
> he hecho lo q me has dicho y ahi t paso el resultado:
>
> NETDIAG
>
>
>
> Computer Name: SERVIDOR
> DNS Host Name: servidor.fsandamaso
> System info : Windows 2000 Server (Build 2195)
> Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
> List of installed hotfixes :
> KB329115
> KB820888
> KB822831
> KB823182
> KB823559
> KB823980
> KB824105
> KB824151
> KB825119
> KB826232
> KB828035
> KB828741
> KB828749
> KB834707-IE6SP1-20040929.091901
> KB835732
> KB837001
> KB839645
> KB840315
> KB840987
> KB841356
> KB841533
> KB841872
> KB841873
> KB842526
> KB893803v2
> Q147222
> Q828026
>
>
> Netcard queries test . . . . . . . : Passed
> GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
> GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_GEN_FAILURE]
> [WARNING] The net card 'Minipuerto WAN (IP)' may not be working
> because
> it h
> as not received any packets.
> [WARNING] The net card 'Minipuerto WAN (Monitor de red)' may not be
> working
> because it has not received any packets.
> GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
>
>
>
> Per interface results:
>
> Adapter : INTEGRADA
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : servidor
> IP Address . . . . . . . . : 169.254.0.10
> Subnet Mask. . . . . . . . : 255.255.0.0
> Default Gateway. . . . . . : 169.254.0.3
> Dns Servers. . . . . . . . : 169.254.0.10
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> No remote names have been found.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
> 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
> [WARNING] Cannot find a primary authoritative DNS server for
> the
> name
> 'servidor.fsandamaso.'. [RCODE_SERVER_FAILURE]
> The name 'servidor.fsandamaso.' may not be registered in
> DNS.
> PASS - All the DNS entries for DC are registered on DNS server
> '169.254.0.10
> '.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
> 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
> [WARNING] Failed to query SPN registration on DC
> 'servidor.fsandamaso'.
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Passed
> IPSec policy service is active, but no policy is assigned.
>
> The command completed successfully
>
>
> DCDIAG /test:registerinDNS
>
> Starting test: RegisterInDNS
> This domain controller cannot register domain controller Locator DNS
> records. This is because it cannot locate a DNS server authoritative
> for
> the zone fsandamaso. This is due to one of the following:
>
> 1. One or more DNS servers involved in the name resolution of the
> fsandamaso name are not responding or contain incorrect delegation
> of
> the
> DNS zones; or
>
> 2. The DNS server that this computer is configured with contains
> incorrect root hints.
>
> The list of such DNS servers might include the DNS servers with
> which
> this computer is configured for name resolution and the DNS servers
> responsible for the following zones: fsandamaso
>
> Verify the correctness of the specified domain name and contact your
> network/DNS administrator to fix the problem.
>
> You can also manually add the records specified in the
> %systemroot%\system32\configetlogon.dns file.
>
>
> . servidor failed test RegisterInDNS
>
>
>

bueno Javier..

probare las mil cosas que me has stado enseñando estos dias..

no se como agradecerte tu ayuda de verdad..

voy a leerme la doc. q me has puesto y me pondre manos a la obra..a ver q
tal sale todo..

mil gracias :-)

"Javier Inglés [MS MVP]" wrote:

Tu rango de subred no hace falta que lo cambies para nada, era sólo un
apunte socio; el tema del laboratorio, lo siento pero no me creo que no
puedas montarte uno con VirtualPC/VirtualServer o VMWare (todos gratuitos)
para probar :-)))

Lo del nombre FQDN es un tema muy importante y que desde el principio se
explica y se debe entender, si no corres el riesgo de que el dominio pueda
presentar ciertos problemas; puedes hacer lo que dice el artículo; y te
recomendaría, después de haber migrado a 2003, plantearte el renombrarlo
como dios manda, pero teneindo especial cuidado, ya que ese paso sí es más
crítico y requiere de muchas más pruebas:

Windows Server 2003 Active Directory Domain Rename Tools
http://technet.microsoft.com/es-es/...05948.aspx

Domain Rename - Rename a Windows 2003 Forest with Exchange 2003 installed
http://www.msexchange.org/tutorials...ename.html

How Domain Rename Works
http://technet2.microsoft.com/windo...x?mfr=true

Microsoft Exchange Server Domain Rename Fixup (XDR-Fixup)
http://www.microsoft.com/downloads/...x?FamilyId$B47D4A-C4B9-4031-B491-29839148A28C&displaylang=en


Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"Pepe" escribió en el mensaje
news:
>
> hola Javier
>
> he estado mirando el doc. y no sabia q era tan importante el nombre FQDN
>
> ahora tal y como lo tngo, con los errores que me salen del netdiag y el
> dcdiag tendre algun problema con el w20003 cuando le pase los roles o algo
> o
> antes tendria que tocar el registro como pone el doc. para que registre
> dinamicamante los dns? se q me has dicho q haga las pruebas antes en un
> laboratorio pero lo cierto es q no tngo esa opcion..de ahi tantas
> preguntas
> antes de hacer nada... a ver como me las apaño
>
> cuando tenga todo pasado al w2003 si cambio el nombre FQDN del DNS por
> "miempesa.com" por ejemplo, tngo que cambiar algo en los clientes o no
> haria
> falta?
>
> en cuanto al rango de red, la verdad es que no se porque lo
> utilizé...tengo
> otra red en la que uso el rango 192.168.x
>
> antes staba en otra empresa en la que usabamos este rango y el otro
> indistintamente y supongo que se me quedo...
>
> Si en el DHCP del nuevo w2003 creo un nuevo rango como alguno de los que
> me
> dices, en los clientes al validarse que pasará? tendria que hacer un
> ipconfig
> /renew en todos o cogeria los datos del nuevo dhcp?
>
> Javier..de verdad que te agradezco muchisimo tanta ayuda..
>
>
> "Javier Inglés [MS MVP]" wrote:
>
>> <<<DNS Host Name: servidor.fsandamaso>>>
>>
>> OK, tu estructura de nombre FQDN no es la adecuada...en esos casos hay
>> que
>> tener cuidadito y revisar esto:
>>
>> Information about configuring Windows for domains with single-label DNS
>> names
>> http://support.microsoft.com/kb/300684/en-us
>>
>> A parte, lo normal e seguir un estandar en redes internas de toda la
>> vida,
>> luego evidentemente cada uno hace lo que quiera, son redes del tipo
>> 10.0.0.0, máscara 255.0.0.0.
>> 172.16.0.0, máscara 255.255.0.0
>> 192.168.0.0 máscara 255.255.255.0
>>
>> Tu direccionamiento interno, que no está mal, simplemente me sorprende
>> que
>> hayas elegido ese rango, se correspnde a esto por estandard, de ahí que
>> me
>> haya extrañado tanto:
>>
>> http://support.microsoft.com/kb/220874
>>
>>
>>
>> Salu2!!
>> Javier Inglés
>> https://mvp.support.microsoft.com/p...B5567431B0
>> MS MVP, Windows Server-Directory Services
>>
>>
>>
>> "Pepe" escribió en el mensaje
>> news:
>> > hola de nuevo Javier...
>> >
>> > tengo la red montada asi desde hace 5 o 6 años.. tambien tengo montado
>> > el
>> > servidor como DHCP y la verdad es q no he tenido problemas de red
>> > nunca...
>> >
>> > que rango es util entonces para usar?
>> >
>> > he hecho lo q me has dicho y ahi t paso el resultado:
>> >
>> > NETDIAG
>> >
>> >
>> >
>> > Computer Name: SERVIDOR
>> > DNS Host Name: servidor.fsandamaso
>> > System info : Windows 2000 Server (Build 2195)
>> > Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
>> > List of installed hotfixes :
>> > KB329115
>> > KB820888
>> > KB822831
>> > KB823182
>> > KB823559
>> > KB823980
>> > KB824105
>> > KB824151
>> > KB825119
>> > KB826232
>> > KB828035
>> > KB828741
>> > KB828749
>> > KB834707-IE6SP1-20040929.091901
>> > KB835732
>> > KB837001
>> > KB839645
>> > KB840315
>> > KB840987
>> > KB841356
>> > KB841533
>> > KB841872
>> > KB841873
>> > KB842526
>> > KB893803v2
>> > Q147222
>> > Q828026
>> >
>> >
>> > Netcard queries test . . . . . . . : Passed
>> > GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
>> > GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_GEN_FAILURE]
>> > [WARNING] The net card 'Minipuerto WAN (IP)' may not be working
>> > because
>> > it h
>> > as not received any packets.
>> > [WARNING] The net card 'Minipuerto WAN (Monitor de red)' may not be
>> > working
>> > because it has not received any packets.
>> > GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
>> >
>> >
>> >
>> > Per interface results:
>> >
>> > Adapter : INTEGRADA
>> >
>> > Netcard queries test . . . : Passed
>> >
>> > Host Name. . . . . . . . . : servidor
>> > IP Address . . . . . . . . : 169.254.0.10
>> > Subnet Mask. . . . . . . . : 255.255.0.0
>> > Default Gateway. . . . . . : 169.254.0.3
>> > Dns Servers. . . . . . . . : 169.254.0.10
>> >
>> >
>> > AutoConfiguration results. . . . . . : Passed
>> >
>> > Default gateway test . . . : Passed
>> >
>> > NetBT name test. . . . . . : Passed
>> > No remote names have been found.
>> >
>> > WINS service test. . . . . : Skipped
>> > There are no WINS servers configured for this interface.
>> >
>> >
>> > Global results:
>> >
>> >
>> > Domain membership test . . . . . . : Passed
>> >
>> >
>> > NetBT transports test. . . . . . . : Passed
>> > List of NetBt transports currently configured:
>> > NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
>> > 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
>> > [WARNING] Cannot find a primary authoritative DNS server for
>> > the
>> > name
>> > 'servidor.fsandamaso.'. [RCODE_SERVER_FAILURE]
>> > The name 'servidor.fsandamaso.' may not be registered in
>> > DNS.
>> > PASS - All the DNS entries for DC are registered on DNS server
>> > '169.254.0.10
>> > '.
>> >
>> >
>> > Redir and Browser test . . . . . . : Passed
>> > List of NetBt transports currently bound to the Redir
>> > NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
>> > The redir is bound to 1 NetBt transport.
>> >
>> > List of NetBt transports currently bound to the browser
>> > NetBT_Tcpip_{E36CF85A-93B8-4EBD-B479-300C27C18603}
>> > 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
>> > [WARNING] Failed to query SPN registration on DC
>> > 'servidor.fsandamaso'.
>> >
>> >
>> > Bindings test. . . . . . . . . . . : Passed
>> >
>> >
>> > WAN configuration test . . . . . . : Skipped
>> > No active remote access connections.
>> >
>> >
>> > Modem diagnostics test . . . . . . : Passed
>> >
>> > IP Security test . . . . . . . . . : Passed
>> > IPSec policy service is active, but no policy is assigned.
>> >
>> > The command completed successfully
>> >
>> >
>> > DCDIAG /test:registerinDNS
>> >
>> > Starting test: RegisterInDNS
>> > This domain controller cannot register domain controller Locator DNS
>> > records. This is because it cannot locate a DNS server authoritative
>> > for
>> > the zone fsandamaso. This is due to one of the following:
>> >
>> > 1. One or more DNS servers involved in the name resolution of the
>> > fsandamaso name are not responding or contain incorrect delegation
>> > of
>> > the
>> > DNS zones; or
>> >
>> > 2. The DNS server that this computer is configured with contains
>> > incorrect root hints.
>> >
>> > The list of such DNS servers might include the DNS servers with
>> > which
>> > this computer is configured for name resolution and the DNS servers
>> > responsible for the following zones: fsandamaso
>> >
>> > Verify the correctness of the specified domain name and contact your