Problem with upgrade from NT server 4 to 2000

[Larry]

Archived from groups: microsoft.public.win2000.setup (More info?)

Started with 3 computers on a test network:
Computer 1 was NT4 PDC
Computer 2 is w2000 server as a plain server
Computer 3 is a NT4 BDC
Upgraded Computer 1 to W2000 server and installed Active Directory.
Then installed DNS
Can see all computers and ping them
Left other 2 computers as is.
On computer 1 - simple and recursive DNS queries pass test.
Then tried to install Active Dir on Computer 2 - Get error:
"Specified Domain either does not exist or could not be contacted"
Run DCDIAG on Computer 1. Result:
Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\SERVER
Starting test: Connectivity
SERVER'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
(b8fae8ad-5dca-472f-959e-049784de0a45._msdcs.domain.com)
couldn't be resolved, the server name (server.domain.com)
resolved to the IP address (192.168.1.99) and was pingable.
Check that the IP address is registered correctly with the DNS server.
......................... SERVER failed test Connectivity

Doing primary tests

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

Running enterprise tests on : domain.com
Starting test: Intersite
......................... domain.com passed test Intersite
Starting test: FsmoCheck
......................... domain.com passed test FsmoCheck

Results from netdiag:

Computer Name: server
DNS Host Name: server.domain.com
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
List of installed hotfixes :
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : server
IP Address . . . . . . . . : 192.168.1.99
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.99


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

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_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
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 . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not registered correctly
on DNS server '192.168.1.99'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
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 'server.domain.com'.


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


Guessing that this is preventing me setting up Computer 2 as a DC. How
do I get the GUID name to resolve? Or are there other problems to deal
with first?

Thanks

 

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

Does computer 2 point to computer 1 for DNS in the properties of TCP/IP?

Does your AD DNS server have all the proper DNS records?
See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;241515


If not does your AD DNS server point to itself for DNS in the properties of
TCP/IP?


hth
DDS W 2k MVP MCSE

"larry" <fraserlw@netscape.net> wrote in message
news:ed6uFOk1EHA.3596@TK2MSFTNGP12.phx.gbl...
> Started with 3 computers on a test network:
> Computer 1 was NT4 PDC
> Computer 2 is w2000 server as a plain server
> Computer 3 is a NT4 BDC
> Upgraded Computer 1 to W2000 server and installed Active Directory.
> Then installed DNS
> Can see all computers and ping them
> Left other 2 computers as is.
> On computer 1 - simple and recursive DNS queries pass test.
> Then tried to install Active Dir on Computer 2 - Get error:
> "Specified Domain either does not exist or could not be contacted"
> Run DCDIAG on Computer 1. Result:
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial non skippeable tests
>
> Testing server: Default-First-Site-Name\SERVER
> Starting test: Connectivity
> SERVER'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
> (b8fae8ad-5dca-472f-959e-049784de0a45._msdcs.domain.com)
> couldn't be resolved, the server name (server.domain.com)
> resolved to the IP address (192.168.1.99) and was pingable.
> Check that the IP address is registered correctly with the DNS server.
> ......................... SERVER failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SERVER
> Skipping all tests, because server SERVER is
> not responding to directory service requests
>
> Running enterprise tests on : domain.com
> Starting test: Intersite
> ......................... domain.com passed test Intersite
> Starting test: FsmoCheck
> ......................... domain.com passed test FsmoCheck
>
> Results from netdiag:
>
> Computer Name: server
> DNS Host Name: server.domain.com
> System info : Windows 2000 Server (Build 2195)
> Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
> List of installed hotfixes :
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : server
> IP Address . . . . . . . . : 192.168.1.99
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.1
> Dns Servers. . . . . . . . : 192.168.1.99
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
>
> 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_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
> 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 . . . . . . . . . . . . . : Failed
> [WARNING] The DNS entries for this DC are not registered correctly
> on DNS server '192.168.1.99'. Please wait for 30 minutes for DNS server
> replication.
> [FATAL] No DNS servers have the DNS records for this DC registered.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
> 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 'server.domain.com'.
>
>
> 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
>
>
> Guessing that this is preventing me setting up Computer 2 as a DC. How
> do I get the GUID name to resolve? Or are there other problems to deal
> with first?
>
> Thanks

 

