2k3 keep hanging?

Dell power edge 2950 DC “one domain” it runs DHCP, DNS, file server, AD….etc
all fine for couple of years...Now all in the sudden last week the server
hangs I have to reboot then couple of hours later it may or may not hang
again maybe a day or so runs fine then it hangs again….when this happens all
clients PC gets real slow they can’t get to their files “total downtime” also
while it’s hanging I still can ping it. I opened a ticket with Dell support
ran couple of missing sw and fw updates…rebooted I see an DNS log error 4016
the DNS has been set for couple of years also the server is pointed to it
self as well as all the clients are pointed to that server. The Dell tech
said the DNS is not any reason for the server to hang! I do have second DC
also set to global catalog and 2nd DNS server “not running AD” when this
server goes down the LAN is all slow isn’t that odd since there is a second
DC and DNS server? Any advice please?
I will create a separate file server because that server access the SAN
files and stuff for the users so if it’s down the files are down as well

Thanks

 

Hello 2K3

What type of error does the event log shows? Do you also have Exchange
running on this server? Everything slows down when this server goes offline
probably because the server also act as a file server having user
s profiles?
Look at the event logs and post errors,
Isaac


"2K3" <2K3@discussions.microsoft.com> wrote in message
news:C31DD836-8A90-4DA5-96DC-187A702D9263@microsoft.com...
> Dell power edge 2950 DC "one domain" it runs DHCP, DNS, file server,
> AD..etc
> all fine for couple of years...Now all in the sudden last week the server
> hangs I have to reboot then couple of hours later it may or may not hang
> again maybe a day or so runs fine then it hangs again..when this happens
> all
> clients PC gets real slow they can't get to their files "total downtime"
> also
> while it's hanging I still can ping it. I opened a ticket with Dell
> support
> ran couple of missing sw and fw updates.rebooted I see an DNS log error
> 4016
> the DNS has been set for couple of years also the server is pointed to it
> self as well as all the clients are pointed to that server. The Dell tech
> said the DNS is not any reason for the server to hang! I do have second DC
> also set to global catalog and 2nd DNS server "not running AD" when this
> server goes down the LAN is all slow isn't that odd since there is a
> second
> DC and DNS server? Any advice please?
> I will create a separate file server because that server access the SAN
> files and stuff for the users so if it's down the files are down as well
>
> Thanks
>
>
>

 

Just that DNS one i posted! exchange is separate box no idea why does it
hang??? so far over the weekend no issues



"Isaac Oben [MCITP:EA, MCSE]" wrote:

> Hello 2K3
>
> What type of error does the event log shows? Do you also have Exchange
> running on this server? Everything slows down when this server goes offline
> probably because the server also act as a file server having user
> s profiles?
> Look at the event logs and post errors,
> Isaac
>
>
> "2K3" <2K3@discussions.microsoft.com> wrote in message
> news:C31DD836-8A90-4DA5-96DC-187A702D9263@microsoft.com...
> > Dell power edge 2950 DC "one domain" it runs DHCP, DNS, file server,
> > AD..etc
> > all fine for couple of years...Now all in the sudden last week the server
> > hangs I have to reboot then couple of hours later it may or may not hang
> > again maybe a day or so runs fine then it hangs again..when this happens
> > all
> > clients PC gets real slow they can't get to their files "total downtime"
> > also
> > while it's hanging I still can ping it. I opened a ticket with Dell
> > support
> > ran couple of missing sw and fw updates.rebooted I see an DNS log error
> > 4016
> > the DNS has been set for couple of years also the server is pointed to it
> > self as well as all the clients are pointed to that server. The Dell tech
> > said the DNS is not any reason for the server to hang! I do have second DC
> > also set to global catalog and 2nd DNS server "not running AD" when this
> > server goes down the LAN is all slow isn't that odd since there is a
> > second
> > DC and DNS server? Any advice please?
> > I will create a separate file server because that server access the SAN
> > files and stuff for the users so if it's down the files are down as well
> >
> > Thanks
> >
> >
> >
>
>
>

 

Any errors in events log?

"2K3" <2K3@discussions.microsoft.com> wrote in message
news:B9BE2BB6-FD82-4975-994B-2FA5A5358E6E@microsoft.com...
> Just that DNS one i posted! exchange is separate box no idea why does it
> hang??? so far over the weekend no issues
>
>
>
> "Isaac Oben [MCITP:EA, MCSE]" wrote:
>
>> Hello 2K3
>>
>> What type of error does the event log shows? Do you also have Exchange
>> running on this server? Everything slows down when this server goes
>> offline
>> probably because the server also act as a file server having user
>> s profiles?
>> Look at the event logs and post errors,
>> Isaac
>>
>>
>> "2K3" <2K3@discussions.microsoft.com> wrote in message
>> news:C31DD836-8A90-4DA5-96DC-187A702D9263@microsoft.com...
>> > Dell power edge 2950 DC "one domain" it runs DHCP, DNS, file server,
>> > AD..etc
>> > all fine for couple of years...Now all in the sudden last week the
>> > server
>> > hangs I have to reboot then couple of hours later it may or may not
>> > hang
>> > again maybe a day or so runs fine then it hangs again..when this
>> > happens
>> > all
>> > clients PC gets real slow they can't get to their files "total
>> > downtime"
>> > also
>> > while it's hanging I still can ping it. I opened a ticket with Dell
>> > support
>> > ran couple of missing sw and fw updates.rebooted I see an DNS log error
>> > 4016
>> > the DNS has been set for couple of years also the server is pointed to
>> > it
>> > self as well as all the clients are pointed to that server. The Dell
>> > tech
>> > said the DNS is not any reason for the server to hang! I do have second
>> > DC
>> > also set to global catalog and 2nd DNS server "not running AD" when
>> > this
>> > server goes down the LAN is all slow isn't that odd since there is a
>> > second
>> > DC and DNS server? Any advice please?
>> > I will create a separate file server because that server access the SAN
>> > files and stuff for the users so if it's down the files are down as
>> > well
>> >
>> > Thanks
>> >
>> >
>> >
>>
>>
>>

 

Hello 2K3,

I agree with Isaac, check the event viewer for errors and post them complete
here.

Additional run dcdiag /v, netdiag /v and post the ouput here.

Event ID 4016:
http://technet.microsoft.com/en-us/library/cc755402.aspx

Are your forward/reverse lookup zones existing and all machines have there
record listed?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Dell power edge 2950 DC "one domain" it runs DHCP, DNS, file server,
> AD..etc
> all fine for couple of years...Now all in the sudden last week the
> server
> hangs I have to reboot then couple of hours later it may or may not
> hang
> again maybe a day or so runs fine then it hangs again..when this
> happens all
> clients PC gets real slow they can't get to their files "total
> downtime" also
> while it's hanging I still can ping it. I opened a ticket with Dell
> support
> ran couple of missing sw and fw updates.rebooted I see an DNS log
> error 4016
> the DNS has been set for couple of years also the server is pointed to
> it
> self as well as all the clients are pointed to that server. The Dell
> tech
> said the DNS is not any reason for the server to hang! I do have
> second DC
> also set to global catalog and 2nd DNS server "not running AD" when
> this
> server goes down the LAN is all slow isn't that odd since there is a
> second
> DC and DNS server? Any advice please?
> I will create a separate file server because that server access the
> SAN
> files and stuff for the users so if it's down the files are down as
> well
> Thanks
>

 

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.ALLIESINC>dcdiag /v

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine DC1, is a DC.
* Connecting to directory service on server DC1.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DC1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DC1
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=DomainDnsZones,DC=AlliesInc,DC=local
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only
replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0
had no
latency information (Win2K DC).
DC=ForestDnsZones,DC=AlliesInc,DC=local
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only
replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0
had no
latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=AlliesInc,DC=local
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only
replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0
had no
latency information (Win2K DC).
CN=Configuration,DC=AlliesInc,DC=local
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only
replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0
had no
latency information (Win2K DC).
DC=AlliesInc,DC=local
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only
replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0
had no
latency information (Win2K DC).
......................... DC1 passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC DC1.
* Security Permissions Check for
DC=DomainDnsZones,DC=AlliesInc,DC=local
(NDNC,Version 2)
* Security Permissions Check for
DC=ForestDnsZones,DC=AlliesInc,DC=local
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=AlliesInc,DC=local
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=AlliesInc,DC=local
(Configuration,Version 2)
* Security Permissions Check for
DC=AlliesInc,DC=local
(Domain,Version 2)
......................... DC1 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\DC1\netlogon
Verified share \\DC1\sysvol
......................... DC1 passed test NetLogons
Starting test: Advertising
The DC DC1 is advertising itself as a DC and having a DS.
The DC DC1 is advertising as an LDAP server
The DC DC1 is advertising as having a writeable directory
The DC DC1 is advertising as a Key Distribution Center
The DC DC1 is advertising as a time server
The DS DC1 is advertising as a GC.
......................... DC1 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=DC1,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
Role Domain Owner = CN=NTDS
Settings,CN=DC1,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
Role PDC Owner = CN=NTDS
Settings,CN=DC1,CN=Servers,CN=Default-First-Si
te-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=DC1,CN=Servers,CN=Default-First-Si
te-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=DC1,CN=Servers,C
N=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
......................... DC1 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 6104 to 1073741823
* DC1.AlliesInc.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 4604 to 5103
* rIDPreviousAllocationPool is 4104 to 4603
* rIDNextRID: 4468
......................... DC1 passed test RidManager
Starting test: MachineAccount
Checking machine account for DC DC1 on DC DC1.
* SPN found :LDAP/DC1.AlliesInc.local/AlliesInc.local
* SPN found :LDAP/DC1.AlliesInc.local
* SPN found :LDAP/DC1
* SPN found :LDAP/DC1.AlliesInc.local/ALLIESINC
* SPN found
:LDAP/ec7ee927-b372-4172-bbea-2b3af599c99b._msdcs.AlliesInc
..local
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/ec7ee927-b372-4172-bb
ea-2b3af599c99b/AlliesInc.local
* SPN found :HOST/DC1.AlliesInc.local/AlliesInc.local
* SPN found :HOST/DC1.AlliesInc.local
* SPN found :HOST/DC1
* SPN found :HOST/DC1.AlliesInc.local/ALLIESINC
* SPN found :GC/DC1.AlliesInc.local/AlliesInc.local
......................... DC1 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DC1 passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
DC1 is in domain DC=AlliesInc,DC=local
Checking for CN=DC1,OU=Domain Controllers,DC=AlliesInc,DC=local in
doma
in DC=AlliesInc,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=DC1,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local in domain
CN=Configuration,D
C=AlliesInc,DC=local on 1 servers
Object is up-to-date on all servers.
......................... DC1 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DC1 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... DC1 passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minut
es.
......................... DC1 passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... DC1 passed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=DC1,OU=Domain Controllers,DC=AlliesInc,DC=local and backlink on

CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=AlliesInc,DC=local
are correct.
The system object reference (frsComputerReferenceBL)
CN=DC1,CN=Domain System Volume (SYSVOL share),CN=File Replication
Servi
ce,CN=System,DC=AlliesInc,DC=local
and backlink on CN=DC1,OU=Domain Controllers,DC=AlliesInc,DC=local
are
correct.
The system object reference (serverReferenceBL)
CN=DC1,CN=Domain System Volume (SYSVOL share),CN=File Replication
Servi
ce,CN=System,DC=AlliesInc,DC=local
and backlink on
CN=NTDS
Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,
CN=Configuration,DC=AlliesInc,DC=local
are correct.
......................... DC1 passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : AlliesInc
Starting test: CrossRefValidation
......................... AlliesInc passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... AlliesInc passed test CheckSDRefDom

