User's Manual
Table Of Contents
- Reference Manual for the Model CG814W Wireless Cable Modem Gateway
- Contents
- About This Manual
- Chapter 1 Introduction 1-1
- Chapter 2 Connecting the Gateway to the Internet 2-1
- Chapter 3 Wireless Configuration 3-1
- Chapter 4 Protecting Your Network 4-1
- Chapter 5 Managing Your Network 5-1
- Chapter 6 Troubleshooting 6-1
- Appendix A Technical Specifications A-1
- Appendix B Networks, Routing, and Firewall Basics B-1
- Appendix C Preparing Your Network C-1
- Glossary G-1
- About This Manual
- Chapter 1 Introduction
- Chapter 2 Connecting the Gateway to the Internet
- Chapter 3 Wireless Configuration
- Chapter 4 Protecting Your Network
- Chapter 5 Managing Your Network
- Chapter 6 Troubleshooting
- Appendix A Technical Specifications
- Appendix B Networks, Routing, and Firewall Basics
- Related Publications
- Basic Router Concepts
- Internet Security and Firewalls
- Wireless Networking Overview
- Authentication and WEP
- Wireless Channels
- Ethernet Cabling
- Appendix C Preparing Your Network
- Glossary
Reference Manual for the Model CG814W Wireless Cable Modem Gateway
Troubleshooting 6-5
ping 192.168.0.1
3. Click on OK.
You should see a message like this one:
Pinging <IP address> with 32 bytes of data
If the path is working, you see this message:
Reply from < IP address >: bytes=32 time=NN ms TTL=xxx
If the path is not working, you see this message:
Request timed out
If the path is not functioning correctly, you could have one of the following problems:
• Wrong physical connections
— Make sure the LAN port LED is on. If the LED is off, follow the instructions in
“Local Link LEDs Not On” on page 6-2.
— Check that the corresponding Link LEDs are on for your network interface card and
for the hub ports (if any) that are connected to your workstation and gateway.
• Wrong network configuration
— Verify that the Ethernet card driver software and TCP/IP software are both installed
and configured on your PC or workstation.
— Verify that the IP address for your gateway and your workstation are correct and that
the addresses are on the same subnet.
Testing the Path from Your PC to a Remote Device
After verifying that the LAN path works correctly, test the path from your PC to a remote device.
From the Windows run menu, type:
PING -n 10 <IP address>
where <IP address> is the IP address of a remote device such as your ISP’s DNS server.
If the path is functioning correctly, replies as in the previous section are displayed. If you do not
receive replies: