windows ultimate error joining w2003 server domain

[Hansel Ortiz -[BrEcHaWarr]]

hi, im trying to join into my domain a laptop with windows vista
ultimate
and i get this error.. my question is..

it is really the server that has DNS problems.. or is just the
annoying vista ultimate

what should i do...


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
C:\Windows\debug\dcdiag.txt.

DNS was successfully queried for the service location (SRV) resource
record used to locate an Active Directory Domain Controller for domain
propcdom.local:

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

The following AD DCs were identified by the query:

trujillo.propcdom.local

Common causes of this error include:

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

- Active Directory Domain Controllers registered in DNS are not
connected
to the network or are not running.

For information about correcting this problem, click Help.

 

[Rick V]

On the notebook do you have the DNS entries pointing to the Domain
Controller or an AD integrated DNS?


"Hansel Ortiz -[BrEcHaWarr]" <hansel.ortiz@gmail.com> wrote in message
news:79a10aaa-924f-4f45-84e2-981890b2fa87@l64g2000hse.googlegroups.com...
> hi, im trying to join into my domain a laptop with windows vista
> ultimate
> and i get this error.. my question is..
>
> it is really the server that has DNS problems.. or is just the
> annoying vista ultimate
>
> what should i do...
>
>
> 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
> C:\Windows\debug\dcdiag.txt.
>
> DNS was successfully queried for the service location (SRV) resource
> record used to locate an Active Directory Domain Controller for domain
> propcdom.local:
>
> The query was for the SRV record for
> _ldap._tcp.dc._msdcs.propcdom.local
>
> The following AD DCs were identified by the query:
>
> trujillo.propcdom.local
>
> Common causes of this error include:
>
> - Host (A) records that map the name of the AD DCs to its IP addresses
> are
> missing or contain incorrect addresses.
>
> - Active Directory Domain Controllers registered in DNS are not
> connected
> to the network or are not running.
>
> For information about correcting this problem, click Help.

 

[Hansel Ortiz -[BrEcHaWarr]]

On Jul 22, 4:16 pm, "Rick V" <r...@di-wave.com> wrote:
> On the notebook do you have the DNS entries pointing to the Domain
> Controller or an AD integrated DNS?
>
> "Hansel Ortiz -[BrEcHaWarr]" <hansel.or...@gmail.com> wrote in messagenews:79a10aaa-924f-4f45-84e2-981890b2fa87@l64g2000hse.googlegroups.com...
>
> > hi, im trying to join into my domain a laptop with windows vista
> > ultimate
> > and i get this error.. my question is..
>
> > it is really the server that has DNS problems.. or is just the
> > annoying  vista ultimate
>
> > what should i do...
>
> > 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
> > C:\Windows\debug\dcdiag.txt.
>
> > DNS was successfully queried for the service location (SRV) resource
> > record used to locate an Active Directory Domain Controller for domain
> > propcdom.local:
>
> > The query was for the SRV record for
> > _ldap._tcp.dc._msdcs.propcdom.local
>
> > The following AD DCs were identified by the query:
in the primary dns i have the server ip...

and others computers with xp can comunicate and join the domain
without problems..



>
> > trujillo.propcdom.local
>
> > Common causes of this error include:
>
> > - Host (A) records that map the name of the AD DCs to its IP addresses
> > are
> > missing or contain incorrect addresses.
>
> > - Active Directory Domain Controllers registered in DNS are not
> > connected
> > to the network or are not running.
>
> > For information about correcting this problem, click Help.