Running enterprise tests on : AlliesInc.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... AlliesInc.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\DC1.AlliesInc.local
Locator Flags: 0xe00003fd
PDC Name: \\DC1.AlliesInc.local
Locator Flags: 0xe00003fd
Time Server Name: \\DC1.AlliesInc.local
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\DC1.AlliesInc.local
Locator Flags: 0xe00003fd
KDC Name: \\DC1.AlliesInc.local
Locator Flags: 0xe00003fd
......................... AlliesInc.local passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS






Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.ALLIESINC>netdiag /v

Querying status of the Netcard drivers... Passed
Testing IpConfig - pinging the Primary WINS server... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Local Area Network
Sending name query to primary WINS server 10.0.0.6 - Passed
There is no secondary WINS server defined for this adapter.
iSCSI
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
PASS - All the DNS entries for DC are registered on DNS server
'10.0.0.6' an
d other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.0.0.17' a
nd other DCs also have some of the names registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Looking for a PDC emulator
Looking for an Active Directory DC
Gathering the list of Domain Controllers for domain 'ALLIESINC'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain ALLIESINC ...
Gathering routing information
Gathering network statistics information.

 

Hello 2K3,

The dcdiag states about a second DC, is that correct? Please post also the
dcdiag of that one. And run repadmin /showrepl to check replication status.

