dcdiag help

i cannot figure out what is wrong with my domain. I am running server 2k3
with AD and wins installed. dns is not installed. as of last monday (the
20th) everything was good. I come to work today (the 27th) and my server
cannot see anything in the network. i browse network neighborhood and no
system appears. if i am on a workstation and browse network neighborhood, all
systems appear except the server. here is what i get from dcdiag.exe...


C:\Documents and Settings\Administrator>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\AFSCME57SVR1
Starting test: Connectivity
The host
065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
uld not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
couldn't
be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG) resolved
to the IP address (192.168.1.1) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... AFSCME57SVR1 failed test Connectivity

Doing primary tests

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

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : CA
Starting test: CrossRefValidation
......................... CA passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... CA passed test CheckSDRefDom

Running enterprise tests on : CA.AFSCME57.ORG
Starting test: Intersite
......................... CA.AFSCME57.ORG passed test Intersite
Starting test: FsmoCheck
......................... CA.AFSCME57.ORG passed test FsmoCheck

C:\Documents and Settings\Administrator>


any help will be greatly appreciated.

Andy

>i cannot figure out what is wrong with my domain. I am running server 2k3
> with AD and wins installed. dns is not installed.

Ad totally relies on DNS being set up properly. Do you have DNS running
*somewhere* on the domain? What do your clients list for preferred DNS
server?


DDS
"neves7" <> wrote in message
news:30DE8A3C-FAC5-43AB-8C79-...
>i cannot figure out what is wrong with my domain. I am running server 2k3
> with AD and wins installed. dns is not installed. as of last monday (the
> 20th) everything was good. I come to work today (the 27th) and my server
> cannot see anything in the network. i browse network neighborhood and no
> system appears. if i am on a workstation and browse network neighborhood,
> all
> systems appear except the server. here is what i get from dcdiag.exe...
>
>
> C:\Documents and Settings\Administrator>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\AFSCME57SVR1
> Starting test: Connectivity
> The host
> 065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
> uld not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
> couldn't
> be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG)
> resolved
> to the IP address (192.168.1.1) and was pingable. Check that the
> IP
> address is registered correctly with the DNS server.
> ......................... AFSCME57SVR1 failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\AFSCME57SVR1
> Skipping all tests, because server AFSCME57SVR1 is
> not responding to directory service requests
>
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> ......................... ForestDnsZones passed test
> CrossRefValidation
>
> Starting test: CheckSDRefDom
> ......................... ForestDnsZones passed test CheckSDRefDom
>
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> ......................... DomainDnsZones passed test
> CrossRefValidation
>
> Starting test: CheckSDRefDom
> ......................... DomainDnsZones passed test CheckSDRefDom
>
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> ......................... Schema passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Schema passed test CheckSDRefDom
>
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> ......................... Configuration passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Configuration passed test CheckSDRefDom
>
> Running partition tests on : CA
> Starting test: CrossRefValidation
> ......................... CA passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... CA passed test CheckSDRefDom
>
> Running enterprise tests on : CA.AFSCME57.ORG
> Starting test: Intersite
> ......................... CA.AFSCME57.ORG passed test Intersite
> Starting test: FsmoCheck
> ......................... CA.AFSCME57.ORG passed test FsmoCheck
>
> C:\Documents and Settings\Administrator>
>
>
> any help will be greatly appreciated.
>
> Andy

the clients use the ISP dns server IP's. My domain name is not a public
registered domain.

Andy


"Danny Sanders" wrote:

> >i cannot figure out what is wrong with my domain. I am running server 2k3
> > with AD and wins installed. dns is not installed.
>
> Ad totally relies on DNS being set up properly. Do you have DNS running
> *somewhere* on the domain? What do your clients list for preferred DNS
> server?
>
>
> DDS
> "neves7" <> wrote in message
> news:30DE8A3C-FAC5-43AB-8C79-...
> >i cannot figure out what is wrong with my domain. I am running server 2k3
> > with AD and wins installed. dns is not installed. as of last monday (the
> > 20th) everything was good. I come to work today (the 27th) and my server
> > cannot see anything in the network. i browse network neighborhood and no
> > system appears. if i am on a workstation and browse network neighborhood,
> > all
> > systems appear except the server. here is what i get from dcdiag.exe...
> >
> >
> > C:\Documents and Settings\Administrator>dcdiag
> >
> > Domain Controller Diagnosis
> >
> > Performing initial setup:
> > Done gathering initial info.
> >
> > Doing initial required tests
> >
> > Testing server: Default-First-Site-Name\AFSCME57SVR1
> > Starting test: Connectivity
> > The host
> > 065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
> > uld not be resolved to an
> > IP address. Check the DNS server, DHCP, server name, etc
> > Although the Guid DNS name
> > (065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
> > couldn't
> > be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG)
> > resolved
> > to the IP address (192.168.1.1) and was pingable. Check that the
> > IP
> > address is registered correctly with the DNS server.
> > ......................... AFSCME57SVR1 failed test Connectivity
> >
> > Doing primary tests
> >
> > Testing server: Default-First-Site-Name\AFSCME57SVR1
> > Skipping all tests, because server AFSCME57SVR1 is
> > not responding to directory service requests
> >
> > Running partition tests on : ForestDnsZones
> > Starting test: CrossRefValidation
> > ......................... ForestDnsZones passed test
> > CrossRefValidation
> >
> > Starting test: CheckSDRefDom
> > ......................... ForestDnsZones passed test CheckSDRefDom
> >
> > Running partition tests on : DomainDnsZones
> > Starting test: CrossRefValidation
> > ......................... DomainDnsZones passed test
> > CrossRefValidation
> >
> > Starting test: CheckSDRefDom
> > ......................... DomainDnsZones passed test CheckSDRefDom
> >
> > Running partition tests on : Schema
> > Starting test: CrossRefValidation
> > ......................... Schema passed test CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... Schema passed test CheckSDRefDom
> >
> > Running partition tests on : Configuration
> > Starting test: CrossRefValidation
> > ......................... Configuration passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... Configuration passed test CheckSDRefDom
> >
> > Running partition tests on : CA
> > Starting test: CrossRefValidation
> > ......................... CA passed test CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... CA passed test CheckSDRefDom
> >
> > Running enterprise tests on : CA.AFSCME57.ORG
> > Starting test: Intersite
> > ......................... CA.AFSCME57.ORG passed test Intersite
> > Starting test: FsmoCheck
> > ......................... CA.AFSCME57.ORG passed test FsmoCheck
> >
> > C:\Documents and Settings\Administrator>
> >
> >
> > any help will be greatly appreciated.
> >
> > Andy
>
>
>