[Larry]

Archived from groups: microsoft.public.win2000.setup (More info?)

Computer 2 is pointed at computer 1 for dns
Computer 1 was pointed to itself for DNS. It seems to be missing the
_msdcs/, _kerberos and _ldap entries in the DNS Manager
Since this network is comprised of just the 3 computers with no internet
access, I have no other dns server to point it to. It does have the
Netlogoin.dns file with what looks like valid entries, but since this is
the first w2000 network I've set up thats only a guess


Danny Sanders wrote:

> Does computer 2 point to computer 1 for DNS in the properties of TCP/IP?
>
> Does your AD DNS server have all the proper DNS records?
> See:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;241515
>
>
> If not does your AD DNS server point to itself for DNS in the properties of
> TCP/IP?
>
>
> hth
> DDS W 2k MVP MCSE
>
> "larry" <fraserlw@netscape.net> wrote in message
> news:ed6uFOk1EHA.3596@TK2MSFTNGP12.phx.gbl...
>
>>Started with 3 computers on a test network:
>>Computer 1 was NT4 PDC
>>Computer 2 is w2000 server as a plain server
>>Computer 3 is a NT4 BDC
>>Upgraded Computer 1 to W2000 server and installed Active Directory.
>>Then installed DNS
>>Can see all computers and ping them
>>Left other 2 computers as is.
>>On computer 1 - simple and recursive DNS queries pass test.
>>Then tried to install Active Dir on Computer 2 - Get error:
>>"Specified Domain either does not exist or could not be contacted"
>>Run DCDIAG on Computer 1. Result:
>>Performing initial setup:
>> Done gathering initial info.
>>
>>Doing initial non skippeable tests
>>
>> Testing server: Default-First-Site-Name\SERVER
>> Starting test: Connectivity
>> SERVER'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
>> (b8fae8ad-5dca-472f-959e-049784de0a45._msdcs.domain.com)
>> couldn't be resolved, the server name (server.domain.com)
>> resolved to the IP address (192.168.1.99) and was pingable.
>>Check that the IP address is registered correctly with the DNS server.
>> ......................... SERVER failed test Connectivity
>>
>>Doing primary tests
>>
>> Testing server: Default-First-Site-Name\SERVER
>> Skipping all tests, because server SERVER is
>> not responding to directory service requests
>>
>> Running enterprise tests on : domain.com
>> Starting test: Intersite
>> ......................... domain.com passed test Intersite
>> Starting test: FsmoCheck
>> ......................... domain.com passed test FsmoCheck
>>
>>Results from netdiag:
>>
>> Computer Name: server
>> DNS Host Name: server.domain.com
>> System info : Windows 2000 Server (Build 2195)
>> Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
>> List of installed hotfixes :
>> Q147222
>>
>>
>>Netcard queries test . . . . . . . : Passed
>>
>>
>>
>>Per interface results:
>>
>> Adapter : Local Area Connection
>>
>> Netcard queries test . . . : Passed
>>
>> Host Name. . . . . . . . . : server
>> IP Address . . . . . . . . : 192.168.1.99
>> Subnet Mask. . . . . . . . : 255.255.255.0
>> Default Gateway. . . . . . : 192.168.1.1
>> Dns Servers. . . . . . . . : 192.168.1.99
>>
>>
>> AutoConfiguration results. . . . . . : Passed
>>
>> Default gateway test . . . : Passed
>>
>> NetBT name test. . . . . . : Passed
>>
>> 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_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>> 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 . . . . . . . . . . . . . : Failed
>> [WARNING] The DNS entries for this DC are not registered correctly
>>on DNS server '192.168.1.99'. Please wait for 30 minutes for DNS server
>>replication.
>> [FATAL] No DNS servers have the DNS records for this DC registered.
>>
>>
>>Redir and Browser test . . . . . . : Passed
>> List of NetBt transports currently bound to the Redir
>> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>> The redir is bound to 1 NetBt transport.
>>
>> List of NetBt transports currently bound to the browser
>> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>> 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 'server.domain.com'.
>>
>>
>>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
>>
>>
>>Guessing that this is preventing me setting up Computer 2 as a DC. How
>>do I get the GUID name to resolve? Or are there other problems to deal
>>with first?
>>
>>Thanks
>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