Your netdiag is not complete, choose "netdiag /v >c:\netdiag.log" and you
have the complete output in the file where you can copy it from.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
> C:\Documents and Settings\Administrator.ALLIESINC>dcdiag /v
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> * Verifying that the local machine DC1, is a DC.
> * Connecting to directory service on server DC1.
> * Collecting site info.
> * Identifying all servers.
> * Identifying all NC cross-refs.
> * Found 2 DC(s). Testing 1 of them.
> Done gathering initial info.
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\DC1
> Starting test: Connectivity
> * Active Directory LDAP Services Check
> * Active Directory RPC Services Check
> ......................... DC1 passed test Connectivity
> Doing primary tests
>
> Testing server: Default-First-Site-Name\DC1
> Starting test: Replications
> * Replications Check
> * Replication Latency Check
> DC=DomainDnsZones,DC=AlliesInc,DC=local
> Latency information for 1 entries in the vector were
> ignored.
> 1 were retired Invocations. 0 were either:
> read-only
> replicas
> and are not verifiably latent, or dc's no longer replicating this nc.
> 0
> had no
> latency information (Win2K DC).
> DC=ForestDnsZones,DC=AlliesInc,DC=local
> Latency information for 1 entries in the vector were
> ignored.
> 1 were retired Invocations. 0 were either:
> read-only
> replicas
> and are not verifiably latent, or dc's no longer replicating this nc.
> 0
> had no
> latency information (Win2K DC).
> CN=Schema,CN=Configuration,DC=AlliesInc,DC=local
> Latency information for 4 entries in the vector were
> ignored.
> 4 were retired Invocations. 0 were either:
> read-only
> replicas
> and are not verifiably latent, or dc's no longer replicating this nc.
> 0
> had no
> latency information (Win2K DC).
> CN=Configuration,DC=AlliesInc,DC=local
> Latency information for 4 entries in the vector were
> ignored.
> 4 were retired Invocations. 0 were either:
> read-only
> replicas
> and are not verifiably latent, or dc's no longer replicating this nc.
> 0
> had no
> latency information (Win2K DC).
> DC=AlliesInc,DC=local
> Latency information for 4 entries in the vector were
> ignored.
> 4 were retired Invocations. 0 were either:
> read-only
> replicas
> and are not verifiably latent, or dc's no longer replicating this nc.
> 0
> had no
> latency information (Win2K DC).
> ......................... DC1 passed test Replications
> Test omitted by user request: Topology
> Test omitted by user request: CutoffServers
> Starting test: NCSecDesc
> * Security Permissions check for all NC's on DC DC1.
> * Security Permissions Check for
> DC=DomainDnsZones,DC=AlliesInc,DC=local
> (NDNC,Version 2)
> * Security Permissions Check for
> DC=ForestDnsZones,DC=AlliesInc,DC=local
> (NDNC,Version 2)
> * Security Permissions Check for
> CN=Schema,CN=Configuration,DC=AlliesInc,DC=local
> (Schema,Version 2)
> * Security Permissions Check for
> CN=Configuration,DC=AlliesInc,DC=local
> (Configuration,Version 2)
> * Security Permissions Check for
> DC=AlliesInc,DC=local
> (Domain,Version 2)
> ......................... DC1 passed test NCSecDesc
> Starting test: NetLogons
> * Network Logons Privileges Check
> Verified share \\DC1\netlogon
> Verified share \\DC1\sysvol
> ......................... DC1 passed test NetLogons
> Starting test: Advertising
> The DC DC1 is advertising itself as a DC and having a DS.
> The DC DC1 is advertising as an LDAP server
> The DC DC1 is advertising as having a writeable directory
> The DC DC1 is advertising as a Key Distribution Center
> The DC DC1 is advertising as a time server
> The DS DC1 is advertising as a GC.
> ......................... DC1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> Role Schema Owner = CN=NTDS
> Settings,CN=DC1,CN=Servers,CN=Default-First
> -Site-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
> Role Domain Owner = CN=NTDS
> Settings,CN=DC1,CN=Servers,CN=Default-First
> -Site-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
> Role PDC Owner = CN=NTDS
> Settings,CN=DC1,CN=Servers,CN=Default-First-Si
> te-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
> Role Rid Owner = CN=NTDS
> Settings,CN=DC1,CN=Servers,CN=Default-First-Si
> te-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local
> Role Infrastructure Update Owner = CN=NTDS
> Settings,CN=DC1,CN=Servers,C
> N=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=AlliesInc,DC=lo
> cal
> ......................... DC1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> * Available RID Pool for the Domain is 6104 to 1073741823
> * DC1.AlliesInc.local is the RID Master
> * DsBind with RID Master was successful
> * rIDAllocationPool is 4604 to 5103
> * rIDPreviousAllocationPool is 4104 to 4603
> * rIDNextRID: 4468
> ......................... DC1 passed test RidManager
> Starting test: MachineAccount
> Checking machine account for DC DC1 on DC DC1.
> * SPN found :LDAP/DC1.AlliesInc.local/AlliesInc.local
> * SPN found :LDAP/DC1.AlliesInc.local
> * SPN found :LDAP/DC1
> * SPN found :LDAP/DC1.AlliesInc.local/ALLIESINC
> * SPN found
> :LDAP/ec7ee927-b372-4172-bbea-2b3af599c99b._msdcs.AlliesInc
> .local
> * SPN found
> :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ec7ee927-b372-4172-bb
> ea-2b3af599c99b/AlliesInc.local
> * SPN found :HOST/DC1.AlliesInc.local/AlliesInc.local
> * SPN found :HOST/DC1.AlliesInc.local
> * SPN found :HOST/DC1
> * SPN found :HOST/DC1.AlliesInc.local/ALLIESINC
> * SPN found :GC/DC1.AlliesInc.local/AlliesInc.local
> ......................... DC1 passed test MachineAccount
> Starting test: Services
> * Checking Service: Dnscache
> * Checking Service: NtFrs
> * Checking Service: IsmServ
> * Checking Service: kdc
> * Checking Service: SamSs
> * Checking Service: LanmanServer
> * Checking Service: LanmanWorkstation
> * Checking Service: RpcSs
> * Checking Service: w32time
> * Checking Service: NETLOGON
> ......................... DC1 passed test Services
> Test omitted by user request: OutboundSecureChannels
> Starting test: ObjectsReplicated
> DC1 is in domain DC=AlliesInc,DC=local
> Checking for CN=DC1,OU=Domain
> Controllers,DC=AlliesInc,DC=local in
> doma
> in DC=AlliesInc,DC=local on 1 servers
> Object is up-to-date on all servers.
> Checking for CN=NTDS
> Settings,CN=DC1,CN=Servers,CN=Default-First-Site-N
> ame,CN=Sites,CN=Configuration,DC=AlliesInc,DC=local in domain
> CN=Configuration,D
> C=AlliesInc,DC=local on 1 servers
> Object is up-to-date on all servers.
> ......................... DC1 passed test ObjectsReplicated
> Starting test: frssysvol
> * The File Replication Service SYSVOL ready test
> File Replication Service's SYSVOL is ready
> ......................... DC1 passed test frssysvol
> Starting test: frsevent
> * The File Replication Service Event log test
> ......................... DC1 passed test frsevent
> Starting test: kccevent
> * The KCC Event log test
> Found no KCC errors in Directory Service Event log in the
> last 15
> minut
> es.
> ......................... DC1 passed test kccevent
> Starting test: systemlog
> * The System Event log test
> Found no errors in System Event log in the last 60 minutes.
> ......................... DC1 passed test systemlog
> Test omitted by user request: VerifyReplicas
> Starting test: VerifyReferences
> The system object reference (serverReference)
> CN=DC1,OU=Domain Controllers,DC=AlliesInc,DC=local and
> backlink on
> CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration
> ,
> DC=AlliesInc,DC=local
> are correct.
> The system object reference (frsComputerReferenceBL)
> CN=DC1,CN=Domain System Volume (SYSVOL share),CN=File
> Replication
> Servi
> ce,CN=System,DC=AlliesInc,DC=local
> and backlink on CN=DC1,OU=Domain
> Controllers,DC=AlliesInc,DC=local
> are
> correct.
> The system object reference (serverReferenceBL)
> CN=DC1,CN=Domain System Volume (SYSVOL share),CN=File
> Replication
> Servi
> ce,CN=System,DC=AlliesInc,DC=local
> and backlink on
> CN=NTDS
> Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,
> CN=Configuration,DC=AlliesInc,DC=local
> are correct.
> ......................... DC1 passed test VerifyReferences
> Test omitted by user request: VerifyEnterpriseReferences
> Test omitted by user request: CheckSecurityError
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> ......................... DomainDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... DomainDnsZones passed test
> CheckSDRefDom
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> ......................... ForestDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... ForestDnsZones passed test
> CheckSDRefDom
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> ......................... Schema passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Schema passed test CheckSDRefDom
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> ......................... Configuration passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Configuration passed test
> CheckSDRefDom
> Running partition tests on : AlliesInc
> Starting test: CrossRefValidation
> ......................... AlliesInc passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... AlliesInc passed test CheckSDRefDom
> Running enterprise tests on : AlliesInc.local
> Starting test: Intersite
> Skipping site Default-First-Site-Name, this site is outside
> the scope
> provided by the command line arguments provided.
> ......................... AlliesInc.local passed test
> Intersite
> Starting test: FsmoCheck
> GC Name: \\DC1.AlliesInc.local
> Locator Flags: 0xe00003fd
> PDC Name: \\DC1.AlliesInc.local
> Locator Flags: 0xe00003fd
> Time Server Name: \\DC1.AlliesInc.local
> Locator Flags: 0xe00003fd
> Preferred Time Server Name: \\DC1.AlliesInc.local
> Locator Flags: 0xe00003fd
> KDC Name: \\DC1.AlliesInc.local
> Locator Flags: 0xe00003fd
> ......................... AlliesInc.local passed test
> FsmoCheck
> Test omitted by user request: DNS
> Test omitted by user request: DNS
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
> C:\Documents and Settings\Administrator.ALLIESINC>netdiag /v
>
> Querying status of the Netcard drivers... Passed
> Testing IpConfig - pinging the Primary WINS server... Passed
> Testing Domain membership... Passed
> Gathering NetBT configuration information.
> Testing for autoconfiguration... Passed
> Testing IP loopback ping... Passed
> Testing default gateways... Passed
> Enumerating local and remote NetBT name cache... Passed
> Testing the WINS server
> Local Area Network
> Sending name query to primary WINS server 10.0.0.6 -
> Passed
> There is no secondary WINS server defined for this
> adapter.
> iSCSI
> There is no primary WINS server defined for this adapter.
> There is no secondary WINS server defined for this
> adapter.
> Gathering Winsock information.
> Testing DNS
> PASS - All the DNS entries for DC are registered on DNS server
> '10.0.0.6' an
> d other DCs also have some of the names registered.
> PASS - All the DNS entries for DC are registered on DNS server
> '10.0.0.17' a
> nd other DCs also have some of the names registered.
> Testing redirector and browser... Passed
> Testing DC discovery.
> Looking for a DC
> Looking for a PDC emulator
> Looking for an Active Directory DC
> Gathering the list of Domain Controllers for domain 'ALLIESINC'
> Testing trust relationships... Skipped
> Testing Kerberos authentication... Passed
> Testing LDAP servers in Domain ALLIESINC ...
> Gathering routing information
> Gathering network statistics information.

 

