Bookmark
Page

Troubleshooting Your Network Software Configuration

When connecting a Windows workstation to a network, in addition to the network card and cable there are three basic software parameters to consider. These are:

1.0 Network Protocol – TCP/IP is the network protocol required for accessing the Internet, and largely for this reason it has become the standard on almost all PC LANs. TCP/IP is normally installed when you install a new network card. You may still encounter NetBEUI, the original Windows networking protocol, either by itself or in addition to TCP/IP, and on networks using Novell NetWare servers you may also need IPX/SPX.

2.0 Client for Microsoft Networks – This permits logon to a Microsoft network and the capability to share network resources. In a NetWare network, the counterpart is Microsoft Client for NetWare.

3.0 File and Printer Sharing – This is only needed for systems that will be sharing some of their own resources, such as drives, folders or local printers, with other network users.

There are several ways that these configurations can be added or verified, including a Microsoft wizard for the technologically faint of heart. The most direct way is to right-click on your Network Neighborhood (or My Network Places) and then select Properties from the pop-up menu. If you have XP, there is an additional step of right-clicking on Local Area Connection, and then selecting Properties again.

On the General tab you will see a list of the network protocols and services that are already installed, and three buttons labeled Install, Uninstall, and Properties. To add something, click the Install button. Next, choose whether you want to add a Client, Service, or Protocol. TCP/IP can be added from Protocol. Client for Microsoft Networks uses Client of course, and for File and Printer Sharing, choose Services. In some operating systems, you would need to select Microsoft first before you get to these configuration options.

Each version of Windows has slight variations, but there are certain basics you need to know to configure or troubleshoot your system’s network configuration. These are:

a. Static or Dynamic IP addressing – If you are using static IP addressing, you will need to manually enter the correct IP address, subnet mask, DNS, and gateway. If your network has a DHCP service running, this information will all be provided by your DHCP server.

b. Domain logging – If your network uses a PDC (Primary Domain Controller) server, make sure you have configured your system with the correct domain name to log in and have created a login and password for this account.

c. Workgroup name – Every computer in your network must use the same workgroup name, or shared resources such as folders, drives, and printers won’t be able available to some users.

d. Computer name – Each computer must have a unique computer name. If you have duplicate computer names, those computers won’t be able to access shared resources.

e. Resources to share – Resources can easily be shared by just right clicking an icon for the drive, folder or printer and then select Sharing from the pop-up menu. Depending on your OS version, there may be some security requirements that you would have to configure first.

f. Internet Connection – There are many third party proxy services (such as Wingate and WinProxy) and these might require you to install their particular client program on your system in order to connect to the internet. Another option for a peer-to-peer network is ICS (Internet Connection Sharing) that is built in to some Windows versions. Routers, gateways, or access points can be configured to share internet connection also, so you would need to point your workstation to the correct device as your access. It’s basically a matter of determining where the Internet access is available in you network, and then configuring for that. Configuring the network itself to provide Internet access is the subject of another tech tip.

Disclaimer - The Micro 2000 Tech Tip is a free service providing information only. While we use reasonable care to see that this information is correct, we do not guarantee it for accuracy, completeness or fitness for a particular purpose. Micro 2000, Inc. shall not be liable for damages of any kind in connection with the use or misuse of this information.