See if this link helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;305967


hth
DDS W 2k MVP MCSE

"larry" <fraserlw@netscape.net> wrote in message
news:#soWSQl1EHA.3588@TK2MSFTNGP14.phx.gbl...
> Computer 2 is pointed at computer 1 for dns
> Computer 1 was pointed to itself for DNS. It seems to be missing the
> _msdcs/, _kerberos and _ldap entries in the DNS Manager
> Since this network is comprised of just the 3 computers with no internet
> access, I have no other dns server to point it to. It does have the
> Netlogoin.dns file with what looks like valid entries, but since this is
> the first w2000 network I've set up thats only a guess
>
>
> Danny Sanders wrote:
>
> > Does computer 2 point to computer 1 for DNS in the properties of TCP/IP?
> >
> > Does your AD DNS server have all the proper DNS records?
> > See:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;241515
> >
> >
> > If not does your AD DNS server point to itself for DNS in the properties
of
> > TCP/IP?
> >
> >
> > hth
> > DDS W 2k MVP MCSE
> >
> > "larry" <fraserlw@netscape.net> wrote in message
> > news:ed6uFOk1EHA.3596@TK2MSFTNGP12.phx.gbl...
> >
> >>Started with 3 computers on a test network:
> >>Computer 1 was NT4 PDC
> >>Computer 2 is w2000 server as a plain server
> >>Computer 3 is a NT4 BDC
> >>Upgraded Computer 1 to W2000 server and installed Active Directory.
> >>Then installed DNS
> >>Can see all computers and ping them
> >>Left other 2 computers as is.
> >>On computer 1 - simple and recursive DNS queries pass test.
> >>Then tried to install Active Dir on Computer 2 - Get error:
> >>"Specified Domain either does not exist or could not be contacted"
> >>Run DCDIAG on Computer 1. Result:
> >>Performing initial setup:
> >> Done gathering initial info.
> >>
> >>Doing initial non skippeable tests
> >>
> >> Testing server: Default-First-Site-Name\SERVER
> >> Starting test: Connectivity
> >> SERVER'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
> >> (b8fae8ad-5dca-472f-959e-049784de0a45._msdcs.domain.com)
> >> couldn't be resolved, the server name (server.domain.com)
> >> resolved to the IP address (192.168.1.99) and was pingable.
> >>Check that the IP address is registered correctly with the DNS server.
> >> ......................... SERVER failed test Connectivity
> >>
> >>Doing primary tests
> >>
> >> Testing server: Default-First-Site-Name\SERVER
> >> Skipping all tests, because server SERVER is
> >> not responding to directory service requests
> >>
> >> Running enterprise tests on : domain.com
> >> Starting test: Intersite
> >> ......................... domain.com passed test Intersite
> >> Starting test: FsmoCheck
> >> ......................... domain.com passed test FsmoCheck
> >>
> >>Results from netdiag:
> >>
> >> Computer Name: server
> >> DNS Host Name: server.domain.com
> >> System info : Windows 2000 Server (Build 2195)
> >> Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
> >> List of installed hotfixes :
> >> Q147222
> >>
> >>
> >>Netcard queries test . . . . . . . : Passed
> >>
> >>
> >>
> >>Per interface results:
> >>
> >> Adapter : Local Area Connection
> >>
> >> Netcard queries test . . . : Passed
> >>
> >> Host Name. . . . . . . . . : server
> >> IP Address . . . . . . . . : 192.168.1.99
> >> Subnet Mask. . . . . . . . : 255.255.255.0
> >> Default Gateway. . . . . . : 192.168.1.1
> >> Dns Servers. . . . . . . . : 192.168.1.99
> >>
> >>
> >> AutoConfiguration results. . . . . . : Passed
> >>
> >> Default gateway test . . . : Passed
> >>
> >> NetBT name test. . . . . . : Passed
> >>
> >> 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_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
> >> 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 . . . . . . . . . . . . . : Failed
> >> [WARNING] The DNS entries for this DC are not registered correctly
> >>on DNS server '192.168.1.99'. Please wait for 30 minutes for DNS server
> >>replication.
> >> [FATAL] No DNS servers have the DNS records for this DC registered.
> >>
> >>
> >>Redir and Browser test . . . . . . : Passed
> >> List of NetBt transports currently bound to the Redir
> >> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
> >> The redir is bound to 1 NetBt transport.
> >>
> >> List of NetBt transports currently bound to the browser
> >> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
> >> 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
'server.domain.com'.
> >>
> >>
> >>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
> >>
> >>
> >>Guessing that this is preventing me setting up Computer 2 as a DC. How
> >>do I get the GUID name to resolve? Or are there other problems to deal
> >>with first?
> >>
> >>Thanks
> >
> >
> >

 