Here is the complet netdiag from first DC


Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Internet Protocol (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t)

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t) #2

Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t)

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t) #2

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : WebClient
Bind Name: WebClient
Binding Paths:

Component Name : DHCP Server
Bind Name: DHCPServer
Binding Paths:

Component Name : Wireless Configuration
Bind Name: wzcsvc
Binding Paths:

Component Name : Network Load Balancing
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Network Load Balancing
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Load Balancing
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t)

Owner of the binding path : Network Load Balancing
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Load Balancing
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t) #2


Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:

Component Name : Dial-Up Server
Bind Name: msrassrv
Binding Paths:

Component Name : Remote Access Connection Manager
Bind Name: RasMan
Binding Paths:

Component Name : Dial-Up Client
Bind Name: msrascli
Binding Paths:

Component Name : File and Printer Sharing for Microsoft Networks
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t)

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t) #2

Owner of the binding path : File and Printer Sharing for Microsoft
Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : Generic Packet Classifier
Bind Name: Gpc
Binding Paths:

Component Name : Application Layer Gateway
Bind Name: ALG
Binding Paths:

Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t)

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
Clien
t) #2

Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)


Component Name : WAN Miniport (Network Monitor)
Bind Name: NdisWanBh
Binding Paths:

Component Name : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Direct Parallel
Bind Name: {DADD58E2-2363-4474-BB08-4694EF91A9B3}
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {C0D04B45-0A09-43C7-83EC-0B01C0FBF0CE}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {383CB9EF-15FA-4460-BBE7-A4E973147647}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {454E35A4-7FA5-41C7-9E62-FD267A2986D1}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {FE6C6C33-566E-46C3-AC6B-A5F31191BAA4}
Binding Paths:

Component Name : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2
Bind Name: {BE0F591A-8E5F-4264-A5BA-E9E86F44E429}
Binding Paths:

Component Name : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
Bind Name: {229E383C-2FB2-4AC3-9697-1E4B9363C1FB}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully


For the second DC when i run the either or commands I get the below
C:\Documents and Settings\Administrator.ALLIESINC>netdiag /v
'netdiag' is not recognized as an internal or external command,
operable program or batch file.

 

Hello 2K3,