> the clients use the ISP dns server IP's. My domain name is not a public
> registered domain.

Using your ISP's DNS server for your AD domain will cause long log in times,
group policy will not work, adding computers to the domain will not work,
and whole list of other problems.
It does not matter if this is a private domain.

You MUST have a DNS server set up for the AD domain. NOT your ISP's DNS
server either. Your AD clients MUST find the SRV records for your AD domain
in order to "find" the AD domain. Your ISP will not nor do you want them
registering the srv records for your private domain on their "public" DNS
server.

Basic AD DNS set up is install DNS on your AD server. In the properties of
TCP/IP point your AD DNS server to itself for DNS resolution. When you
reboot the proper srv records will get registered in the DNS zone your AD
DNS server holds.
See:
http://support.microsoft.com:80/kb/814591/en-us

Point all AD clients to the DNS server set up for the AD domain ONLY.
Remember servers of the AD domain are AD clients also.

See:
http://support.microsoft.com/kb/825036/en-us


For Internet access set up your AD DNS server to forward requests and list
your ISP's DNS server(s) as the forwarders (or use root hints). This is the
ONLY place on your AD domain your ISP's DNS server should be listed.
See:
http://support.microsoft.com/kb/323380/en-us

Those 3 articles will walk you through installing and setting up DNS to
support an AD domain.


hth
DDS
"neves7" <> wrote in message
news:A1026CF8-41C2-4CA8-A3C6-...
> the clients use the ISP dns server IP's. My domain name is not a public
> registered domain.
>
> Andy
>
>
> "Danny Sanders" wrote:
>
>> >i cannot figure out what is wrong with my domain. I am running server
>> >2k3
>> > with AD and wins installed. dns is not installed.
>>
>> Ad totally relies on DNS being set up properly. Do you have DNS running
>> *somewhere* on the domain? What do your clients list for preferred DNS
>> server?
>>
>>
>> DDS
>> "neves7" <> wrote in message
>> news:30DE8A3C-FAC5-43AB-8C79-...
>> >i cannot figure out what is wrong with my domain. I am running server
>> >2k3
>> > with AD and wins installed. dns is not installed. as of last monday
>> > (the
>> > 20th) everything was good. I come to work today (the 27th) and my
>> > server
>> > cannot see anything in the network. i browse network neighborhood and
>> > no
>> > system appears. if i am on a workstation and browse network
>> > neighborhood,
>> > all
>> > systems appear except the server. here is what i get from dcdiag.exe...
>> >
>> >
>> > C:\Documents and Settings\Administrator>dcdiag
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: Default-First-Site-Name\AFSCME57SVR1
>> > Starting test: Connectivity
>> > The host
>> > 065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
>> > uld not be resolved to an
>> > IP address. Check the DNS server, DHCP, server name, etc
>> > Although the Guid DNS name
>> > (065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
>> > couldn't
>> > be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG)
>> > resolved
>> > to the IP address (192.168.1.1) and was pingable. Check that
>> > the
>> > IP
>> > address is registered correctly with the DNS server.
>> > ......................... AFSCME57SVR1 failed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: Default-First-Site-Name\AFSCME57SVR1
>> > Skipping all tests, because server AFSCME57SVR1 is
>> > not responding to directory service requests
>> >
>> > Running partition tests on : ForestDnsZones
>> > Starting test: CrossRefValidation
>> > ......................... ForestDnsZones passed test
>> > CrossRefValidation
>> >
>> > Starting test: CheckSDRefDom
>> > ......................... ForestDnsZones passed test
>> > CheckSDRefDom
>> >
>> > Running partition tests on : DomainDnsZones
>> > Starting test: CrossRefValidation
>> > ......................... DomainDnsZones passed test
>> > CrossRefValidation
>> >
>> > Starting test: CheckSDRefDom
>> > ......................... DomainDnsZones passed test
>> > CheckSDRefDom
>> >
>> > Running partition tests on : Schema
>> > Starting test: CrossRefValidation
>> > ......................... Schema passed test CrossRefValidation
>> > Starting test: CheckSDRefDom
>> > ......................... Schema passed test CheckSDRefDom
>> >
>> > Running partition tests on : Configuration
>> > Starting test: CrossRefValidation
>> > ......................... Configuration passed test
>> > CrossRefValidation
>> > Starting test: CheckSDRefDom
>> > ......................... Configuration passed test
>> > CheckSDRefDom
>> >
>> > Running partition tests on : CA
>> > Starting test: CrossRefValidation
>> > ......................... CA passed test CrossRefValidation
>> > Starting test: CheckSDRefDom
>> > ......................... CA passed test CheckSDRefDom
>> >
>> > Running enterprise tests on : CA.AFSCME57.ORG
>> > Starting test: Intersite
>> > ......................... CA.AFSCME57.ORG passed test Intersite
>> > Starting test: FsmoCheck
>> > ......................... CA.AFSCME57.ORG passed test FsmoCheck
>> >
>> > C:\Documents and Settings\Administrator>
>> >
>> >
>> > any help will be greatly appreciated.
>> >
>> > Andy
>>
>>
>>

