Appendixes
The warning tells you that you should set TCPIP configurations individually for each connec- tion. If you set the TCPIP settings in the Network dialog box under Dial-Up Adapter, those
settings apply to all connections you create. In order to create different connections — say, for the Internet, for a work network, or for a home network — you configure TCPIP for each
connection in the Dial-Up Networking window.
Working with TCPIP and Windows XP
Windows 2000 and XP install with the TCPIP protocol. You can connect a new XP computer to a network, and the new computer figures out the protocol settings and joins the network
without much configuration. You should, however, understand how to change configuration yourself, in case you need to change the network.
For more information about setting up a network card, file and printer sharing, and other net- working software, see Chapter 10.
To set up or edit TCPIP in Windows XP, follow these steps:
1. Right-click My Network Places and click Properties from the pop-up menu. The
Network Connections dialog box appears, as shown in Figure B-17. Your Network Connections dialog box might not display the same items in the figure.
2. Right-click the Local Area Connection and click Properties. The Local Area Connection
Properties dialog box appears, as shown in Figure B-18. You can rename the Local Area Connection using the same pop-up menu if you prefer to call
it Home, or Plumleys, or some other name more true to your personal network.
3. Click the Internet Protocol TCPIP to select it, and click the Properties button. The
Internet Protocol TCPIP Properties dialog box appears, as shown in Figure B-19.
Figure B-17: Network Connections shows LAN connections, Internet connections, and dial-up connections.
Tip Cross-
Reference
Appendix B ✦ IP Addressing
Figure B-18: Edit or add components to the network properties.
4. Click Use the Following IP Address. Enter the IP address, subnet mask, and default gate-
way you want to assign the computer in your network.
5. Optionally, assign a preferred DNS server and an alternate DNS server.
Figure B-19: Change TCPIP address, subnet mask, or DNS server.
Appendixes
You can click the Advanced button to assign additional IP, DNS, and WINS settings, if need be. On a small home or business network, you won’t need to assign additional settings.
6. Click OK and then click OK again to close the Local Area Connection Properties dialog
box. Reboot if prompted, although generally Windows XP does not need to be rebooted for TCPIP configuration.
Using Dial-Up Networking in Windows XP
Windows XP uses a wizard to help you create and configure a dial-up connection. With the New Connection Wizard, you can set up a dial-up or LAN connection to the Internet or a dial-
up or VPN connection to another location, connect to a home network, or connect to another computer using a direct cable or infrared port.
For a dial-up connection, use the Connect to the network at my workplace option. To create a dial-up network connection, follow these steps:
1. Click Start ➪ Control Panel. The Control Panel dialog box appears. 2. Double-click Network Connections. The Network Connections dialog box appears.
3. In Network Tasks, click Create a New Connection. The New Connection Wizard dialog
box appears.
4. Click Next. The second wizard dialog box appears, as shown in Figure B-20. 5. Click Connect to the Network at My Workplace; then click Next. The next wizard dialog
box appears, as shown in Figure B-21.
6. Choose Dial-Up Connection and click Next. The next wizard dialog box appears. 7. Type a name for the connection, such as home, work, Tammy’s, or some other easily
recognizable name. Click Next. The next wizard dialog box appears.
8. Type the phone number. Add a 1 and the area code if necessary. Click Next. The final
wizard dialog box appears.
9. Click Finish. The Connect dialog box appears, as shown in Figure B-22.
Figure B-20: Create a new connection.
Tip
Appendix B ✦ IP Addressing
Figure B-21: Choose a dial-up connection.
Figure B-22: Connect by dial-up.
10. Enter your username and password needed to connect to the dial-up connection. Click
Dial to connect.
Using TCPIP and the Macintosh
Macintosh OS X comes with TCPIP installed by default. You can also change the TCPIP set- tings, however, to fit into your network if necessary. In the Network Preferences dialog box,
you can change settings for Ethernet, AirPort, an internal modem, AppleTalk, proxies, and other settings.
To edit TCPIP settings, follow these steps:
1. Click the Apple ➪ System Preferences. The System Preferences dialog box appears, as
shown in Figure B-23.
Appendixes
Figure B-23: Use System Preferences in the Mac to change Network settings.
2. Double-click the Network icon. The Network dialog box appears, as shown in
Figure B-24.
Figure B-24: Change TCPIP settings in a Mac OS X system.
Appendix B ✦ IP Addressing
3. To change network settings, choose the port you want to change from the Show menu;
choose the Built-in Ethernet port, for example.
4. Optionally, create a new location by clicking Location ➪ New Location. 5. When finished with the dialog box, click Apply Now.
Creating a connection with the Mac
You can create a connection with the Mac OS X system easily by using the System Preferences and Network dialog boxes. To create a connection, follow these steps:
1. Click the Apple ➪ System Preferences. The System Preferences dialog box appears. 2. Double-click the Network icon. The Network dialog box appears.
3. In Show, click Internal Modem. The dialog box changes to enable you to use TCPIP, as
shown in Figure B-25.
4. Alternatively, you can select Built-in Ethernet in the Show drop-down list, click the
PPPoE tab, and configure PPPoE information, as shown in Figure B-26.
5. You can also, depending on what you select in the Show drop-down list, configure a
proxy and adjust the modem settings in the same dialog box.
6. When finished, click Apply Now.
Figure B-25: Change TCPIP settings for a dial-up connection.
Appendixes
Figure B-26: Change PPPoE settings in a Mac OS X system.
Creating a dial-up connection with Linux
Linux machines are normally the dial-up server as opposed to the client. Because a Linux box is so basic and stable, many people use Linux as a base for FTP servers, Gopher servers, Web
servers, and so on. If you’re interested in using your Linux box as a dial-up server, there are a lot of sites you can go to on the Internet, such as networking.earthweb.com or
www.linux.com.
As a dial-up client, your configuration varies according to your distribution. Configuration might be as simple as using the GNULinux PPP Configuration Utility or the Dial-Up
Configuration Tool found in the Task menu. The following instructions are general, because each distribution, each package, and installation of a distribution is different.
1. Add a modem and make sure it is properly connected. 2. Load PPP as a module and compile it to the kernel. Many Linux distributions already
have PPP compiled within the kernel; it depends on how you received the packages and which distribution you’re using.
3. You next must determine which COM port your modem is on. 4. Install the dial-up script. You’ll need to know the initial script for the modem you’re
calling, or you could use the default string, atdt.
5. Enter the phone number of the modem you’re calling, along with your username and
password, if required.
Appendix B ✦ IP Addressing
Troubleshooting TCPIP
TCPIP is difficult to configure if you don’t understand the way it works. You might find that your most difficult problems with the protocol involve misconfiguration problems. Luckily,
several TCPIP diagnostic utilities are available that you can use to diagnose problems and — with some effort and luck — maybe fix yourself.
The first thing you should do if you have trouble connecting to a computer is check the TCPIP configuration for that computer. Check the IP address, subnet mask, and any other
settings of all computers involved with the problem. If the configuration seems okay, the next step is to try some diagnostic utilities.
Using ping
The PING command sends TCPIP packets to the designated computer. If PING is successful, TCPIP sends the packets back. Use PING to verify that the TCPIP configuration is correct,
that local computers are communicating with each other, and that remote computers are communicating.
PING your own computer first to make sure you have configured the TCPIP correctly. If the PING doesn’t return packets, you need to check your own configuration.
If the PING is successful, it means the TCPIP stack is configured correctly on the local host, and your computer can reach others on the network. If you PING a remote network and the
PING is successful, the connection between the two computers is working, hosts and gate- ways between the two computers are working, and the TCPIP configuration on both comput-
ers is working.
You enter the PING command and then the computer name or IP address. Run PING from the MS-DOS prompt. To run PING, follow these steps:
1. In Windows 98, choose Start ➪ Programs ➪ MS-DOS Prompt. The MS-DOS window
appears on screen. In Windows XP or 2000, click Start ➪ Run, and type Command in the Open text box and
then click OK.
2. At the prompt, type ping, press the spacebar, and then type the name of the computer, as in this example: ping sue. Press Enter.
If the packets reach the destination, you see a response similar to the one in Figure B-27. Note that PING sends 32 bytes of data to the other computer. The replies indicate that 32 bytes of
data were returned. PING also indicates the time it takes the packets to travel the network. At the end of the replies, the command lists statistics, including the number of packets sent,
received, and lost, and the average time it took the packets to make a round trip.
If the PING was unsuccessful, the response might be that the host is unknown, the destination is unreachable, or the request timed out. This type of failure might indicate that your TCPIP
configuration is faulty, a name server is down, or your hardware — cable, network card, or hub — has a problem.
If the IP address of a remote computer PINGs successfully but the domain name doesn’t, it means a Domain Name Server is down.
Tip
Appendixes
Figure B-27: A successful PING gets a reply. If packets are lost or the PING is slow, check the network cabling on the system. A loose cable
could be the problem. If you PING your local host and all connections are working, but you still have trouble with a
remote host — another network segment, a WAN, or an Internet server, for example — try using the TRACEROUTE command. If you can reach only a local host, the remote host might have
problems. The problems also could be with a gateway or router connecting the two hosts.
TRACEROUTE, or TRACE, maps the specific path traveled to a destination, including routers, gateways, and computers.
Using IPCONFIG
IPCONFIG, a utility included with TCPIP, displays the IP address, subnet mask, and default gateway for all network adapter cards on your computer. IPCONFIG is handy for checking a
computer’s address quickly. It also can detect bad IP addresses or subnet masks. To use IPCONFIG, type the command at the MS-DOS prompt. Figure B-28 illustrates the infor-
mation from the IPCONFIG command. Note that the computer has two adapter cards, but only one is using the TCPIP protocol.
You can type IPCONFIG in lowercase or uppercase letters. MS-DOS doesn’t recognize case changes.
IPCONFIG also includes a parameter, all, that enables you to see more information about the computer. You type the following at the MS-DOS prompt:
ipconfig all
Using the all parameter displays the computer’s name, any DNS servers, the type of net- work node, and other information about the WINS server, NetBIOS resolution, and even the
MAC address of the adapter. Figure B-29 illustrates the results of the command.
Tip Tip
Appendix B ✦ IP Addressing
Figure B-28: List addressing information for a computer with IPCONFIG.
Figure B-29: Use a parameter to list more information about the computer.
Use the pipe | more command — ipconfig all |more — to display one screen of information at a time. Press the Enter key to read the next screen of information.
Using NETSTAT
NETSTAT network statistics is useful for tracking down network problems. Use NETSTAT to troubleshoot incoming or outgoing packet errors or to verify the presence of needed routes.
If you type netstat at the MS-DOS prompt, you see the protocol used, the name and local address of the computer, and any connected computers and their current state, as shown in
Figure B-30.
Tip
Appendixes
Figure B-30: Check network statistics. The NETSTAT command includes various parameters that display information about the net-
work connections. Table B-2 shows some of the commonly used parameters and their results.
Table B-2: NETSTAT Parameters
Type This Command Results
Netstat –a
Displays all connections and listening ports
Netstat –e
Displays Ethernet statistics
Netstat -n
Displays addresses and numbers in numerical format
Netstat -s
Displays the statistics of TCPIP protocols: TCP, UDP, and IP
Figure B-31 shows the results of the command using the -e parameter. The statistics list bytes sent and received, errors, and other details of the Ethernet statistics.
Figure B-31: View Ethernet statistics about your computer.
Appendix B ✦ IP Addressing
Using WINIPCFG
The WINIPCFG command yields the same results as the IPCONFIG command, but those results appear in a Windows dialog box instead of in the MS-DOS window. The WINIPCFG com-
mand includes several parameters. The most common is winipcfg all. Using the all parameter displays all of the information about your host and Ethernet adapter, including the
host name, DNS server used, node type, adapter name and MAC address, IP address, and so on.
To use WINIPCFG, follow these steps:
1. Choose Start ➪ Run. The Run dialog box appears. Click OK. 2. In the Open text box, type winipcfg all and then press the Enter key. The IP
Configuration dialog box appears. Click OK when you’re finished. The IP Configuration dialog box enables you to renew or release DHCP leases if you’re using
a DHCP server.
✦ ✦
✦
Note
Telecommuting
T
elecommuting is an excellent way of working at home or on the road while communicating with an office network to keep up-to-
date, exchange files, and print to the office printer, when necessary. You also can telecommute, or access remotely, other computers by
using a dial-up connection and a modem. Windows supplies the soft- ware you need to connect to remote computers. You can also pur-
chase software that enables you to remotely work on a computer. All you need is the modem and the connection.
Understanding Remote Access
Remote access refers to attaching to a network from another location and accessing resources from the remote computer. You might attach
to your work computer from home, for example, in order to access a program or a file; or you might attach to your son’s computer at col-
lege to copy a file or print your vacation schedule on his printer.
Many people work from home or bring their work home to complete. Using remote access, you can access files, programs, printers, and
any other resource on your work computer and other computers on the network for which you have permissions. You can also transfer
files between the remote computer and home or work.
Companies hire people to work from home part- or full-time then those workers use remote access to keep in touch with the office. By
allowing workers to telecommute, companies save on office space, insurance, and time less direct management, and spend less money
on remote workers than office workers. In addition, remote workers save commuting time, set their own schedules, and have better
morale than if they are stuck in an office all day.
Remote access also enables you to work from the road or another location. If you’re in another city, for example, but have a modem, a
phone line, and remote access, you can call your home computer or work computer to access your to-do list, your schedule, or any docu-
ment that you have saved. Naturally, the remote computer must be turned on and available for you to access it.
You can use remote access for home use or for work; many peo- ple, however, use it to attach to an office computer. This appendix
discusses several work situations, but you can apply any process, procedure, or information discussed to home use as well.
Note
C C
A P P E N D I X
✦ ✦
✦ ✦
Appendixes
Examining types of remote access
Remote access can mean any of several processes. You might use remote node access to attach to another computer or network, for file transfer, as a gateway, or for software-controlled
access. You probably will use remote node access or file transfer remote access. ✦
The most common method of remote access is when a computer connects to an office or corporate network. The remote computer user accesses any of the resources on the
office network and then works as if he or she were actually in the office, sharing pro- grams and files with coworkers.
The user can retrieve files, print on an office printer or local printer, log on to a server, get into shared calendars, and more. Remote access for the telecommuter sounds like a
dream come true. The user can take breaks, play with the dog, and generally set his or her own schedule — as long as the work gets done, of course.
Working via remote access has disadvantages, however. Applications and large files do not transmit well over a remote access connection, sometimes the cost is prohibitive,
and if the worker isn’t focused on his or her work, the work may not get done in a timely manner. However, for the right company and the right workers, telecommuting
can be the perfect arrangement.
✦ Another common method of remote access is file transfer. File transfer involves upload-
ing a file to or downloading a file from the remote computer. You might send a file con- taining family pictures, a budget spreadsheet, or a letter to a family member. More
likely, though, you will upload files to your work computer or download the informa- tion and research you need to complete a report.
✦ A gateway is a method of connecting to one computer to get to another. You might con-
nect to the server at work, for example, in order to get to your workstation there. ✦
Software-controlled access is when you are permitted to attach to only one program remotely, such as accounting software.
Understanding Dial-up networking
Dial-up networking is a Windows feature that enables you to use your modem to call the Internet, your company’s network, or some other remote network for the purpose of sharing
resources, exchanging e-mail, and other network-specific tasks. To use dial-up networking, you must install and configure it. Dial-up networking applies only
to the connection. After making the connection, you use another program, such as a Web browser, to communicate with the remote computer.
To use dial-up networking, both your computer and the remote computer must have a modem, the connection needs to be configured, and both computers must be turned on. You also need
to use the same protocol as the remote computer, such as TCPIP.
Appendix C ✦ Telecommuting
Distinguishing the remote access user
Remote users may be telecommuters, home office users, or employees traveling on the road or otherwise away from the office. Remote users may be home users who dial up home from col-
lege, the office, a hotel room, or another location. There are as many reasons to access a net- work from a remote location as there are types of users who must access a remote computer.
Users might want to check e-mail, copy a file, or print a document at home or at the office for others to see. Other reasons to access a network remotely might be for research, for techni-
cal support, or for an online meeting or conference. Remote access enables you to communi- cate with others over the network without being in the same room or office.
Other advantages of telecommuting and remote access are tremendous. Besides easing high- way congestion, lowering fuel usage, and saving wasted commuting time, remote access
users can complete a job more efficiently and set their own schedules as they do it. As a telecommuter, however, you must consider a few things. You want to make sure that you
have the equipment you need and that you’re using that equipment and the situation effi- ciently and considerately.
Using pcANYWHERE
Symantec sells a popular remote access program called pcANYWHERE for about 100. Using pcANYWHERE, you can access another PC remotely, and through the connection, you can access
a server or other remote node to transfer files or perform other network tasks. The other com- puter must also have pcANYWHERE installed and be turned on with pcANYWHERE running in
host mode.
pcANYWHERE uses a Windows interface. You call using the program, the program authenticates you, and then you can perform file transfers or other tasks with pcANYWHERE running in the
background. You can even train a remote computer user, troubleshoot problems on a remote computer, and perform programming tasks while connected to the remote computer. In short,
you can do anything on the remote computer that you could do if you were in the same room as the computer.
pcANYWHERE includes many remote management tools that enable you to troubleshoot prob- lems on the remote computer. You can edit the Registry, go to the command prompt, view logs,
and so on. pcANYWHERE is perfect for computer consultants and their clients and for corporate help desks.
pcANYWHERE is also very secure. The program uses Public Key Infrastructure PKI and symmet- ric encryption; it can use up to 13 authentication types, mandatory passwords, and integrity
checking. You’re safe when you’re online with pcANYWHERE. pcANYWHERE requires a minimum of 64MB of RAM, 35MB of free disk space, and a Pentium
processor, and it works with Windows 98, NT, 2000, and XP. For more information, see www.symantec.compcanywhere.