Sorry but again it is not complete, please choose the command from before
and copy the content of the textfile.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Here is the complet netdiag from first DC
>
> Owner of the binding path : WINS Client(TCP/IP) Protocol
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndiswanip
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: WAN Miniport (IP)
> Component Name : Internet Protocol (TCP/IP)
> Bind Name: Tcpip
> Binding Paths:
> Owner of the binding path : Internet Protocol (TCP/IP)
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t)
>
> Owner of the binding path : Internet Protocol (TCP/IP)
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t) #2
>
> Owner of the binding path : Internet Protocol (TCP/IP)
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: ndiswanip
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: WAN Miniport (IP)
> Component Name : Client for Microsoft Networks
> Bind Name: LanmanWorkstation
> Binding Paths:
> Owner of the binding path : Client for Microsoft Networks
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios_smb
> Upper Component: Client for Microsoft Networks
> Lower Component: Message-oriented TCP/IP Protocol (SMB
> session)
> Owner of the binding path : Client for Microsoft Networks
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: Client for Microsoft Networks
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t)
>
> Owner of the binding path : Client for Microsoft Networks
> Binding Enabled: No
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: Client for Microsoft Networks
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t) #2
>
> Owner of the binding path : Client for Microsoft Networks
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: Client for Microsoft Networks
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndiswanip
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: WAN Miniport (IP)
> Component Name : WebClient
> Bind Name: WebClient
> Binding Paths:
> Component Name : DHCP Server
> Bind Name: DHCPServer
> Binding Paths:
> Component Name : Wireless Configuration
> Bind Name: wzcsvc
> Binding Paths:
> Component Name : Network Load Balancing
> Bind Name: Wlbs
> Binding Paths:
> Owner of the binding path : Network Load Balancing
> Binding Enabled: No
> Interfaces of the binding path:
> -Interface Name: ndis5
> Upper Component: Network Load Balancing
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t)
>
> Owner of the binding path : Network Load Balancing
> Binding Enabled: No
> Interfaces of the binding path:
> -Interface Name: ndis5
> Upper Component: Network Load Balancing
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t) #2
>
> Component Name : Steelhead
> Bind Name: RemoteAccess
> Binding Paths:
> Component Name : Dial-Up Server
> Bind Name: msrassrv
> Binding Paths:
> Component Name : Remote Access Connection Manager
> Bind Name: RasMan
> Binding Paths:
> Component Name : Dial-Up Client
> Bind Name: msrascli
> Binding Paths:
> Component Name : File and Printer Sharing for Microsoft Networks
> Bind Name: LanmanServer
> Binding Paths:
> Owner of the binding path : File and Printer Sharing for
> Microsoft
> Netwo
> rks
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios_smb
> Upper Component: File and Printer Sharing for Microsoft
> Networks
> Lower Component: Message-oriented TCP/IP Protocol (SMB
> session)
> Owner of the binding path : File and Printer Sharing for
> Microsoft
> Netwo
> rks
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: File and Printer Sharing for Microsoft
> Networks
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t)
>
> Owner of the binding path : File and Printer Sharing for
> Microsoft
> Netwo
> rks
> Binding Enabled: No
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: File and Printer Sharing for Microsoft
> Networks
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t) #2
>
> Owner of the binding path : File and Printer Sharing for
> Microsoft
> Netwo
> rks
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: File and Printer Sharing for Microsoft
> Networks
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndiswanip
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: WAN Miniport (IP)
> Component Name : Generic Packet Classifier
> Bind Name: Gpc
> Binding Paths:
> Component Name : Application Layer Gateway
> Bind Name: ALG
> Binding Paths:
> Component Name : NetBIOS Interface
> Bind Name: NetBIOS
> Binding Paths:
> Owner of the binding path : NetBIOS Interface
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: NetBIOS Interface
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t)
>
> Owner of the binding path : NetBIOS Interface
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: NetBIOS Interface
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndis5
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> VBD
> Clien
> t) #2
>
> Owner of the binding path : NetBIOS Interface
> Binding Enabled: Yes
> Interfaces of the binding path:
> -Interface Name: netbios
> Upper Component: NetBIOS Interface
> Lower Component: WINS Client(TCP/IP) Protocol
> -Interface Name: tdi
> Upper Component: WINS Client(TCP/IP) Protocol
> Lower Component: Internet Protocol (TCP/IP)
> -Interface Name: ndiswanip
> Upper Component: Internet Protocol (TCP/IP)
> Lower Component: WAN Miniport (IP)
> Component Name : WAN Miniport (Network Monitor)
> Bind Name: NdisWanBh
> Binding Paths:
> Component Name : WAN Miniport (IP)
> Bind Name: NdisWanIp
> Binding Paths:
> Component Name : Direct Parallel
> Bind Name: {DADD58E2-2363-4474-BB08-4694EF91A9B3}
> Binding Paths:
> Component Name : WAN Miniport (PPPOE)
> Bind Name: {C0D04B45-0A09-43C7-83EC-0B01C0FBF0CE}
> Binding Paths:
> Component Name : WAN Miniport (PPTP)
> Bind Name: {383CB9EF-15FA-4460-BBE7-A4E973147647}
> Binding Paths:
> Component Name : WAN Miniport (L2TP)
> Bind Name: {454E35A4-7FA5-41C7-9E62-FD267A2986D1}
> Binding Paths:
> Component Name : RAS Async Adapter
> Bind Name: {FE6C6C33-566E-46C3-AC6B-A5F31191BAA4}
> Binding Paths:
> Component Name : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
> Client) #2
> Bind Name: {BE0F591A-8E5F-4264-A5BA-E9E86F44E429}
> Binding Paths:
> Component Name : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
> Client)
> Bind Name: {229E383C-2FB2-4AC3-9697-1E4B9363C1FB}
> Binding Paths:
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
>
> Note: run "netsh ipsec dynamic show /?" for more detailed
> information
>
> The command completed successfully
>
> For the second DC when i run the either or commands I get the below
> C:\Documents and Settings\Administrator.ALLIESINC>netdiag /v 'netdiag'
> is not recognized as an internal or external command, operable program
> or batch file.
>

 

Meinolf,

it's not taking the other command to copy it to a txt but i posted
everythying for you? also for DC2 it's not taking those commands at all what
am i doing wrong?

Thanks



"Meinolf Weber [MVP-DS]" wrote:

