Re: Trust relationship between this workstation and the primary do

Tech-Archive recommends: Fix windows errors by optimizing your registry




"Server Guy" <ServerGuy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5EE604E2-11C7-47FF-841B-994F1DA62F4A@xxxxxxxxxxxxxxxx
Client computers (actually ALL internal computers) must use STRICTLY
the INTERNAL DNS servers which can resolve your DCs and other
internal services -- they cannot mix in the ISP or firewall/gateway DNS
on the NIC->IP Properties.

Herb, this had absoutly nothing to do with DNS as I thought from the
beginning. Everything was resolving both internally and externally.

Which we have been trying to tell you is INSUFFICIENT as a test of
DNS.

Were you to grasp that, prove your DNS working, we could move on
to something that has a lower chance of being the problem.

Of course, we have been giving you other ideas but mostly you avoid
doing the tests and answering the questions but keep posting difficult
to understand, vague, or unclear messages.

State your actual problem clearly -- that is your job if YOU want help.

Work the problem logically, we'll help you with that but you are the one
who must actually do it.

Perhaps
if you had read the information fully and not got caught up in picking at
terminology,

No, but if you cannot learn to state you problem accurately we don't know
for sure what you want OR what you are doing to fix it.

We could have solved it here. I would tell you what it was but
you wouldnt believe it anyway and still have me chasing DNS problems that
are
not there.

Look at ALL of YOUR posts -- you have had a lot of people offer you
help and you are still flailing around without a solution.

That should help you to realize you aren't stating you problem clearly,
following the testing strategy we give you, or working logically.

You admitted in your last post that you "don't have a clue" what the
problem is and yet you argue with those trying to help you.

Notice that you bother to complain that WE aren't solving your problem,
but you still don't state explicitly HOW you have proven that you DNS
or your DC is well.

Were you doing that you would post "IPConfig /all" and "DCDiag /c"
outputs or just simply state: "DCDiag /c completes with no FAIL or
WARN messages."

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


.



Relevant Pages

  • Re: Trust relationship between this workstation and the primary do
    ... the INTERNAL DNS servers which can resolve your DCs and other ... internal services -- they cannot mix in the ISP or firewall/gateway DNS ... blame others because you didnt have the right answers. ... Look at ALL of YOUR posts -- you have had a lot of people offer you ...
    (microsoft.public.windows.server.active_directory)
  • Re: Need Help from DNS Expert on Subdomain DNS Records
    ... When you use nslookup to resolve these names do you get the correct internal ... domain from within and outside our firewall. ... public IP to point to the same private IP, ... You need to verify that the all DNS servers assigned to a the DNS Client be ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot a DC, HOPELESS Case
    ... If the DC is not fully registered in DNS then it won't resolve ... the DCs NIC properties specify the correct DNS server. ... >>> error whenever I'm running DCpromo! ...
    (microsoft.public.win2000.active_directory)
  • Re: aol..
    ... These are all AOL's email server. ... DNS work fine. ... This newsgroup only focuses on SBS technical issues. ... If we unable to resolve this issue after steps above, ...
    (microsoft.public.windows.server.sbs)
  • Re: NS and domain A record affecting AD
    ... Clients are pointing to the local dc for both WINS and DNS, ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)