|
Home > Archive > 70-216 > August 2001 > Answer this question please
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Answer this question please
|
|
| esexon 2001-08-07, 4:18 pm |
| You add a Windows 2000 Professional computer to your network and share several resources from it. When other clients attempt to contact this new computer, they are unsuccessful. You are concerned that the new computer is not configured to use WINS properly.
Which command could you run to check this?
a. netstat –e?
b. netstat –s?
c. netstat –r?
d. netdiag /test:WINS?
According to the book i'm reading the answer is d
I have tried to run this command but was unsuccesful.Any ideas?
Cheers
Evan | |
| Joe Blacke 2001-08-07, 9:06 pm |
| Just a question, but when you try to run netdiag on a pc, is that pc a WINS client? Do you have a WINS server on your network? | |
| esexon 2001-08-08, 2:11 am |
| I don't have a wins server running, i do have dhcp configured with options 44 and 46.
Maybe this is why that command doesn't work?
Evan | |
| el duderino 2001-08-08, 10:27 am |
| Answer d is correct. The reason that netdiag doesn't work for you is that it probably isn't installed. It is located in the support\tools directory of the Windows CD. Netdiag and dcdiag are nice diagnostic tools for 2000. | |
| esexon 2001-08-08, 11:41 am |
| Thanks
I found some useful info on Netdiag on the Brainbuzz site.
---------------------------------------------
Netdiag can solve moderately complex TCP/IP problems, and
even provides advice about what needs to be fixed immediately
and what can be fixed at a later time. Not only does it
address TCP/IP problems, it can also examine and diagnose
problems with NWLink configuration.
The information Netdiag collects is obtained from a variety
of sources. These include .dll files, the registry, and even
other command line networking tools. It first checks the
network configuration on the machine, and then runs the
appropriate tests for the machine's unique configuration.
Netdiag Switches
Netdiag is run from the command prompt and supports the
following switches:
/q - Provides minimal output and supplies information about
errors only.
/v - Provides verbose (detailed) output
/l - Allows Netdiag to send the output to a text file –
Netdiag.log
/debug – Provides more detailed output than the /v switch
/d: - Finds a DC in the specified domain
/fix – Fixes problems identified by DC and DNS tests
/DcaccountEnum – Enumerates DC machine accounts
/test: – runs a particular test rather than all
of them
/skip: – Skips a particular test rather than
running all of them
Note that the /fix switch performs a very specific and
limited function. You can get details on this in
KB article Q219289.
The Netdiag.log file is stored in the folder.
The text file contains information dependent on the level of
detail you have configured Netdiag to show.
Netdiag Tests
Netdiag performs a series of 22 tests. These tests include:
IPConfig – this runs the ipconfig utility to determine local
IP configuration
Autonet – tests basic network card functionality and APIPA
address assignment
IpLoopBk – pings the loopback address 127.0.0.1 to determine
status of the TCP/IP stack
DefGW – pings the default gateway(s) on each interface
installed on the machine
NbtNm – tests domain membership and status of NetBIOS names
registered
WINS – sends name queries to WINS servers configured on the
machine
Winsock – runs a command to retrieve available transport
protocols
DNS – check DNS cache and registration status of all adapters.
If the machine is a DC, checks that the appropriate
entries are in the netlogon.dns file
Browser – checks if the redirector (workstation) service is
running. Also checks details on NetBT transports,
and browser status.
DsGetDc – Checks and tests for Domain Controllers
DcList – Gets a list of Domain Controllers from the Directory
Service
Trust – Tests machine's trust relationship with the domain;
confirms secure channel to DC.
Kerberos – Tests Kerberos package and ticket cache.
Ldap – Test LDAP on all active Domain Controllers in the domain.
Route – Runs the Route Print command
Netstat – Runs the netstat command
Bindings – Tests all interface bindings
WAN – Check settings and status of RAS connections
Modem – Checks modem settings
Netware – Checks to see if NetWare is using a Tree or Bindery.
Determines context.
IPX – Checks IPX configuration
IPSec – Check IPSec policies and provides detailed information
about SAs.
Heres the link for the whole article
http://itresources.brainbuzz.com/tu...5&pn=Networking
Cheers and thanks for everyones help. |
|
|
|
|