> Hello 2K3,
>
> Sorry but again it is not complete, please choose the command from before
> and copy the content of the textfile.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Here is the complet netdiag from first DC
> >
> > Owner of the binding path : WINS Client(TCP/IP) Protocol
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndiswanip
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: WAN Miniport (IP)
> > Component Name : Internet Protocol (TCP/IP)
> > Bind Name: Tcpip
> > Binding Paths:
> > Owner of the binding path : Internet Protocol (TCP/IP)
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t)
> >
> > Owner of the binding path : Internet Protocol (TCP/IP)
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t) #2
> >
> > Owner of the binding path : Internet Protocol (TCP/IP)
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: ndiswanip
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: WAN Miniport (IP)
> > Component Name : Client for Microsoft Networks
> > Bind Name: LanmanWorkstation
> > Binding Paths:
> > Owner of the binding path : Client for Microsoft Networks
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios_smb
> > Upper Component: Client for Microsoft Networks
> > Lower Component: Message-oriented TCP/IP Protocol (SMB
> > session)
> > Owner of the binding path : Client for Microsoft Networks
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: Client for Microsoft Networks
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t)
> >
> > Owner of the binding path : Client for Microsoft Networks
> > Binding Enabled: No
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: Client for Microsoft Networks
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t) #2
> >
> > Owner of the binding path : Client for Microsoft Networks
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: Client for Microsoft Networks
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndiswanip
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: WAN Miniport (IP)
> > Component Name : WebClient
> > Bind Name: WebClient
> > Binding Paths:
> > Component Name : DHCP Server
> > Bind Name: DHCPServer
> > Binding Paths:
> > Component Name : Wireless Configuration
> > Bind Name: wzcsvc
> > Binding Paths:
> > Component Name : Network Load Balancing
> > Bind Name: Wlbs
> > Binding Paths:
> > Owner of the binding path : Network Load Balancing
> > Binding Enabled: No
> > Interfaces of the binding path:
> > -Interface Name: ndis5
> > Upper Component: Network Load Balancing
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t)
> >
> > Owner of the binding path : Network Load Balancing
> > Binding Enabled: No
> > Interfaces of the binding path:
> > -Interface Name: ndis5
> > Upper Component: Network Load Balancing
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t) #2
> >
> > Component Name : Steelhead
> > Bind Name: RemoteAccess
> > Binding Paths:
> > Component Name : Dial-Up Server
> > Bind Name: msrassrv
> > Binding Paths:
> > Component Name : Remote Access Connection Manager
> > Bind Name: RasMan
> > Binding Paths:
> > Component Name : Dial-Up Client
> > Bind Name: msrascli
> > Binding Paths:
> > Component Name : File and Printer Sharing for Microsoft Networks
> > Bind Name: LanmanServer
> > Binding Paths:
> > Owner of the binding path : File and Printer Sharing for
> > Microsoft
> > Netwo
> > rks
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios_smb
> > Upper Component: File and Printer Sharing for Microsoft
> > Networks
> > Lower Component: Message-oriented TCP/IP Protocol (SMB
> > session)
> > Owner of the binding path : File and Printer Sharing for
> > Microsoft
> > Netwo
> > rks
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: File and Printer Sharing for Microsoft
> > Networks
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t)
> >
> > Owner of the binding path : File and Printer Sharing for
> > Microsoft
> > Netwo
> > rks
> > Binding Enabled: No
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: File and Printer Sharing for Microsoft
> > Networks
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t) #2
> >
> > Owner of the binding path : File and Printer Sharing for
> > Microsoft
> > Netwo
> > rks
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: File and Printer Sharing for Microsoft
> > Networks
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndiswanip
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: WAN Miniport (IP)
> > Component Name : Generic Packet Classifier
> > Bind Name: Gpc
> > Binding Paths:
> > Component Name : Application Layer Gateway
> > Bind Name: ALG
> > Binding Paths:
> > Component Name : NetBIOS Interface
> > Bind Name: NetBIOS
> > Binding Paths:
> > Owner of the binding path : NetBIOS Interface
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: NetBIOS Interface
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t)
> >
> > Owner of the binding path : NetBIOS Interface
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: NetBIOS Interface
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndis5
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
> > VBD
> > Clien
> > t) #2
> >
> > Owner of the binding path : NetBIOS Interface
> > Binding Enabled: Yes
> > Interfaces of the binding path:
> > -Interface Name: netbios
> > Upper Component: NetBIOS Interface
> > Lower Component: WINS Client(TCP/IP) Protocol
> > -Interface Name: tdi
> > Upper Component: WINS Client(TCP/IP) Protocol
> > Lower Component: Internet Protocol (TCP/IP)
> > -Interface Name: ndiswanip
> > Upper Component: Internet Protocol (TCP/IP)
> > Lower Component: WAN Miniport (IP)
> > Component Name : WAN Miniport (Network Monitor)
> > Bind Name: NdisWanBh
> > Binding Paths:
> > Component Name : WAN Miniport (IP)
> > Bind Name: NdisWanIp
> > Binding Paths:
> > Component Name : Direct Parallel
> > Bind Name: {DADD58E2-2363-4474-BB08-4694EF91A9B3}
> > Binding Paths:
> > Component Name : WAN Miniport (PPPOE)
> > Bind Name: {C0D04B45-0A09-43C7-83EC-0B01C0FBF0CE}
> > Binding Paths:
> > Component Name : WAN Miniport (PPTP)
> > Bind Name: {383CB9EF-15FA-4460-BBE7-A4E973147647}
> > Binding Paths:
> > Component Name : WAN Miniport (L2TP)
> > Bind Name: {454E35A4-7FA5-41C7-9E62-FD267A2986D1}
> > Binding Paths:
> > Component Name : RAS Async Adapter
> > Bind Name: {FE6C6C33-566E-46C3-AC6B-A5F31191BAA4}
> > Binding Paths:
> > Component Name : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
> > Client) #2
> > Bind Name: {BE0F591A-8E5F-4264-A5BA-E9E86F44E429}
> > Binding Paths:

 

Hello 2K3,

If the support\tools\suptools.msi from the 2003 installation disk is not
installed on the server the command's dcdiag, netdiag and repadmin for exdample
are not available, so install the support tools.

If you run:

netdiag /v >c:\netdiag.log

