Network: testing
Once network adapters, protocols, and services have been installed the network should be tested. Tests include searching for a computer by Name and then testing UNC paths to see if resources can be located. A diagnostic will be executed and then the Network Neighborhood will be browsed to verify that all shared resources are visible. |
|
Internet Access |
Open Internet Explorer on each networked computer, enter familysearch.org in the Address bar and click the Refresh button. If the home page is displayed then the Internet is accessable. If the Internet is inaccessabile from one computer then the network hardware and TCP/IP installation should be tested. physical connection - lights on card test tcp/ip stack - ping localhost test network connectivity - ping network gateway - filtered ????? verify IP lease ?? If the Internet is inaccessabile from several computers then the network hardware and router/firewall should be tested.
Router/Firewall testing - ISP testing ??
|
Basic Function |
Start at Client11 and search for a computer that is sharing resources. To search by name click the Start button, select Find -> Computer and enter the computer name in the search box. Click Find Now. If the computer is not found, verify that it is turned on, is correctly connected to the network, and has a compatible workgroup name. Repeat this procedure from other clients to confirm full visibility over the network. If you can ping a remote computer IP but not the name, and you have WINS or enable NetBIOS over TCP/IP, this may be an outdated NetBIOS name resolution in the local NetBIOS name cache. You may want to run NBTSTAT -r to reset the cache and force the computer to retrieve remote computer name.
Install WNTIPCfg Once installed, Wntipcfg lets you easily see the addresses of any/all network cards in your system; to see how long each address is good for; and if you wish, to force the address to be released and renewed on demand. Wntipcfg is free. The download and additional information is here. http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/wntipcfg-o.asp |
UNC Paths |
From each computer, open Windows Explorer and enter a UNC path to a shared resource in the address bar. From Client11 enter \\<host name>\<sharedfolder> in the address bar. If Windows Explorer opens to the <sharedfolder> folder on <host name>, then UNC paths are working. |
Network Browsing |
In the figure below, My Network Places shows three shared folders, one local and two remote. Unlike Network Neighborhood in W9x, Network Places displays shared resources, not workgroup computers. Click 'View workgroup computers' to view workgroup computers that are sharing resources. Network Places does not display network resources by default, you can add them with the 'Add a network place' wizard or enable automatic searching by clicking Tools > Folder Options > View, Automatically search for network folders and printers. Note that NetBEUI is not part of the default XP network configuration. If resources on W9x systems are not bound to TCP/IP they will not appear in Network Places unless NetBEUI is installed. 
Windows 2000/XP SystemsBy default, Windows 2000/XP systems do not have the NetBEUI protocol installed. NetBEUI broadcasts the existence of a PC so they will show up in the browse list maintained by the master browser on the network. TCP/IP does not have the same ability, however. As a result, you might find that systems without NetBEUI installed are not shown in the Network Neighborhood or My Network Places. If you can ping ip and computer name but can't see it on My Network Places even you have correct DNS and WINS settings. Or you have enabled NetBIOS over TCP/IP in a peer to peer workgroup network. Or when you get NetBIOS name resolution failure message, try disabling Internet Connection Firewall. Browse Master operationIf all computers with shared resources are not visible you may have to fix the Browse Master election parameters. The Network Neighborhood is a separate resource in the Microsoft Networking suite of services operating on a computer referred to as the Browse Master. A problem with the Neighborhood may be a problem with the Browse Master and not with the network. It is possible for the Browse Master to be absent or malfunctioning, disabling Network Neighborhood browsing, while NetBEUI communications are unaffected. A common problem, especially with mixed Win95 and Win98 peer-to-peer networks, is difficulty with the Browse Master election. One computer in the Workgroup is selected to manage the Network Neighborhood view with one or more computers designated as backups. The default setting for Browse Master election is Automatic. 
The Microsoft Networks Properties dialog box allows a specific system to be the Browse Master. One solution is to change these default settings to Enabled for one computer and Disabled for the others. Select one machine which is always on and open the File and printer sharing component in the Network control panel. Set Browse Master to Enabled. This machine will always be the Browse Master. On all other computers, set Browse Master to Disabled. As long as the Enabled computer is up the Network Neighborhood will be present, although it can take up to fifteen minutes for changes to become visible. This is not the only solution, any setting that reduces the number of eligible Browse Masters will help relieve the problem. |
Network Troubleshooting |
These sites provide additional information on network troubleshooting:
|