OK, i installed DNS per your recommendation and setup the way the microsoft
articles suggested. rebooted the server, pointed all workstations to the
server for DNS. All XP systems still can get to the internet, also they can
still access the shared drives on the server. But, i still cant see the
server through my network places. Do i need to let it replicate longer? here
is the lates dcdiag...

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\AFSCME57SVR1
Starting test: Connectivity
The host
065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
uld not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
couldn't
be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG) resolved
to the IP address (192.168.1.1) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... AFSCME57SVR1 failed test Connectivity

Doing primary tests

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

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : CA
Starting test: CrossRefValidation
......................... CA passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... CA passed test CheckSDRefDom

Running enterprise tests on : CA.AFSCME57.ORG
Starting test: Intersite
......................... CA.AFSCME57.ORG passed test Intersite
Starting test: FsmoCheck
......................... CA.AFSCME57.ORG passed test FsmoCheck

Andy


"Danny Sanders" wrote:

> > the clients use the ISP dns server IP's. My domain name is not a public
> > registered domain.
>
> Using your ISP's DNS server for your AD domain will cause long log in times,
> group policy will not work, adding computers to the domain will not work,
> and whole list of other problems.
> It does not matter if this is a private domain.
>
> You MUST have a DNS server set up for the AD domain. NOT your ISP's DNS
> server either. Your AD clients MUST find the SRV records for your AD domain
> in order to "find" the AD domain. Your ISP will not nor do you want them
> registering the srv records for your private domain on their "public" DNS
> server.
>
> Basic AD DNS set up is install DNS on your AD server. In the properties of
> TCP/IP point your AD DNS server to itself for DNS resolution. When you
> reboot the proper srv records will get registered in the DNS zone your AD
> DNS server holds.
> See:
> http://support.microsoft.com:80/kb/814591/en-us
>
> Point all AD clients to the DNS server set up for the AD domain ONLY.
> Remember servers of the AD domain are AD clients also.
>
> See:
> http://support.microsoft.com/kb/825036/en-us
>
>
> For Internet access set up your AD DNS server to forward requests and list
> your ISP's DNS server(s) as the forwarders (or use root hints). This is the
> ONLY place on your AD domain your ISP's DNS server should be listed.
> See:
> http://support.microsoft.com/kb/323380/en-us
>
> Those 3 articles will walk you through installing and setting up DNS to
> support an AD domain.
>
>
> hth
> DDS
> "neves7" <> wrote in message
> news:A1026CF8-41C2-4CA8-A3C6-...
> > the clients use the ISP dns server IP's. My domain name is not a public
> > registered domain.
> >
> > Andy
> >
> >
> > "Danny Sanders" wrote:
> >
> >> >i cannot figure out what is wrong with my domain. I am running server
> >> >2k3
> >> > with AD and wins installed. dns is not installed.
> >>
> >> Ad totally relies on DNS being set up properly. Do you have DNS running
> >> *somewhere* on the domain? What do your clients list for preferred DNS
> >> server?
> >>
> >>
> >> DDS
> >> "neves7" <> wrote in message
> >> news:30DE8A3C-FAC5-43AB-8C79-...
> >> >i cannot figure out what is wrong with my domain. I am running server
> >> >2k3
> >> > with AD and wins installed. dns is not installed. as of last monday
> >> > (the
> >> > 20th) everything was good. I come to work today (the 27th) and my
> >> > server
> >> > cannot see anything in the network. i browse network neighborhood and
> >> > no
> >> > system appears. if i am on a workstation and browse network
> >> > neighborhood,
> >> > all
> >> > systems appear except the server. here is what i get from dcdiag.exe...
> >> >
> >> >
> >> > C:\Documents and Settings\Administrator>dcdiag
> >> >
> >> > Domain Controller Diagnosis
> >> >
> >> > Performing initial setup:
> >> > Done gathering initial info.
> >> >
> >> > Doing initial required tests
> >> >
> >> > Testing server: Default-First-Site-Name\AFSCME57SVR1
> >> > Starting test: Connectivity
> >> > The host
> >> > 065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
> >> > uld not be resolved to an
> >> > IP address. Check the DNS server, DHCP, server name, etc
> >> > Although the Guid DNS name
> >> > (065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
> >> > couldn't
> >> > be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG)
> >> > resolved
> >> > to the IP address (192.168.1.1) and was pingable. Check that
> >> > the
> >> > IP
> >> > address is registered correctly with the DNS server.
> >> > ......................... AFSCME57SVR1 failed test Connectivity
> >> >
> >> > Doing primary tests
> >> >
> >> > Testing server: Default-First-Site-Name\AFSCME57SVR1
> >> > Skipping all tests, because server AFSCME57SVR1 is
> >> > not responding to directory service requests
> >> >
> >> > Running partition tests on : ForestDnsZones
> >> > Starting test: CrossRefValidation
> >> > ......................... ForestDnsZones passed test
> >> > CrossRefValidation
> >> >
> >> > Starting test: CheckSDRefDom
> >> > ......................... ForestDnsZones passed test
> >> > CheckSDRefDom
> >> >
> >> > Running partition tests on : DomainDnsZones
> >> > Starting test: CrossRefValidation
> >> > ......................... DomainDnsZones passed test
> >> > CrossRefValidation
> >> >
> >> > Starting test: CheckSDRefDom
> >> > ......................... DomainDnsZones passed test
> >> > CheckSDRefDom
> >> >
> >> > Running partition tests on : Schema
> >> > Starting test: CrossRefValidation
> >> > ......................... Schema passed test CrossRefValidation
> >> > Starting test: CheckSDRefDom
> >> > ......................... Schema passed test CheckSDRefDom
> >> >
> >> > Running partition tests on : Configuration
> >> > Starting test: CrossRefValidation
> >> > ......................... Configuration passed test
> >> > CrossRefValidation
> >> > Starting test: CheckSDRefDom
> >> > ......................... Configuration passed test
> >> > CheckSDRefDom
> >> >
> >> > Running partition tests on : CA
> >> > Starting test: CrossRefValidation
> >> > ......................... CA passed test CrossRefValidation
> >> > Starting test: CheckSDRefDom
> >> > ......................... CA passed test CheckSDRefDom
> >> >
> >> > Running enterprise tests on : CA.AFSCME57.ORG
> >> > Starting test: Intersite
> >> > ......................... CA.AFSCME57.ORG passed test Intersite
> >> > Starting test: FsmoCheck
> >> > ......................... CA.AFSCME57.ORG passed test FsmoCheck
> >> >
> >> > C:\Documents and Settings\Administrator>
> >> >
> >> >
> >> > any help will be greatly appreciated.
> >> >
> >> > Andy
> >>
> >>
> >>
>
>
>

From your DNS server:
You might try running ipconfig /registerdns then check dcdiag.

You can also try running netdiag /fix

hth
DDS

"neves7" <> wrote in message
news:9681E61F-57E5-4031-A0A9-...
> OK, i installed DNS per your recommendation and setup the way the
> microsoft
> articles suggested. rebooted the server, pointed all workstations to the
> server for DNS. All XP systems still can get to the internet, also they
> can
> still access the shared drives on the server. But, i still cant see the
> server through my network places. Do i need to let it replicate longer?
> here
> is the lates dcdiag...
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\AFSCME57SVR1
> Starting test: Connectivity
> The host
> 065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
> uld not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
> couldn't
> be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG)
> resolved
> to the IP address (192.168.1.1) and was pingable. Check that the
> IP
> address is registered correctly with the DNS server.
> ......................... AFSCME57SVR1 failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\AFSCME57SVR1
> Skipping all tests, because server AFSCME57SVR1 is
> not responding to directory service requests
>
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> ......................... ForestDnsZones passed test
> CrossRefValidation
>
> Starting test: CheckSDRefDom
> ......................... ForestDnsZones passed test CheckSDRefDom
>
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> ......................... DomainDnsZones passed test
> CrossRefValidation
>
> Starting test: CheckSDRefDom
> ......................... DomainDnsZones passed test CheckSDRefDom
>
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> ......................... Schema passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Schema passed test CheckSDRefDom
>
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> ......................... Configuration passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Configuration passed test CheckSDRefDom
>
> Running partition tests on : CA
> Starting test: CrossRefValidation
> ......................... CA passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... CA passed test CheckSDRefDom
>
> Running enterprise tests on : CA.AFSCME57.ORG
> Starting test: Intersite
> ......................... CA.AFSCME57.ORG passed test Intersite
> Starting test: FsmoCheck
> ......................... CA.AFSCME57.ORG passed test FsmoCheck
>
> Andy
>
>
> "Danny Sanders" wrote:
>
>> > the clients use the ISP dns server IP's. My domain name is not a public
>> > registered domain.
>>
>> Using your ISP's DNS server for your AD domain will cause long log in
>> times,
>> group policy will not work, adding computers to the domain will not work,
>> and whole list of other problems.
>> It does not matter if this is a private domain.
>>
>> You MUST have a DNS server set up for the AD domain. NOT your ISP's DNS
>> server either. Your AD clients MUST find the SRV records for your AD
>> domain
>> in order to "find" the AD domain. Your ISP will not nor do you want them
>> registering the srv records for your private domain on their "public" DNS
>> server.
>>
>> Basic AD DNS set up is install DNS on your AD server. In the properties
>> of
>> TCP/IP point your AD DNS server to itself for DNS resolution. When you
>> reboot the proper srv records will get registered in the DNS zone your AD
>> DNS server holds.
>> See:
>> http://support.microsoft.com:80/kb/814591/en-us
>>
>> Point all AD clients to the DNS server set up for the AD domain ONLY.
>> Remember servers of the AD domain are AD clients also.
>>
>> See:
>> http://support.microsoft.com/kb/825036/en-us
>>
>>
>> For Internet access set up your AD DNS server to forward requests and
>> list
>> your ISP's DNS server(s) as the forwarders (or use root hints). This is
>> the
>> ONLY place on your AD domain your ISP's DNS server should be listed.
>> See:
>> http://support.microsoft.com/kb/323380/en-us
>>
>> Those 3 articles will walk you through installing and setting up DNS to
>> support an AD domain.
>>
>>
>> hth
>> DDS
>> "neves7" <> wrote in message
>> news:A1026CF8-41C2-4CA8-A3C6-...
>> > the clients use the ISP dns server IP's. My domain name is not a public
>> > registered domain.
>> >
>> > Andy
>> >
>> >
>> > "Danny Sanders" wrote:
>> >
>> >> >i cannot figure out what is wrong with my domain. I am running server
>> >> >2k3
>> >> > with AD and wins installed. dns is not installed.
>> >>
>> >> Ad totally relies on DNS being set up properly. Do you have DNS
>> >> running
>> >> *somewhere* on the domain? What do your clients list for preferred DNS
>> >> server?
>> >>
>> >>
>> >> DDS
>> >> "neves7" <> wrote in message
>> >> news:30DE8A3C-FAC5-43AB-8C79-...
>> >> >i cannot figure out what is wrong with my domain. I am running server
>> >> >2k3
>> >> > with AD and wins installed. dns is not installed. as of last monday
>> >> > (the
>> >> > 20th) everything was good. I come to work today (the 27th) and my
>> >> > server
>> >> > cannot see anything in the network. i browse network neighborhood
>> >> > and
>> >> > no
>> >> > system appears. if i am on a workstation and browse network
>> >> > neighborhood,
>> >> > all
>> >> > systems appear except the server. here is what i get from
>> >> > dcdiag.exe...
>> >> >
>> >> >
>> >> > C:\Documents and Settings\Administrator>dcdiag
>> >> >
>> >> > Domain Controller Diagnosis
>> >> >
>> >> > Performing initial setup:
>> >> > Done gathering initial info.
>> >> >
>> >> > Doing initial required tests
>> >> >
>> >> > Testing server: Default-First-Site-Name\AFSCME57SVR1
>> >> > Starting test: Connectivity
>> >> > The host
>> >> > 065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG co
>> >> > uld not be resolved to an
>> >> > IP address. Check the DNS server, DHCP, server name, etc
>> >> > Although the Guid DNS name
>> >> >
>> >> > (065caa73-489c-4e8d-b39f-a399dcb6c06f._msdcs.CA.AFSCME57.ORG)
>> >> > couldn't
>> >> > be resolved, the server name (afscme57svr1.CA.AFSCME57.ORG)
>> >> > resolved
>> >> > to the IP address (192.168.1.1) and was pingable. Check
>> >> > that
>> >> > the
>> >> > IP
>> >> > address is registered correctly with the DNS server.
>> >> > ......................... AFSCME57SVR1 failed test
>> >> > Connectivity
>> >> >
>> >> > Doing primary tests
>> >> >
>> >> > Testing server: Default-First-Site-Name\AFSCME57SVR1
>> >> > Skipping all tests, because server AFSCME57SVR1 is
>> >> > not responding to directory service requests
>> >> >
>> >> > Running partition tests on : ForestDnsZones
>> >> > Starting test: CrossRefValidation
>> >> > ......................... ForestDnsZones passed test
>> >> > CrossRefValidation
>> >> >
>> >> > Starting test: CheckSDRefDom
>> >> > ......................... ForestDnsZones passed test
>> >> > CheckSDRefDom
>> >> >
>> >> > Running partition tests on : DomainDnsZones
>> >> > Starting test: CrossRefValidation
>> >> > ......................... DomainDnsZones passed test
>> >> > CrossRefValidation
>> >> >
>> >> > Starting test: CheckSDRefDom
>> >> > ......................... DomainDnsZones passed test
>> >> > CheckSDRefDom
>> >> >
>> >> > Running partition tests on : Schema
>> >> > Starting test: CrossRefValidation
>> >> > ......................... Schema passed test
>> >> > CrossRefValidation
>> >> > Starting test: CheckSDRefDom
>> >> > ......................... Schema passed test CheckSDRefDom
>> >> >
>> >> > Running partition tests on : Configuration
>> >> > Starting test: CrossRefValidation
>> >> > ......................... Configuration passed test
>> >> > CrossRefValidation
>> >> > Starting test: CheckSDRefDom
>> >> > ......................... Configuration passed test
>> >> > CheckSDRefDom
>> >> >
>> >> > Running partition tests on : CA
>> >> > Starting test: CrossRefValidation
>> >> > ......................... CA passed test CrossRefValidation
>> >> > Starting test: CheckSDRefDom
>> >> > ......................... CA passed test CheckSDRefDom
>> >> >
>> >> > Running enterprise tests on : CA.AFSCME57.ORG
>> >> > Starting test: Intersite
>> >> > ......................... CA.AFSCME57.ORG passed test
>> >> > Intersite
>> >> > Starting test: FsmoCheck
>> >> > ......................... CA.AFSCME57.ORG passed test
>> >> > FsmoCheck
>> >> >
>> >> > C:\Documents and Settings\Administrator>
>> >> >
>> >> >
>> >> > any help will be greatly appreciated.
>> >> >
>> >> > Andy
>> >>
>> >>
>> >>
>>
>>
>>

