Computer Configuration Issues


If you use a broadband connection to the Internet, you'll probably have a switch/router appliance connecting your small LAN to the cable or DSL modem. These inexpensive devices allow your LAN to share a single Internet connection (that is, a single IP address) on the Internet, while providing for separate addresses for each computer on the LAN.

DHCP (the Dynamic Host Configuration Protocol) allows the router/switch to automatically configure your computer with the network addressing information it needs when it boots up. When you add a new computer to the LAN, you need to be sure that it's configured to use DHCP. Otherwise , if you've configured a static address on the computer, you need to be sure that the following are true:

  • The address is compatible with the addresses of other computers on your network.

  • The address is not already in use by another computer on the network.

Tip

Although you might consider yourself a network guru just because you have a network at home, don't try to step on your own toes. That is, if you decide to assign static IP addresses to some computers in your network, such as a server, then be sure to enable your DHCP service to use an address range which doesn't include that address. Or, if your switch allows, enter a record for the static address. This can be useful when you're connecting to the Internet yet maintaining an internal Windows domain-based network.

You can check your computer configuration easily. For Windows 2000, for example, follow these steps to configure your computer to use DHCP:

  1. Select Start, Settings, Network, Dial-up Connections.

  2. Right-click Local Area Network and select Properties from the menu that appears.

  3. Scroll down in the Components section of the properties sheet shown in Figure 54.1, highlight Internet Protocol (TCP/IP), and click the Properties button.

    Figure 54.1. Select the Internet Protocol to troubleshoot network address issues.

    graphics/54fig01.gif

  4. The Internet Protocol (TCP/IP) Properties sheet pops up, as shown in Figure 54.2. If you are using DHCP, be sure that the Obtain an IP Address Automatically option is selected. Unless your Internet provider has told you otherwise, the Obtain DNS Server Address Automatically option should also be selected.

    Figure 54.2. Be sure you have the correct IP configuration information filled in for this dialog box.

    graphics/54fig02.gif

  5. If you configured your computers with static addresses, select Use the Following IP Address, and the IP Address, Subnet Mask, and Default Gateway fields should contain the appropriate values. If you chose to use DHCP (automatic configuration), you will not see the IP address, DNS servers, and so on that were assigned by the switch. To see these details, you must run IPCONFIG /ALL from the command line, as described in step 7.

  6. If all looks okay in the configuration screens, check out what address your computer is actually using. Choose Start, Programs, Accessories, Command Prompt for Windows 2000 (or Windows 2003 servers), or Start, Programs, Command Prompt for earlier versions of Windows.

  7. From the command prompt, issue the command IPCONFIG /ALL for Windows NT/2000/XP or Windows 2003 servers operating systems (you can use WINIPCFG to find the same information for Windows 95/98). The response to this command will include a lot of information, so look for the IP address and the subnet mask. Try using the ping command (described in Chapter 28, "Troubleshooting Tools for TCP/IP Networks") from another computer to determine whether it can bounce packets off this address. If not, you probably have unplugged the computer from the network (either at the network card end or at the switch/router or hub).

Another possible cause of the problem is that you are using an address that is not in the same network or subnet as the other computers. It doesn't matter if all the cables are connected to the hub or switch and each computer's network card if you have misconfigured IP addresses or subnet masks. For example, a computer with an IP address of 10.10.10.1 is not going to talk to a computer with an address of 140.176.222.1, no matter how long you try, unless you go through a router that has been configured to pass this information. The network adapter card detects the data you try to send back and forth, but because the protocol stack knows that it's destined for a different network, those packets are ignored and never passed up to the Application level.

Figure 54.3 shows an example of using a switch/router to connect to the Internet through a cable or DSL modem.

Figure 54.3. Connect to the Internet using a cable or DSL modem and a router/switch. Note that the IP address for Computer C is not valid on the LAN and can't pass through the switch/router.

graphics/54fig03.gif

In this example, the Internet service provider (ISP) has assigned an IP address to your connection (140.176.200.123). Because you have more than one computer, you went to the local computer store and bought a small switch/router designed to work with broadband connections. Note that the switch/router is plugged into the broadband modem using one port, and plugged into your LAN using another port. To keep track of both connections, the switch/router uses a different address on the port that connects to your LAN.

In this example, the IP address is 10.10.10.1. The switch/router uses the address range of 10.10.10.0 through 10.10.10.254 to allocate IP addresses to computers on the LAN. This means that Computer C has an invalid address, which was configured as a static address.

Yet, when computer A (10.10.10.2) on your network wants to send or receive data to or from the Internet, the switch/router knows that the IP address of the Internet server is different from the LAN address (the 10.10.10.0 address space). Thus, Computer A knows that it must send the data packet to the default gateway, which is the switch/router (10.10.10.1).

When the switch/router receives the data packet, it substitutes its own valid Internet address (140.176.200.123) in the packet header and sends it to the Internet through the broadband modem. When a response is received back from the Internet connection, the switch/router removes the 140.176.200.123 address from the packet header and puts Computer A's address (10.10.10.2) in the header so that it can be delivered to Computer A.

The important thing to keep in mind here is that addresses used inside the network are not valid on the Internet. The switch/router must use sleight of hand to act as a "man in the middle" for you so that, although you have multiple computers on your LAN, the switch/router makes the cable or DSL modem think you have only one. The switch/router keeps track of which computer on the LAN sends out requests and makes sure that packets are routed back to the correct computer.

Note

You can learn more about reserved IP address spaces that you can use in your local network but that are not valid on the Internet. Chapter 25, "Overview of the TCP/IP Protocol Suite," covers this topic in detail.

When Computer A wants to talk to Computer B, it compares the address of Computer B (10.10.10.3) with its own address. Because the address falls in the same network address space, it doesn't send the packet to the default gateway. Instead, it just broadcasts a packet on the LAN knowing that Computer B will see the packet and pick it up.

So far, everything is working as it's supposed to. However, let's suppose you just brought a computer from work to your home office (Computer C) and plugged it into your network. At work, the computer had been configured with a static address of 123.111.221.43. When you try to send or receive data from Computer C, nothing happens because of the following:

  • Computer C has an IP address that does not match the addresses on the LAN, so the other computers just ignore the packets that Computer C sends out.

  • Computer C was configured at work to use a different default gateway address, so it can't even get a packet to go through the router/switch.

The point is that if your switch/router allows for DHCP and you set up each computer to use DHCP, things should work just as you expect. If you try to mix and match computers with different subnets on the same LAN, you're going to have trouble.

Note

Broadband services come in all sizes and shapes . Just check out Chapter 16, "Dedicated Connections." If your service provider is using DSL, you might have to connect a small device to your telephone outlet before you can plug in a telephone. This device prevents telephone interference from causing problems with the frequencies used on the copper wire by the DSL service. And the reverse is also true. These filters can keep the DSL frequencies from interfering with and degrading the voice channel. Not all DSL services require this sort of device. If your service does, when you buy a new phone for a different room, be sure you obtain another of these devices. Don't just plug in the phone and expect all to be well. A ringing phone or a phone off the hook can cause enough interference to make the DSL connection sporadic or nonfunctional for this kind of connection.



Upgrading and Repairing Networks
Upgrading and Repairing Networks (5th Edition)
ISBN: 078973530X
EAN: 2147483647
Year: 2003
Pages: 434

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net