in a command prompt on the DC it creates the netdiag.log on the c-drive with
the complete output.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Meinolf,
>
> it's not taking the other command to copy it to a txt but i posted
> everythying for you? also for DC2 it's not taking those commands at
> all what am i doing wrong?
>
> Thanks
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello 2K3,
>>
>> Sorry but again it is not complete, please choose the command from
>> before and copy the content of the textfile.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Here is the complet netdiag from first DC
>>>
>>> Owner of the binding path : WINS Client(TCP/IP) Protocol
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndiswanip
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: WAN Miniport (IP)
>>> Component Name : Internet Protocol (TCP/IP)
>>> Bind Name: Tcpip
>>> Binding Paths:
>>> Owner of the binding path : Internet Protocol (TCP/IP)
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t)
>>> Owner of the binding path : Internet Protocol (TCP/IP)
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t) #2
>>> Owner of the binding path : Internet Protocol (TCP/IP)
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: ndiswanip
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: WAN Miniport (IP)
>>> Component Name : Client for Microsoft Networks
>>> Bind Name: LanmanWorkstation
>>> Binding Paths:
>>> Owner of the binding path : Client for Microsoft Networks
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios_smb
>>> Upper Component: Client for Microsoft Networks
>>> Lower Component: Message-oriented TCP/IP Protocol (SMB
>>> session)
>>> Owner of the binding path : Client for Microsoft Networks
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: Client for Microsoft Networks
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t)
>>> Owner of the binding path : Client for Microsoft Networks
>>> Binding Enabled: No
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: Client for Microsoft Networks
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t) #2
>>> Owner of the binding path : Client for Microsoft Networks
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: Client for Microsoft Networks
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndiswanip
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: WAN Miniport (IP)
>>> Component Name : WebClient
>>> Bind Name: WebClient
>>> Binding Paths:
>>> Component Name : DHCP Server
>>> Bind Name: DHCPServer
>>> Binding Paths:
>>> Component Name : Wireless Configuration
>>> Bind Name: wzcsvc
>>> Binding Paths:
>>> Component Name : Network Load Balancing
>>> Bind Name: Wlbs
>>> Binding Paths:
>>> Owner of the binding path : Network Load Balancing
>>> Binding Enabled: No
>>> Interfaces of the binding path:
>>> -Interface Name: ndis5
>>> Upper Component: Network Load Balancing
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t)
>>> Owner of the binding path : Network Load Balancing
>>> Binding Enabled: No
>>> Interfaces of the binding path:
>>> -Interface Name: ndis5
>>> Upper Component: Network Load Balancing
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t) #2
>>> Component Name : Steelhead
>>> Bind Name: RemoteAccess
>>> Binding Paths:
>>> Component Name : Dial-Up Server
>>> Bind Name: msrassrv
>>> Binding Paths:
>>> Component Name : Remote Access Connection Manager
>>> Bind Name: RasMan
>>> Binding Paths:
>>> Component Name : Dial-Up Client
>>> Bind Name: msrascli
>>> Binding Paths:
>>> Component Name : File and Printer Sharing for Microsoft Networks
>>> Bind Name: LanmanServer
>>> Binding Paths:
>>> Owner of the binding path : File and Printer Sharing for
>>> Microsoft
>>> Netwo
>>> rks
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios_smb
>>> Upper Component: File and Printer Sharing for Microsoft
>>> Networks
>>> Lower Component: Message-oriented TCP/IP Protocol (SMB
>>> session)
>>> Owner of the binding path : File and Printer Sharing for
>>> Microsoft
>>> Netwo
>>> rks
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: File and Printer Sharing for Microsoft
>>> Networks
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t)
>>> Owner of the binding path : File and Printer Sharing for
>>> Microsoft
>>> Netwo
>>> rks
>>> Binding Enabled: No
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: File and Printer Sharing for Microsoft
>>> Networks
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t) #2
>>> Owner of the binding path : File and Printer Sharing for
>>> Microsoft
>>> Netwo
>>> rks
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: File and Printer Sharing for Microsoft
>>> Networks
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndiswanip
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: WAN Miniport (IP)
>>> Component Name : Generic Packet Classifier
>>> Bind Name: Gpc
>>> Binding Paths:
>>> Component Name : Application Layer Gateway
>>> Bind Name: ALG
>>> Binding Paths:
>>> Component Name : NetBIOS Interface
>>> Bind Name: NetBIOS
>>> Binding Paths:
>>> Owner of the binding path : NetBIOS Interface
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: NetBIOS Interface
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t)
>>> Owner of the binding path : NetBIOS Interface
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: NetBIOS Interface
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndis5
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: Broadcom BCM5708C NetXtreme II GigE (NDIS
>>> VBD
>>> Clien
>>> t) #2
>>> Owner of the binding path : NetBIOS Interface
>>> Binding Enabled: Yes
>>> Interfaces of the binding path:
>>> -Interface Name: netbios
>>> Upper Component: NetBIOS Interface
>>> Lower Component: WINS Client(TCP/IP) Protocol
>>> -Interface Name: tdi
>>> Upper Component: WINS Client(TCP/IP) Protocol
>>> Lower Component: Internet Protocol (TCP/IP)
>>> -Interface Name: ndiswanip
>>> Upper Component: Internet Protocol (TCP/IP)
>>> Lower Component: WAN Miniport (IP)
>>> Component Name : WAN Miniport (Network Monitor)
>>> Bind Name: NdisWanBh
>>> Binding Paths:
>>> Component Name : WAN Miniport (IP)
>>> Bind Name: NdisWanIp
>>> Binding Paths:
>>> Component Name : Direct Parallel
>>> Bind Name: {DADD58E2-2363-4474-BB08-4694EF91A9B3}
>>> Binding Paths:
>>> Component Name : WAN Miniport (PPPOE)
>>> Bind Name: {C0D04B45-0A09-43C7-83EC-0B01C0FBF0CE}
>>> Binding Paths:
>>> Component Name : WAN Miniport (PPTP)
>>> Bind Name: {383CB9EF-15FA-4460-BBE7-A4E973147647}
>>> Binding Paths:
>>> Component Name : WAN Miniport (L2TP)
>>> Bind Name: {454E35A4-7FA5-41C7-9E62-FD267A2986D1}
>>> Binding Paths:
>>> Component Name : RAS Async Adapter
>>> Bind Name: {FE6C6C33-566E-46C3-AC6B-A5F31191BAA4}
>>> Binding Paths:
>>> Component Name : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD
>>> Client) #2
>>> Bind Name: {BE0F591A-8E5F-4264-A5BA-E9E86F44E429}
>>> Binding Paths: