Re: Does DCDiag require WINS?

"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:e59lRvL6GHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
Hi
use port query tool to check available ports
http://www.microsoft.com/downloads/details.aspx?FamilyID=89811747-C74B-4638-A2D5-AC828BDC6983&displaylang=en


Thanks, I didn't have that one.

Also NetCat and NMap may occasionally be useful.

NMap is focused more on "finding computers", and to
use netcat the admin may need to know a bit more about
the protocol but unlike using Telnet for command testing
a port path/service, NetCat can "do UDP".

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:uQFGbiL6GHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
No, but practically every Windows network requires
NetBIOS resolution and THAT requires WINS Server
(and every machine, including DCs a WINS client) IF
you have more than one subnet (which is pretty much
common with multiple domains.)


"cc0" <cc0@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8892A9A2-BE65-42B8-8CE0-FF93EEC05485@xxxxxxxxxxxxxxxx
I just added a Windows 2003 domain controller to each of our 5 remote
locations. When I run dcdiag from my domain on these new controllers all
of
the tests pass.

Good.

DCDiag might conceivable be using NetBIOS to FIND
all of the DCs but it really SHOULD do this through DNS.

We are also required to get a good dcdiag from our central
office domain.

Good policy.

The problem I'm running into is that on these new domain
controllers I am getting the error messages below. I've gone through
most of
the trouble shooting steps I've found on the web and everything looks OK
as
far as DNS and replication goes. We do not have WINS running in our
domain
but our central office does. MOM 2005 also shows no problems. When I
added
one of our new domain controllers to their WINS server the dcdiags from
their
domain to ours started passing.

This strongly implies that DCDiag is somehow using NetBIOS
to find or connect to the machine to RUN the DCDiag (not the
actual tests.) But this still doesn't sound right.

AND I want to know if it turns out to be the case -- I collect
NetBIOS requirements <Grin> for Windows networks.

So here are my questions. Does dcdiag require WINS to properly run these
tests from a higher up domain? Should we even be worried about running
dcdiag
from a higher level domain? Am I missing something?

Is your parent zone (at "higher up") delegate to your child
zone (or have some other way to resolve its DNS) as it
should?

If the parent isn't delegating then it would not be able to
find the child DCs by DNS and when you add WINS
registration this might be how DNS resolution fails over
to the NetBIOS and then seems to work because of WINS
(when really DNS is broken.)

With it working (registered in WINS) try the FULLY
QUALIFIED child DC name: DC1.child.domain.com.

If this fails when WINS works, I would bet that your
real problem is failure to delegate and resolve DNS
from parent to child (which is a MUCH worse thing
than just failing DCDiag from there.)

[Server1] An net use or LsaPolicy operation failed with error 53, The
network path was not found..

And you might have some firewall issues form Parent
net to child net....

If so these might be either DNS ports or those used by
DCs for LDAP, Kerberos, or other purposes.....

If so, those problems need to be correct anyway since
there is SOME (limited) replication between all domains
in a forest (Scheme, Config, and GC.)

BTW: Do you have GCs at all locations?

If not, adding that to the child "location" (a DC there)
may uncover further errors (due to firewalls or DNS)
if it fails to replicate which it must for things to be
correct.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

"cc0" <cc0@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8892A9A2-BE65-42B8-8CE0-FF93EEC05485@xxxxxxxxxxxxxxxx
I just added a Windows 2003 domain controller to each of our 5 remote
locations. When I run dcdiag from my domain on these new controllers all
of
the tests pass. We are also required to get a good dcdiag from our
central
office domain. The problem I'm running into is that on these new domain
controllers I am getting the error messages below. I've gone through
most of
the trouble shooting steps I've found on the web and everything looks OK
as
far as DNS and replication goes. We do not have WINS running in our
domain
but our central office does. MOM 2005 also shows no problems. When I
added
one of our new domain controllers to their WINS server the dcdiags from
their
domain to ours started passing.

So here are my questions. Does dcdiag require WINS to properly run these
tests from a higher up domain? Should we even be worried about running
dcdiag
from a higher level domain? Am I missing something?

[Server1] An net use or LsaPolicy operation failed with error 53, The
network path was not found..
......................... Server1 failed test NetLogons

Starting test: Advertising
Fatal Error:DsGetDcName (Server1) call failed, error 1722
The Locator could not find the server.
......................... Server1 failed test Advertising

Starting test: MachineAccount
Could not open pipe with [Server1]:failed with 53: The network path was
not
found.

Could not open Remote ipc to [Server1]:failed with 53: The network path
was
not found.
......................... Server1 failed test Services

[Server1] An net use or LsaPolicy operation failed with error 53, The
network path was not found..
......................... Server1 failed test frssysvol






.

Relevant Pages

  • Re: Domain Controller Stops Processing All Login Requests Randomly
    ... But you seem pretty competent and if you have checked all of the DCDiag ... They are both holding the same exact zone. ... DNS is not case sensitive and although NetBIOS ... > "waimea.coe.cudenver.edu" in the server field. ...
    (microsoft.public.windows.server.dns)
  • Re: Does DCDiag require WINS?
    ... NetBIOS resolution and THAT requires WINS Server ... DCDiag might conceivable be using NetBIOS to FIND ... all of the DCs but it really SHOULD do this through DNS. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Does DCDiag require WINS?
    ... NetBIOS resolution and THAT requires WINS Server ... DCDiag might conceivable be using NetBIOS to FIND ... all of the DCs but it really SHOULD do this through DNS. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cant access web on local network server
    ... Yes my Windows 2003 R2 Standard Server is a DC domain controller. ... How do I open DNS for the outside? ... What port should I give access to? ...
    (microsoft.public.windows.server.general)
  • Re: Active Directory could not resolve DNS host name
    ... If you don't have the tools installed, install them from your server install ... Run dcdiag, netdiag and repadmin in verbose mode. ... Active Directory could not resolve the following DNS host name of the ... domain controller to an IP address. ...
    (microsoft.public.windows.server.active_directory)