Manual Pages
Table of Contents
na_cifs_testdc - test the Filer's connection to Windows NT
domain controllers
cifs testdc [ domainname ]
cifs testdc [ WINSsvrIPaddress ] domainname [ filername ]
The cifs testdc command tests the Filer's ability to connect
with Windows NT domain controllers. The output of
the cifs testdc command is useful in the diagnosis of
CIFS-related network problems.
There are two forms of the command:
cifs testdc [ domainname ]
is used when CIFS has been successfully started and is
operational.
domainname tells the Filer which NT domain to search for
domain controllers. If omitted, the Filer will search for
domain controllers in the NT domain in which it is configured.
cifs testdc [ WINSsvrIPaddress ] domainname [ filername ]
is used when the CIFS subsystem is not running.
WINSsvrIPaddress is optionally given to have the Filer use
WINS name resolution to locate domainname; otherwise, the
Filer will use broadcast name resolution to attempt to
find domain controllers. WINSsvrIPaddress is the IP
address of a WINS server in the domain.
filername is the name of the Filer in the domain. If the
name of the Filer is not given, then the Filer will manufacture
a name to use for the search.
The following example was executed while the CIFS subsystem
was started.
purple> cifs testdc mydc
Current Mode of NBT is H Mode
Netbios scope ""
Registered names...
DWATSON1 < 0> WINS
DWATSON1 < 3> WINS
DWATSON1 <20> WINS
WIN2KTEST < 0> WINS
Testing Primary Domain Controller
found 1 addresses
trying 10.10.10.56...10.10.10.56 is alive
found PDC SONOMA
Testing all Domain Controllers
found 24 unique addresses
found DC SONOMA at 10.10.10.56
found DC KENWOOD at 10.10.20.42
...Not able to communicate with DC 192.168.208.183
trying 192.168.208.183...no answer from 192.168.208.183
found DC ROCKRIDGE at 10.10.20.41
...Not able to communicate with DC 172.21.0.5
trying 172.21.0.5...no answer from 172.21.0.5
...Not able to communicate with DC 172.21.4.210
trying 172.21.4.210...no answer from 172.21.4.210
.Not able to communicate with DC 172.20.4.31
trying 172.20.4.31...no answer from 172.20.4.31
...Not able to communicate with DC 198.95.230.56
trying 198.95.230.56...no answer from 198.95.230.56
...Not able to communicate with DC 172.20.4.66
trying 172.20.4.66...no answer from 172.20.4.66
...Not able to communicate with DC 172.21.8.210
trying 172.21.8.210...no answer from 172.21.8.210
...Not able to communicate with DC 192.168.200.76
trying 192.168.200.76...no answer from 192.168.200.76
...Not able to communicate with DC 10.162.5.240
trying 10.162.5.240...no answer from 10.162.5.240
found DC ROCKVILLE at 192.168.80.5
found DC RTP-BDC at 192.168.125.13
...Not able to communicate with DC 10.162.5.252
trying 10.162.5.252...no answer from 10.162.5.252
...Not able to communicate with DC 192.168.199.11
trying 192.168.199.11...192.168.199.11 is alive
.Not able to communicate with DC 192.168.199.42
trying 192.168.199.42...no answer from 192.168.199.42
.Not able to communicate with DC 10.160.4.21
trying 10.160.4.21...no answer from 10.160.4.21
...Not able to communicate with DC 10.10.20.192
trying 10.10.20.192...no answer from 10.10.20.192
...Not able to communicate with DC 10.10.20.90
trying 10.10.20.90...no answer from 10.10.20.90
...Not able to communicate with DC 10.10.20.144
trying 10.10.20.144...10.10.20.144 is alive
found DC DENVER-SRV at 192.168.150.11
found DC SOUTHFIELD-SRV at 192.168.45.11
found DC NAPA at 10.10.10.55
The following example was executed after the CIFS subsystem
was terminated.
purple> cifs testdc 10.10.10.55 nt-domain
Test will use WINS name resolution
Testing WINS address...10.10.10.55 is alive
Using name NTAP1783328093
Testing name registration...
succeeded
Current Mode of NBT is H Mode
Netbios scope ""
Registered names...
NTAP1783328093 < 0> WINS
Testing Primary Domain Controller
found 1 addresses
trying 172.18.1.65...172.18.1.65 is alive
found PDC CIFS_ALPHA
Testing all Domain Controllers
found 2 unique addresses
found DC CIFS_ALPHA at 172.18.1.65
found DC FRENCH40 at 10.150.13.15
Table of Contents