My lan/modem card wont give

Jan 21, 2009

1. start the troubleshooting process by making sure that everything (routers, switches, hubs, modems, and computers) is firmly plugged in.
2. If your computer is on and the other end of the Ethernet cable is connected to a network device, the link or activity LED should light. If the light remains dark after you plug in the cable, replace the cable. If replacing the cable gives the same result (no green light), then go to the next step.
   
3. Once you’ve eliminated cabling as a source of the problem, it’s time to look to your computer. Start by making sure that your computer is able to access your Ethernet card. A good tool for doing this, and subsequent network troubleshooting, is the command prompt.
4. Select Start, All Programs, Accessories, and then Command Prompt. When the Command Prompt window opens, type ipconfig –all and press ENTER. Various lines of information will display, depending on how your system is configured. Look for a section labeled Ethernet Adapter Local Area Connection. This section should include a line labeled Description, which should be a description of your Ethernet card. If you see it, then your computer knows about your Ethernet card and has successfully loaded the necessary drivers. If the Description line is blank or missing, you will need to reinstall the drivers for your Ethernet card.
5. Your Ethernet card doesn’t detect a connection to the Ethernet cable. Open a command prompt, type ipconfig –all, and press ENTER. If the section that starts with Ethernet adapter Local Area Connection contains a line labeled Media, with a status of Media Disconnected, then your computer is unable to detect that a link has been made from your Ethernet card through the Ethernet cable to another network device, such as your computer or router. Recheck the cabling. Use a known good cable to connect your computer to a known good network device and then perform the check again. If the status is still Media Disconnected, and you are sure that the cable and the network device the cable connects to are good, then you may have a bad Ethernet card. Reinstall the Ethernet card. If the problem continues, you may need to replace the card.
6. Other things to check:
7. Bad connection, bad cable, or wrong cable. The ports on a router, hub, switch, wireless access point, and print server can, like any other device, go bad. However, the most common problem is not a bad port but a bad or loose connection, a bad Ethernet cable, or the wrong type of cable. Refer to the Cabling section above, to eliminate these possibilities.
8. Wrong port. One possible cause of Ethernet port problems is using the wrong port on a network device. For example, routers have WAN (wide-area network) and LAN ports. These ports accept the same Ethernet cabling but are not interchangeable. The same is true of hubs and switches that have uplink ports, which are specially wired LAN ports that allow easy cascading of multiple hubs and switches. In some cases, the uplink port is also a normal LAN port controlled by a switch on the device. If you’re using the uplink port as a normal LAN port, make sure the device is configured properly for this type of use.
   
   If a port doesn’t appear to be working, you can use the link light to confirm it. Port link lights should always be lit when a good cable is connected between the port and another working network device. If you use known good cable and a known good network device to test the port but the link light isn’t lit, you may have a bad port. You can either replace the network device, or in the case of a hub/switch, add a hub or switch to gain more LAN ports.
9. You cannot connect to other computers or router/Internet. When other computers in your LAN can connect to each other, as well as to the Internet or other services, and your computer cannot, this may be an indication that your computer did not receive an IP (Internet Protocol) assignment when you booted.
   
10. Open a command prompt, type ipconfig –all, and press ENTER. In the section labeled Ethernet adapter Local Area Connection, look for the line labeled IP. If it starts with 169, you have a self-assigned IP, which indicates that your computer was not able to acquire an IP assignment from the DHCP (Dynamic Host Configuration Protocol) server.
    
    Test your access to the DHCP server by using the ping command. Open a command prompt and type ping followed by the IP address of the DHCP server. Your DHCP server is probably the same as your router. For example, if your router’s IP is 192.168.1.1, then type ping 192.168.1.1 and press ENTER. You should see four lines of text, starting with Reply From 192.168.1.1: Bytes 32, followed by time values that indicate how much time elapsed between the ping command and the router’s response. If you see four lines that say Request Timed Out, then your computer cannot reach your router/DHCP server.
    
    Make sure the router is plugged in, turned on, and properly configured to provide DHCP services.