[Larry]

Archived from groups: microsoft.public.win2000.setup (More info?)

Haven't had any time to work on this, but will try this asap. Thanks
for the assistance

Danny Sanders wrote:

> See if this link helps:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;305967
>
>
> hth
> DDS W 2k MVP MCSE
>
> "larry" <fraserlw@netscape.net> wrote in message
> news:#soWSQl1EHA.3588@TK2MSFTNGP14.phx.gbl...
>
>>Computer 2 is pointed at computer 1 for dns
>>Computer 1 was pointed to itself for DNS. It seems to be missing the
>>_msdcs/, _kerberos and _ldap entries in the DNS Manager
>>Since this network is comprised of just the 3 computers with no internet
>>access, I have no other dns server to point it to. It does have the
>>Netlogoin.dns file with what looks like valid entries, but since this is
>>the first w2000 network I've set up thats only a guess
>>
>>
>>Danny Sanders wrote:
>>
>>
>>>Does computer 2 point to computer 1 for DNS in the properties of TCP/IP?
>>>
>>>Does your AD DNS server have all the proper DNS records?
>>>See:
>>>http://support.microsoft.com/default.aspx?scid=kb;en-us;241515
>>>
>>>
>>>If not does your AD DNS server point to itself for DNS in the properties
>
> of
>
>>>TCP/IP?
>>>
>>>
>>>hth
>>>DDS W 2k MVP MCSE
>>>
>>>"larry" <fraserlw@netscape.net> wrote in message
>>>news:ed6uFOk1EHA.3596@TK2MSFTNGP12.phx.gbl...
>>>
>>>
>>>>Started with 3 computers on a test network:
>>>>Computer 1 was NT4 PDC
>>>>Computer 2 is w2000 server as a plain server
>>>>Computer 3 is a NT4 BDC
>>>>Upgraded Computer 1 to W2000 server and installed Active Directory.
>>>>Then installed DNS
>>>>Can see all computers and ping them
>>>>Left other 2 computers as is.
>>>>On computer 1 - simple and recursive DNS queries pass test.
>>>>Then tried to install Active Dir on Computer 2 - Get error:
>>>>"Specified Domain either does not exist or could not be contacted"
>>>>Run DCDIAG on Computer 1. Result:
>>>>Performing initial setup:
>>>> Done gathering initial info.
>>>>
>>>>Doing initial non skippeable tests
>>>>
>>>> Testing server: Default-First-Site-Name\SERVER
>>>> Starting test: Connectivity
>>>> SERVER'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
>>>> (b8fae8ad-5dca-472f-959e-049784de0a45._msdcs.domain.com)
>>>> couldn't be resolved, the server name (server.domain.com)
>>>> resolved to the IP address (192.168.1.99) and was pingable.
>>>>Check that the IP address is registered correctly with the DNS server.
>>>> ......................... SERVER failed test Connectivity
>>>>
>>>>Doing primary tests
>>>>
>>>> Testing server: Default-First-Site-Name\SERVER
>>>> Skipping all tests, because server SERVER is
>>>> not responding to directory service requests
>>>>
>>>> Running enterprise tests on : domain.com
>>>> Starting test: Intersite
>>>> ......................... domain.com passed test Intersite
>>>> Starting test: FsmoCheck
>>>> ......................... domain.com passed test FsmoCheck
>>>>
>>>>Results from netdiag:
>>>>
>>>> Computer Name: server
>>>> DNS Host Name: server.domain.com
>>>> System info : Windows 2000 Server (Build 2195)
>>>> Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
>>>> List of installed hotfixes :
>>>> Q147222
>>>>
>>>>
>>>>Netcard queries test . . . . . . . : Passed
>>>>
>>>>
>>>>
>>>>Per interface results:
>>>>
>>>> Adapter : Local Area Connection
>>>>
>>>> Netcard queries test . . . : Passed
>>>>
>>>> Host Name. . . . . . . . . : server
>>>> IP Address . . . . . . . . : 192.168.1.99
>>>> Subnet Mask. . . . . . . . : 255.255.255.0
>>>> Default Gateway. . . . . . : 192.168.1.1
>>>> Dns Servers. . . . . . . . : 192.168.1.99
>>>>
>>>>
>>>> AutoConfiguration results. . . . . . : Passed
>>>>
>>>> Default gateway test . . . : Passed
>>>>
>>>> NetBT name test. . . . . . : Passed
>>>>
>>>> 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_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>>>> 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 . . . . . . . . . . . . . : Failed
>>>> [WARNING] The DNS entries for this DC are not registered correctly
>>>>on DNS server '192.168.1.99'. Please wait for 30 minutes for DNS server
>>>>replication.
>>>> [FATAL] No DNS servers have the DNS records for this DC registered.
>>>>
>>>>
>>>>Redir and Browser test . . . . . . : Passed
>>>> List of NetBt transports currently bound to the Redir
>>>> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>>>> The redir is bound to 1 NetBt transport.
>>>>
>>>> List of NetBt transports currently bound to the browser
>>>> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>>>> 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
>
> 'server.domain.com'.
>
>>>>
>>>>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
>>>>
>>>>
>>>>Guessing that this is preventing me setting up Computer 2 as a DC. How
>>>>do I get the GUID name to resolve? Or are there other problems to deal
>>>>with first?
>>>>
>>>>Thanks
>>>
>>>
>>>
>
>

 

