«

Gang,

I have been working on trying to connect an XP workstation to a win 2003
server and seem to be having some DNS issues. The error message below is
from the XP workstation when I try to configure the client XP workstation to
the domain phoenix.com.

All computers have the latest and greatest patches and I can ping via name
and ip address to the server from the client and from the server to the
client via ip address. Also when I do an ns lookup on the server it comes
back with server01.phoenix.com, also on the workstation has the same
nslookup response

Server 172.16.0.2 /24
Workstation 172.16.0.5 /24
Server name Server
Domain=Phoenix.com

Not sure if what other infor you will need.

************************************************** *************
Note: This information is intended for a network administrator. If you are
not your network's administrator, notify the administrator that you received
this information, which has been recorded in the file
D:\WINDOWS\debug\dcdiag.txt.

DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain Phoenix.com:

The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com

The following domain controllers were identified by the query:

server01.phoenix.com

Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.

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

For information about correcting this problem, click Help.

***********************************************

did you hear "John West" <> say in
news:n35sd.174868$cJ3.155850@fed1read06:

> Gang,
>
> I have been working on trying to connect an XP workstation to a win
> 2003 server and seem to be having some DNS issues. The error message
> below is from the XP workstation when I try to configure the client XP
> workstation to the domain phoenix.com.
>
> All computers have the latest and greatest patches and I can ping via
> name and ip address to the server from the client and from the server
> to the client via ip address. Also when I do an ns lookup on the
> server it comes back with server01.phoenix.com, also on the
> workstation has the same nslookup response
>
> Server 172.16.0.2 /24
> Workstation 172.16.0.5 /24
> Server name Server
> Domain=Phoenix.com
>
> Not sure if what other infor you will need.
>
> ************************************************** *************
> Note: This information is intended for a network administrator. If
> you are not your network's administrator, notify the administrator
> that you received this information, which has been recorded in the
> file D:\WINDOWS\debug\dcdiag.txt.
>
> DNS was successfully queried for the service location (SRV) resource
> record used to locate a domain controller for domain Phoenix.com:
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
>
> The following domain controllers were identified by the query:
>
> server01.phoenix.com
>
> Common causes of this error include:
>
> - Host (A) records that map the name of the domain controller to its
> IP addresses are missing or contain incorrect addresses.
>
> - Domain controllers registered in DNS are not connected to the
> network or are not running.
>
> For information about correcting this problem, click Help.
>
> ***********************************************
>
>

other than checking the possible cuases listed in the error can you ping
server01.pheonix.com and get replies? Is the DNS configured correctly?
does this happen with just on machine or is this global to every machine?
nslookup?

this might be worth a read:

http://support.microsoft.com/default...b;en-us;314861

--
Neil MCNGP #30
"Human beings, who are almost unique in having the ability to
learn from the experience of others, are also remarkable for
their apparent disinclination to do so."
-- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)

Finding a domain controller is a 2 step job:
first, the client ask the DNS server for the name of DC.
This is the query for _ldap._tcp.dc._msdcs.Phoenix.com which is successfull
and return server01.phoenix.com
Second, you have to resolve the IP address for the just found DC.
This does not work.
Can you ping server01.phoenix.com from your client?


"John West" <> wrote in message
news:n35sd.174868$cJ3.155850@fed1read06...
> DNS was successfully queried for the service location (SRV) resource
> record used to locate a domain controller for domain Phoenix.com:
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
>
> The following domain controllers were identified by the query:
>
> server01.phoenix.com
>
> Common causes of this error include:
>
> - Host (A) records that map the name of the domain controller to its IP
> addresses are missing or contain incorrect addresses.
>
> - Domain controllers registered in DNS are not connected to the network or
> are not running.

Did you try running DCdiag /fix...on the server?

What is your server DNS configuration? As requested in another message, is
the client the only one with the problem or is this more general, wide
spread? Are you running DHCP, AD-integrated DNS, have your run Scavenge?
checked for duplicate IP addresses?



"John West" <> wrote in message
news:n35sd.174868$cJ3.155850@fed1read06...
> Gang,
>
> I have been working on trying to connect an XP workstation to a win 2003
> server and seem to be having some DNS issues. The error message below is
> from the XP workstation when I try to configure the client XP workstation
> to the domain phoenix.com.
>
> All computers have the latest and greatest patches and I can ping via name
> and ip address to the server from the client and from the server to the
> client via ip address. Also when I do an ns lookup on the server it comes
> back with server01.phoenix.com, also on the workstation has the same
> nslookup response
>
> Server 172.16.0.2 /24
> Workstation 172.16.0.5 /24
> Server name Server
> Domain=Phoenix.com
>
> Not sure if what other infor you will need.
>
> ************************************************** *************
> Note: This information is intended for a network administrator. If you
> are not your network's administrator, notify the administrator that you
> received this information, which has been recorded in the file
> D:\WINDOWS\debug\dcdiag.txt.
>
> DNS was successfully queried for the service location (SRV) resource
> record used to locate a domain controller for domain Phoenix.com:
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
>
> The following domain controllers were identified by the query:
>
> server01.phoenix.com
>
> Common causes of this error include:
>
> - Host (A) records that map the name of the domain controller to its IP
> addresses are missing or contain incorrect addresses.
>
> - Domain controllers registered in DNS are not connected to the network or
> are not running.
>
> For information about correcting this problem, click Help.
>
> ***********************************************
>