I ran netdiag /fix and these are my results...i still cant see the rest of my
network, andy if I browse the network, nothing shows up still even though all
the shared drives still work.

C:\Documents and Settings\Administrator>ipconfig /registerdns

Windows IP Configuration

Registration of the DNS resource records for all adapters of this computer
has b
een initiated. Any errors will be reported in the Event Viewer in 15 minutes..

C:\Documents and Settings\Administrator>netdiag /fix

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

Computer Name: AFSCME57SVR1
DNS Host Name: afscme57svr1.CA.AFSCME57.ORG
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896424
KB896428
KB898715
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB904942
KB905414
KB908519
KB908531
KB910437
KB911164
KB911280
KB911562
KB911567
KB911927
KB912919
KB914388
KB914389
KB914783
KB917344
KB917422
KB917734
KB917953
KB917969
KB918439
KB918899
KB920213
KB920214
KB920670
KB920683
KB920685
KB921398
KB921883
KB922582
KB922616
KB922819
KB923191
KB923414
KB923980
KB924191
KB924496
KB925486
Q147222


Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Client
) #3' may not be working.



Per interface results:

Adapter : Local Area Connection 3

Netcard queries test . . . : Failed
NetCard Status: DISCONNECTED
Some tests will be skipped on this interface.

Host Name. . . . . . . . . : afscme57svr1
Autoconfiguration IP Address : 169.254.208.150
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :


Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : afscme57svr1
IP Address . . . . . . . . : 192.168.1.1
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.254
NetBIOS over Tcpip . . . . : Disabled
Dns Servers. . . . . . . . : 192.186.1.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Skipped
NetBT is disabled on this interface. [Test skipped]

WINS service test. . . . . : Skipped
NetBT is disable on this interface. [Test skipped].


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
1 NetBt transport currently configured.


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


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


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


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


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


DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be registered
in DN
S.
[WARNING] Cannot find a primary authoritative DNS server for the
name
'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be registered
in DN
S.
[WARNING] The DNS entries for this DC cannot be verified right now on
DNS
server 192.186.1.1, ERROR_TIMEOUT.
[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_{270160DE-EE27-455D-AB2C-4FEA85423510}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
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:\Documents and Settings\Administrator>

"Danny Sanders" wrote:

> From your DNS server:
> You might try running ipconfig /registerdns then check dcdiag.
>
> You can also try running netdiag /fix
>
> hth
> DDS

Do you have more than one network card in use on this computer?


DDS
"neves7" <> wrote in message
news:4B032C38-7B81-410F-9D0B-...
>I ran netdiag /fix and these are my results...i still cant see the rest of
>my
> network, andy if I browse the network, nothing shows up still even though
> all
> the shared drives still work.
>
> C:\Documents and Settings\Administrator>ipconfig /registerdns
>
> Windows IP Configuration
>
> Registration of the DNS resource records for all adapters of this computer
> has b
> een initiated. Any errors will be reported in the Event Viewer in 15
> minutes..
>
> C:\Documents and Settings\Administrator>netdiag /fix
>
> ....................................
>
> Computer Name: AFSCME57SVR1
> DNS Host Name: afscme57svr1.CA.AFSCME57.ORG
> System info : Microsoft Windows Server 2003 R2 (Build 3790)
> Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
> List of installed hotfixes :
> KB890046
> KB893756
> KB896358
> KB896424
> KB896428
> KB898715
> KB899587
> KB899588
> KB899589
> KB899591
> KB900725
> KB901017
> KB901214
> KB902400
> KB904706
> KB904942
> KB905414
> KB908519
> KB908531
> KB910437
> KB911164
> KB911280
> KB911562
> KB911567
> KB911927
> KB912919
> KB914388
> KB914389
> KB914783
> KB917344
> KB917422
> KB917734
> KB917953
> KB917969
> KB918439
> KB918899
> KB920213
> KB920214
> KB920670
> KB920683
> KB920685
> KB921398
> KB921883
> KB922582
> KB922616
> KB922819
> KB923191
> KB923414
> KB923980
> KB924191
> KB924496
> KB925486
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
> [WARNING] The net card 'Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
> Client
> ) #3' may not be working.
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection 3
>
> Netcard queries test . . . : Failed
> NetCard Status: DISCONNECTED
> Some tests will be skipped on this interface.
>
> Host Name. . . . . . . . . : afscme57svr1
> Autoconfiguration IP Address : 169.254.208.150
> Subnet Mask. . . . . . . . : 255.255.0.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . :
>
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : afscme57svr1
> IP Address . . . . . . . . : 192.168.1.1
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.254
> NetBIOS over Tcpip . . . . : Disabled
> Dns Servers. . . . . . . . : 192.186.1.1
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Skipped
> NetBT is disabled on this interface. [Test skipped]
>
> WINS service test. . . . . : Skipped
> NetBT is disable on this interface. [Test skipped].
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Passed
>
>
> NetBT name test. . . . . . . . . . : Passed
> [WARNING] You don't have a single interface with the <00> 'WorkStation
> Servi
> ce', <03> 'Messenger Service', <20> 'WINS' names defined.
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
> The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be registered
> in DN
> S.
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
> The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be registered
> in DN
> S.
> [WARNING] The DNS entries for this DC cannot be verified right now
> on
> DNS
> server 192.186.1.1, ERROR_TIMEOUT.
> [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_{270160DE-EE27-455D-AB2C-4FEA85423510}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
> 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:\Documents and Settings\Administrator>
>
> "Danny Sanders" wrote:
>
>> From your DNS server:
>> You might try running ipconfig /registerdns then check dcdiag.
>>
>> You can also try running netdiag /fix
>>
>> hth
>> DDS
>

> Host Name. . . . . . . . . : afscme57svr1
> IP Address . . . . . . . . : 192.168.1.1
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.254
> NetBIOS over Tcpip . . . . : Disabled
> Dns Servers. . . . . . . . : 192.186.1.1
>

Is this the actual IP address and DNS settings or a typo?

The IP address of this server is 192.168.1.1 but you have it pointed to
192.186.1.1 for DNS. Assuming this is the DNS server for the AD domain it
should list 192.168.1.1 as the DNS server.

If this is not a typo, change it then run ipconfig /flushdns followed by
ipconfig /registerdns, then check.

hth
DDS

"neves7" <> wrote in message
news:4B032C38-7B81-410F-9D0B-...
>I ran netdiag /fix and these are my results...i still cant see the rest of
>my
> network, andy if I browse the network, nothing shows up still even though
> all
> the shared drives still work.
>
> C:\Documents and Settings\Administrator>ipconfig /registerdns
>
> Windows IP Configuration
>
> Registration of the DNS resource records for all adapters of this computer
> has b
> een initiated. Any errors will be reported in the Event Viewer in 15
> minutes..
>
> C:\Documents and Settings\Administrator>netdiag /fix
>
> ....................................
>
> Computer Name: AFSCME57SVR1
> DNS Host Name: afscme57svr1.CA.AFSCME57.ORG
> System info : Microsoft Windows Server 2003 R2 (Build 3790)
> Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
> List of installed hotfixes :
> KB890046
> KB893756
> KB896358
> KB896424
> KB896428
> KB898715
> KB899587
> KB899588
> KB899589
> KB899591
> KB900725
> KB901017
> KB901214
> KB902400
> KB904706
> KB904942
> KB905414
> KB908519
> KB908531
> KB910437
> KB911164
> KB911280
> KB911562
> KB911567
> KB911927
> KB912919
> KB914388
> KB914389
> KB914783
> KB917344
> KB917422
> KB917734
> KB917953
> KB917969
> KB918439
> KB918899
> KB920213
> KB920214
> KB920670
> KB920683
> KB920685
> KB921398
> KB921883
> KB922582
> KB922616
> KB922819
> KB923191
> KB923414
> KB923980
> KB924191
> KB924496
> KB925486
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
> [WARNING] The net card 'Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
> Client
> ) #3' may not be working.
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection 3
>
> Netcard queries test . . . : Failed
> NetCard Status: DISCONNECTED
> Some tests will be skipped on this interface.
>
> Host Name. . . . . . . . . : afscme57svr1
> Autoconfiguration IP Address : 169.254.208.150
> Subnet Mask. . . . . . . . : 255.255.0.0
> Default Gateway. . . . . . :
> Dns Servers. . . . . . . . :
>
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : afscme57svr1
> IP Address . . . . . . . . : 192.168.1.1
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.254
> NetBIOS over Tcpip . . . . : Disabled
> Dns Servers. . . . . . . . : 192.186.1.1
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Skipped
> NetBT is disabled on this interface. [Test skipped]
>
> WINS service test. . . . . : Skipped
> NetBT is disable on this interface. [Test skipped].
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Passed
>
>
> NetBT name test. . . . . . . . . . : Passed
> [WARNING] You don't have a single interface with the <00> 'WorkStation
> Servi
> ce', <03> 'Messenger Service', <20> 'WINS' names defined.
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
> The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be registered
> in DN
> S.
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
> The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be registered
> in DN
> S.
> [WARNING] The DNS entries for this DC cannot be verified right now
> on
> DNS
> server 192.186.1.1, ERROR_TIMEOUT.
> [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_{270160DE-EE27-455D-AB2C-4FEA85423510}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
> 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:\Documents and Settings\Administrator>
>
> "Danny Sanders" wrote:
>
>> From your DNS server:
>> You might try running ipconfig /registerdns then check dcdiag.
>>
>> You can also try running netdiag /fix
>>
>> hth
>> DDS
>

>> > IP Address . . . . . . . . : 192.168.1.1
>> > Dns Servers. . . . . . . . : 192.186.1.1


From your post, these don't match.

DDS
"neves7" <> wrote in message
news:1F395EFC-3048-4CFF-A049-...
>I have 2 network cards in the server, only one is connected as of now. The
>IP
> of the server is 192.168.1.1 so the DNS server is also 192.168.1.1 because
> I
> only have 1 server on my network. The Domain Controller is also the DNS
> server.
>
>
>
> "Danny Sanders" wrote:
>
>> > Host Name. . . . . . . . . : afscme57svr1
>> > IP Address . . . . . . . . : 192.168.1.1
>> > Subnet Mask. . . . . . . . : 255.255.255.0
>> > Default Gateway. . . . . . : 192.168.1.254
>> > NetBIOS over Tcpip . . . . : Disabled
>> > Dns Servers. . . . . . . . : 192.186.1.1
>> >
>>
>> Is this the actual IP address and DNS settings or a typo?
>>
>> The IP address of this server is 192.168.1.1 but you have it pointed to
>> 192.186.1.1 for DNS. Assuming this is the DNS server for the AD domain it
>> should list 192.168.1.1 as the DNS server.
>>
>> If this is not a typo, change it then run ipconfig /flushdns followed by
>> ipconfig /registerdns, then check.
>>
>> hth
>> DDS
>>
>> "neves7" <> wrote in message
>> news:4B032C38-7B81-410F-9D0B-...
>> >I ran netdiag /fix and these are my results...i still cant see the rest
>> >of
>> >my
>> > network, andy if I browse the network, nothing shows up still even
>> > though
>> > all
>> > the shared drives still work.
>> >
>> > C:\Documents and Settings\Administrator>ipconfig /registerdns
>> >
>> > Windows IP Configuration
>> >
>> > Registration of the DNS resource records for all adapters of this
>> > computer
>> > has b
>> > een initiated. Any errors will be reported in the Event Viewer in 15
>> > minutes..
>> >
>> > C:\Documents and Settings\Administrator>netdiag /fix
>> >
>> > ....................................
>> >
>> > Computer Name: AFSCME57SVR1
>> > DNS Host Name: afscme57svr1.CA.AFSCME57.ORG
>> > System info : Microsoft Windows Server 2003 R2 (Build 3790)
>> > Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel
>> > List of installed hotfixes :
>> > KB890046
>> > KB893756
>> > KB896358
>> > KB896424
>> > KB896428
>> > KB898715
>> > KB899587
>> > KB899588
>> > KB899589
>> > KB899591
>> > KB900725
>> > KB901017
>> > KB901214
>> > KB902400
>> > KB904706
>> > KB904942
>> > KB905414
>> > KB908519
>> > KB908531
>> > KB910437
>> > KB911164
>> > KB911280
>> > KB911562
>> > KB911567
>> > KB911927
>> > KB912919
>> > KB914388
>> > KB914389
>> > KB914783
>> > KB917344
>> > KB917422
>> > KB917734
>> > KB917953
>> > KB917969
>> > KB918439
>> > KB918899
>> > KB920213
>> > KB920214
>> > KB920670
>> > KB920683
>> > KB920685
>> > KB921398
>> > KB921883
>> > KB922582
>> > KB922616
>> > KB922819
>> > KB923191
>> > KB923414
>> > KB923980
>> > KB924191
>> > KB924496
>> > KB925486
>> > Q147222
>> >
>> >
>> > Netcard queries test . . . . . . . : Passed
>> > [WARNING] The net card 'Broadcom BCM5708C NetXtreme II GigE (NDIS
>> > VBD
>> > Client
>> > ) #3' may not be working.
>> >
>> >
>> >
>> > Per interface results:
>> >
>> > Adapter : Local Area Connection 3
>> >
>> > Netcard queries test . . . : Failed
>> > NetCard Status: DISCONNECTED
>> > Some tests will be skipped on this interface.
>> >
>> > Host Name. . . . . . . . . : afscme57svr1
>> > Autoconfiguration IP Address : 169.254.208.150
>> > Subnet Mask. . . . . . . . : 255.255.0.0
>> > Default Gateway. . . . . . :
>> > Dns Servers. . . . . . . . :
>> >
>> >
>> > Adapter : Local Area Connection
>> >
>> > Netcard queries test . . . : Passed
>> >
>> > Host Name. . . . . . . . . : afscme57svr1
>> > IP Address . . . . . . . . : 192.168.1.1
>> > Subnet Mask. . . . . . . . : 255.255.255.0
>> > Default Gateway. . . . . . : 192.168.1.254
>> > NetBIOS over Tcpip . . . . : Disabled
>> > Dns Servers. . . . . . . . : 192.186.1.1
>> >
>> >
>> > AutoConfiguration results. . . . . . : Passed
>> >
>> > Default gateway test . . . : Passed
>> >
>> > NetBT name test. . . . . . : Skipped
>> > NetBT is disabled on this interface. [Test skipped]
>> >
>> > WINS service test. . . . . : Skipped
>> > NetBT is disable on this interface. [Test skipped].
>> >
>> >
>> > Global results:
>> >
>> >
>> > Domain membership test . . . . . . : Passed
>> >
>> >
>> > NetBT transports test. . . . . . . : Passed
>> > List of NetBt transports currently configured:
>> > NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
>> > 1 NetBt transport currently configured.
>> >
>> >
>> > Autonet address test . . . . . . . : Passed
>> >
>> >
>> > IP loopback ping test. . . . . . . : Passed
>> >
>> >
>> > Default gateway test . . . . . . . : Passed
>> >
>> >
>> > NetBT name test. . . . . . . . . . : Passed
>> > [WARNING] You don't have a single interface with the <00>
>> > 'WorkStation
>> > Servi
>> > ce', <03> 'Messenger Service', <20> 'WINS' names defined.
>> >
>> >
>> > Winsock test . . . . . . . . . . . : Passed
>> >
>> >
>> > DNS test . . . . . . . . . . . . . : Failed
>> > [WARNING] Cannot find a primary authoritative DNS server for
>> > the
>> > name
>> > 'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
>> > The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be
>> > registered
>> > in DN
>> > S.
>> > [WARNING] Cannot find a primary authoritative DNS server for
>> > the
>> > name
>> > 'afscme57svr1.CA.AFSCME57.ORG.'. [ERROR_TIMEOUT]
>> > The name 'afscme57svr1.CA.AFSCME57.ORG.' may not be
>> > registered
>> > in DN
>> > S.
>> > [WARNING] The DNS entries for this DC cannot be verified right
>> > now
>> > on
>> > DNS
>> > server 192.186.1.1, ERROR_TIMEOUT.
>> > [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_{270160DE-EE27-455D-AB2C-4FEA85423510}
>> > The redir is bound to 1 NetBt transport.
>> >
>> > List of NetBt transports currently bound to the browser
>> > NetBT_Tcpip_{270160DE-EE27-455D-AB2C-4FEA85423510}
>> > 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:\Documents and Settings\Administrator>
>> >
>> > "Danny Sanders" wrote:
>> >
>> >> From your DNS server:
>> >> You might try running ipconfig /registerdns then check dcdiag.
>> >>
>> >> You can also try running netdiag /fix
>> >>
>> >> hth
>> >> DDS
>> >
>>
>>
>>