Archived from groups: microsoft.public.win2000.dns (
More info?)
Thanks for the response.
There is only our internal dns server listed in the
clients tcp/ip properties. Our dns server has already has
a forwarder listed. None of our dc's are multihomed.
Netdiag on the pdc emulator did show "error 9003
rcode_name_error" for a dns server that is not at our
site, but is one of our isp's servers. This dns server is
one of our forwarders, and it is also listed as a Name
Server under the forward lookup zone for our domain. I
don't know why my predecessor has it entered as a Name
Server for the domain.
Any advice?
>-----Original Message-----
>In news:309b01c47100$3708d180$a401280a@phx.gbl,
>Evan <anonymous@discussions.microsoft.com> asked for help
and I offered my
>suggestions below:
>> Hi all
>> I have a laptop that intermittently fails to map drives
>> for a user. KiXtart records event id 1789 in the
>> application log "The trust relationship between this
>> workstation and the primary domain failed".
>>
>> The system log shows:
>> event id 54 "The Windows Time Service was not able to
find
>> a Domain Controller".
>> event id 5719 "There are currently no logon servers
>> available to service the logon request".
>> event id 4319 "A duplicate name has been detected on the
>> TCP network"
>>
>> Of course the computer has been renamed and re-added to
>> the domain, but this problem returned.
>> Could this be a DNS issue?
>
>If you're getting a 'domain or something or other not
found' message, that's
>indicating a DNS lookup issue. Make sure you are only
using your internal
>DNS. Remove your ISP's addresses from IP properties. In
DNS properties,
>configure a forwarder for efficient Internet resolution.
This config will
>give AD what it needs and will resolve external names
efficiently as well.
>
>How to configure a forwarder?
>http://support.microsoft.com/?id=300202
>
>Duplicate names issues come up due to multihomed
machines. If at all
>possible, its not suggested to mutlihome a DC. If a
server, decide which NIC
>is the higher priority, and disable NetBIOS, MS Client
and F&P services on
>the other NIC. That will eliminate the dupe name error.
>
>--
>Regards,
>Ace
>
>Please direct all replies ONLY to the Microsoft public
newsgroups
>so all can benefit.
>
>This posting is provided "AS-IS" with no warranties or
guarantees
>and confers no rights.
>
>Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I,
MCT, MVP
>Microsoft Windows MVP - Windows Server - Directory
Services
>
>Security Is Like An Onion, It Has Layers
>HAM AND EGGS: A day's work for a chicken;
>A lifetime commitment for a pig.
>--
>=================================
>
>
>.
>