Thanks for the reply I can ping the sever but when I do an nslookup I
receive the messsage default server unknown and server 172.16.0.2 non
existent domain.

I can ping in both directions so I know the IP portion of this is good...

Ant thoughts ?

Thanks!
John


"Corrado Labinaz" <> wrote in message
news:...
> Finding a domain controller is a 2 step job:
> first, the client ask the DNS server for the name of DC.
> This is the query for _ldap._tcp.dc._msdcs.Phoenix.com which is
> successfull and return server01.phoenix.com
> Second, you have to resolve the IP address for the just found DC.
> This does not work.
> Can you ping server01.phoenix.com from your client?
>
>
> "John West" <> wrote in message
> news:n35sd.174868$cJ3.155850@fed1read06...
>> DNS was successfully queried for the service location (SRV) resource
>> record used to locate a domain controller for domain Phoenix.com:
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
>>
>> The following domain controllers were identified by the query:
>>
>> server01.phoenix.com
>>
>> Common causes of this error include:
>>
>> - Host (A) records that map the name of the domain controller to its IP
>> addresses are missing or contain incorrect addresses.
>>
>> - Domain controllers registered in DNS are not connected to the network
>> or are not running.
>
>

I ran the test earlier and the only issue that failed was a test concerning
DHCP not being able to find AD, really nothing as I am not using DHCP on
this box. I guess i should disable the service :> But then again if DHCP
cant find AD I wonder if DNS has the same issue? This box is runing an
evualation copy not a full vesion but that should not make a difference.

As for clients, all of them seem to have the same issue. As for the DHCP,
AD-integrated DNS, yes this is what I am running. As for the Scavenge check
I only have two current computers on this network to resolve this issue, at
one point I had many but reduced to two computers now no possible way I
could have dup IP addresses.

What other logs or tests can I run for you guys?

A phone call on this would be great and anyone who can fix this gets a quick
50 via paypall or check from me. I have been working on this issue for the
past 6 weeks off and on what a drag, but I am learning a lot!


Any thoughts?

Thanks

John


"beoweolf" <> wrote in message
news:2CGsd.54774$ om...
> Did you try running DCdiag /fix...on the server?
>
> What is your server DNS configuration? As requested in another message, is
> the client the only one with the problem or is this more general, wide
> spread? Are you running DHCP, AD-integrated DNS, have your run Scavenge?
> checked for duplicate IP addresses?
>
>
>
> "John West" <> wrote in message
> news:n35sd.174868$cJ3.155850@fed1read06...
>> Gang,
>>
>> I have been working on trying to connect an XP workstation to a win 2003
>> server and seem to be having some DNS issues. The error message below is
>> from the XP workstation when I try to configure the client XP workstation
>> to the domain phoenix.com.
>>
>> All computers have the latest and greatest patches and I can ping via
>> name and ip address to the server from the client and from the server to
>> the client via ip address. Also when I do an ns lookup on the server it
>> comes back with server01.phoenix.com, also on the workstation has the
>> same nslookup response
>>
>> Server 172.16.0.2 /24
>> Workstation 172.16.0.5 /24
>> Server name Server
>> Domain=Phoenix.com
>>
>> Not sure if what other infor you will need.
>>
>> ************************************************** *************
>> Note: This information is intended for a network administrator. If you
>> are not your network's administrator, notify the administrator that you
>> received this information, which has been recorded in the file
>> D:\WINDOWS\debug\dcdiag.txt.
>>
>> DNS was successfully queried for the service location (SRV) resource
>> record used to locate a domain controller for domain Phoenix.com:
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
>>
>> The following domain controllers were identified by the query:
>>
>> server01.phoenix.com
>>
>> Common causes of this error include:
>>
>> - Host (A) records that map the name of the domain controller to its IP
>> addresses are missing or contain incorrect addresses.
>>
>> - Domain controllers registered in DNS are not connected to the network
>> or are not running.
>>
>> For information about correcting this problem, click Help.
>>
>> ***********************************************
>>
>
>

Neil sorry I did not get back to you sooner! Yes I can ping
server01.phoenix.com to the client and from the client to the server so
network is working good. As for DNS being configured correclty everyting
looks right from my end that is why I just do not understand what is going
on with this issue.

Any thoughts?

Thanks