[Larry]

Archived from groups: microsoft.public.win2000.setup (More info?)

Got it fixed - Thanks

Danny Sanders wrote:
> See if this link helps:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;305967
>
>
> hth
> DDS W 2k MVP MCSE
>
> "larry" <fraserlw@netscape.net> wrote in message
> news:#soWSQl1EHA.3588@TK2MSFTNGP14.phx.gbl...
>
>>Computer 2 is pointed at computer 1 for dns
>>Computer 1 was pointed to itself for DNS. It seems to be missing the
>>_msdcs/, _kerberos and _ldap entries in the DNS Manager
>>Since this network is comprised of just the 3 computers with no internet
>>access, I have no other dns server to point it to. It does have the
>>Netlogoin.dns file with what looks like valid entries, but since this is
>>the first w2000 network I've set up thats only a guess
>>
>>
>>Danny Sanders wrote:
>>
>>
>>>Does computer 2 point to computer 1 for DNS in the properties of TCP/IP?
>>>
>>>Does your AD DNS server have all the proper DNS records?
>>>See:
>>>http://support.microsoft.com/default.aspx?scid=kb;en-us;241515
>>>
>>>
>>>If not does your AD DNS server point to itself for DNS in the properties
>
> of
>
>>>TCP/IP?
>>>
>>>
>>>hth
>>>DDS W 2k MVP MCSE
>>>
>>>"larry" <fraserlw@netscape.net> wrote in message
>>>news:ed6uFOk1EHA.3596@TK2MSFTNGP12.phx.gbl...
>>>
>>>
>>>>Started with 3 computers on a test network:
>>>>Computer 1 was NT4 PDC
>>>>Computer 2 is w2000 server as a plain server
>>>>Computer 3 is a NT4 BDC
>>>>Upgraded Computer 1 to W2000 server and installed Active Directory.
>>>>Then installed DNS
>>>>Can see all computers and ping them
>>>>Left other 2 computers as is.
>>>>On computer 1 - simple and recursive DNS queries pass test.
>>>>Then tried to install Active Dir on Computer 2 - Get error:
>>>>"Specified Domain either does not exist or could not be contacted"
>>>>Run DCDIAG on Computer 1. Result:
>>>>Performing initial setup:
>>>> Done gathering initial info.
>>>>
>>>>Doing initial non skippeable tests
>>>>
>>>> Testing server: Default-First-Site-Name\SERVER
>>>> Starting test: Connectivity
>>>> SERVER'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
>>>> (b8fae8ad-5dca-472f-959e-049784de0a45._msdcs.domain.com)
>>>> couldn't be resolved, the server name (server.domain.com)
>>>> resolved to the IP address (192.168.1.99) and was pingable.
>>>>Check that the IP address is registered correctly with the DNS server.
>>>> ......................... SERVER failed test Connectivity
>>>>
>>>>Doing primary tests
>>>>
>>>> Testing server: Default-First-Site-Name\SERVER
>>>> Skipping all tests, because server SERVER is
>>>> not responding to directory service requests
>>>>
>>>> Running enterprise tests on : domain.com
>>>> Starting test: Intersite
>>>> ......................... domain.com passed test Intersite
>>>> Starting test: FsmoCheck
>>>> ......................... domain.com passed test FsmoCheck
>>>>
>>>>Results from netdiag:
>>>>
>>>> Computer Name: server
>>>> DNS Host Name: server.domain.com
>>>> System info : Windows 2000 Server (Build 2195)
>>>> Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
>>>> List of installed hotfixes :
>>>> Q147222
>>>>
>>>>
>>>>Netcard queries test . . . . . . . : Passed
>>>>
>>>>
>>>>
>>>>Per interface results:
>>>>
>>>> Adapter : Local Area Connection
>>>>
>>>> Netcard queries test . . . : Passed
>>>>
>>>> Host Name. . . . . . . . . : server
>>>> IP Address . . . . . . . . : 192.168.1.99
>>>> Subnet Mask. . . . . . . . : 255.255.255.0
>>>> Default Gateway. . . . . . : 192.168.1.1
>>>> Dns Servers. . . . . . . . : 192.168.1.99
>>>>
>>>>
>>>> AutoConfiguration results. . . . . . : Passed
>>>>
>>>> Default gateway test . . . : Passed
>>>>
>>>> NetBT name test. . . . . . : Passed
>>>>
>>>> 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_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>>>> 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 . . . . . . . . . . . . . : Failed
>>>> [WARNING] The DNS entries for this DC are not registered correctly
>>>>on DNS server '192.168.1.99'. Please wait for 30 minutes for DNS server
>>>>replication.
>>>> [FATAL] No DNS servers have the DNS records for this DC registered.
>>>>
>>>>
>>>>Redir and Browser test . . . . . . : Passed
>>>> List of NetBt transports currently bound to the Redir
>>>> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>>>> The redir is bound to 1 NetBt transport.
>>>>
>>>> List of NetBt transports currently bound to the browser
>>>> NetBT_Tcpip_{58D64DD9-672C-45D8-97E5-2B94F38E23F3}
>>>> 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
>
> 'server.domain.com'.
>
>>>>
>>>>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
>>>>
>>>>
>>>>Guessing that this is preventing me setting up Computer 2 as a DC. How
>>>>do I get the GUID name to resolve? Or are there other problems to deal
>>>>with first?
>>>>
>>>>Thanks
>>>
>>>
>>>
>
>