John
"Neil" <guess!!!@gmail.com> wrote in message
news:Xns95B5A309DE0C3neilmcsegmailcom@207.46.248.1 6...
> did you hear "John West" <> say in
> news:n35sd.174868$cJ3.155850@fed1read06:
>
>> Gang,
>>
>> I have been working on trying to connect an XP workstation to a win
>> 2003 server and seem to be having some DNS issues. The error message
>> below is from the XP workstation when I try to configure the client XP
>> workstation to the domain phoenix.com.
>>
>> All computers have the latest and greatest patches and I can ping via
>> name and ip address to the server from the client and from the server
>> to the client via ip address. Also when I do an ns lookup on the
>> server it comes back with server01.phoenix.com, also on the
>> workstation has the same nslookup response
>>
>> Server 172.16.0.2 /24
>> Workstation 172.16.0.5 /24
>> Server name Server
>> Domain=Phoenix.com
>>
>> Not sure if what other infor you will need.
>>
>> ************************************************** *************
>> Note: This information is intended for a network administrator. If
>> you are not your network's administrator, notify the administrator
>> that you received this information, which has been recorded in the
>> file D:\WINDOWS\debug\dcdiag.txt.
>>
>> DNS was successfully queried for the service location (SRV) resource
>> record used to locate a domain controller for domain Phoenix.com:
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.Phoenix.com
>>
>> The following domain controllers were identified by the query:
>>
>> server01.phoenix.com
>>
>> Common causes of this error include:
>>
>> - Host (A) records that map the name of the domain controller to its
>> IP addresses are missing or contain incorrect addresses.
>>
>> - Domain controllers registered in DNS are not connected to the
>> network or are not running.
>>
>> For information about correcting this problem, click Help.
>>
>> ***********************************************
>>
>>
>
> other than checking the possible cuases listed in the error can you ping
> server01.pheonix.com and get replies? Is the DNS configured correctly?
> does this happen with just on machine or is this global to every machine?
> nslookup?
>
> this might be worth a read:
>
> http://support.microsoft.com/default...b;en-us;314861
>
> --
> Neil MCNGP #30
> "Human beings, who are almost unique in having the ability to
> learn from the experience of others, are also remarkable for
> their apparent disinclination to do so."
> -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)

did you hear "John West" <> say in
news:vSQsd.175754$cJ3.5266@fed1read06:

> Neil sorry I did not get back to you sooner! Yes I can ping
> server01.phoenix.com to the client and from the client to the server
> so network is working good. As for DNS being configured correclty
> everyting looks right from my end that is why I just do not understand
> what is going on with this issue.
>
> Any thoughts?
>
> Thanks
>
> John


since it's 2k3 drop down to a command prompt and run the dnslint command

dnslint /ad /s /v server01.pheonix.com

this might give you a better idea as to what's happening.

More than that, well it looks fine from here

--
Neil MCNGP #30
"Human beings, who are almost unique in having the ability to
learn from the experience of others, are also remarkable for
their apparent disinclination to do so."
-- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)

did you hear Neil <guess!!!@gmail.com> say in
news:Xns95B76A162E789neilmcsegmailcom@207.46.248.1 6:

> dnslint /ad /s /v server01.pheonix.com

feh, sorry, use the IP addy of server01 instead...

--
Neil MCNGP #30
"Human beings, who are almost unique in having the ability to
learn from the experience of others, are also remarkable for
their apparent disinclination to do so."
-- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)

This is from the client side of things I have also changed the ip addressing
fearing the ip zero subnet thing:> The nslookup thing really bugs me cant
figure out why nslookup cant resolve the name in dns?



************************************************** **************
D:\tools>nltest /dclisthoenix.com
Get list of DCs in domain 'phoenix.com' from '\\server01.phoenix.com'.
You don't have access to DsBind to phoenix.com (\\server01.phoenix.com)
(Trying
NetServerEnum).
I_NetGetDCList failed: Status = 6118 0x17e6 ERROR_NO_BROWSER_SERVERS_FOUND
************************************************** ***************
D:\tools>nltest /dcnamehoenix.com
NetGetDCName failed: Status = 2453 0x995 NERR_DCNotFound
************************************************** **************


D:\tools>nltest /dsgetdchoenix.com
DC: \\server01.phoenix.com
Address: \\172.16.1.8
Dom Guid: c8876d07-d748-47cc-9dde-9967cb103e46
Dom Name: phoenix.com
Forest Name: phoenix.com
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC
DNS_DOMAIN
DNS_FOREST CLOSE_SITE
The command completed successfully
************************************************** *************
D:\>nslookup
*** Can't find server name for address 172.16.1.8: Non-existent domain
************************************************** ***********








"Neil" <guess!!!@gmail.com> wrote in message
news:Xns95B76AF0EAFC6neilmcsegmailcom@207.46.248.1 6...
> did you hear Neil <guess!!!@gmail.com> say in
> news:Xns95B76A162E789neilmcsegmailcom@207.46.248.1 6:
>
>> dnslint /ad /s /v server01.pheonix.com
>
> feh, sorry, use the IP addy of server01 instead...
>
> --
> Neil MCNGP #30
> "Human beings, who are almost unique in having the ability to
> learn from the experience of others, are also remarkable for
> their apparent disinclination to do so."
> -- a quote by Doug Adams (Author of the Hitchhiker's Guide to the Galaxy)