I tried to ping my wireless router. it says destination not reachable but shows 0% loss. When i entered the ip address of my router it show address not valid. please let me know what to do.

Jus Powercycle the Whole N/w
Unplug Modem and Router
Plug Modem First and then Router
Check Wired Internet to Router if that Works, wireless will be Online

Check this tip out from Linksys. It is for a G VPN Router but you could use the same steps to troubleshoot. Title: Resolving Blinking Power or Diag LED on a Linksys Wireless-G VPN Router Article ID: 4982 If the Power LED on your Linksys router is blinking, this means the device is not ready. It should go off once the router completes its diagnostic test. If the Power LED won?t go off, it indicates that there?s a possible hardware problem with the router. To resolve this, you will need to perform five steps: Resetting the Router Assigning Static IP to the Computer Pinging the Router Accessing the Router?s Web-based Setup Page Updating the Router?s Firmware For instructions on how to reset the router, follow the steps below. Resetting the Router Hold in the RESET button at the back of the router for 30 seconds. Unplug the power to the router then plug it back in. If after resetting the router and the Power LED is still blinking, try resetting the router again for another 30 seconds. Then proceed with assigning a static IP address on the PC. For instructions, follow the steps below. Assigning a Static IP Address on Your Computer Most of the time, if the power LED on the router is blinking it loses its ability to assign IP addresses to the PCs connected to it, which is why you need to assign the computer a static IP address. After assigning a static IP address on the computer, check if the computer is still communicating to the router by performing a ping test. To ping the router, follow the steps below. Pinging the Router Ping test helps trace the communication between the computer and the router. The computer sends packets to the router and in return the router sends out replies to validate the connection. In this example, our router IP address is 192.168.1.1. NOTE: If you?re using Windows 98 or ME, click here. Windows 2000/XP Step 1: Click Start, then Run. Step 2: When the Run window opens, type ?cmd? in the Open field, then click OK. Step 3: When the MS DOS Prompt appears, type ?ping 192.168.1.1? and press [Enter]. Step 4: Check the ping statistics. You should get Packets: Sent =4, Received =4, Lost = 0 (0% loss). NOTE: If you?re not getting good replies from the router, it means the router is not communicating properly with the computer anymore. You can already consider the device defective. Windows 98/ME Step 1: Click Start, then Run. A window similar to Step 2 will appear. Step 2: When the Run window appears, type ?command? in the Open field, then click OK. Step 3: When the MS DOS Prompt appears, type ?ping 192.168.1.1? and press [Enter]. Step 4: Check the ping statistics. You should get Packets: Sent =4, Received =4, Lost = 0 (0% loss). NOTE: If you?re not getting good replies from the router, it means the router is not communicating properly with the computer anymore. You can already consider the device defective. If you get good responses from the router, access the router?s web-based setup page to see if a firmware update is possible. For instructions, follow the steps below. Accessing the Router?s Web-based Setup Page In order to perform a firmware update, you should be able to access the router?s web-based setup page. Updating the firmware is one way of resolving the blinking power light on the Linksys router. To access the router?s web-based setup page, click here. NOTE: If you?re having difficulties accessing the router?s web-based setup page, the router is considered defective. If you?re able to access the router?s web-based setup page, proceed in updating the firmware upgrade.

Check you internet provider is on your Router Wan Setup and select obtain IP address to identify internet relay are accessible.
If not reset your Router.
Good luck!

Hi Martin,
with all what you say, it looks like that your hardware is ok. That's a good start.
There are several possibilities what can be wrong: either your modem is not configured correctly, or some of the setting in your computer are not right.
Let's start with the computer:
1. open a command prompt (WindowsKey+R), type "cmd" and hit "Enter".
2. In the following window type "ipconfig /all" (there is a space before the "/").
3. Your output should look similar to mine:

Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.xxx
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Friday, August 07, 2009 17:32:33
Lease Expires . . . . . . . . . . : Saturday, August 08, 2009 17:32:33

Since the default IP address of your modem is 192.168.2.1, you IP address has to be in that range: 192.168.2.2-254.
If your IP address starts with 169.xxx.xxx.xxx or is 0.0.0.0, you have a connectivity problem. (Let me know and post your output here, if that's the case.)

Now type in that command prompt "ping 192.168.2.1" and hit "Enter" - replace the numbers with what you see under your Default Gateway.
My result looks like this:

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

This shows that you can connect to your modem. If you get a "Request timed out." reply, then your computer can not connect to your modem. Also, let me know if that's the case.

Now go back to the command prompt and type "ping www.google.com" and hit "Enter". My result looks like this:

Pinging www.l.google.com [74.125.65.99] with 32 bytes of data:

Reply from 74.125.65.99: bytes=32 time=87ms TTL=50
Reply from 74.125.65.99: bytes=32 time=85ms TTL=50
Reply from 74.125.65.99: bytes=32 time=87ms TTL=50
Reply from 74.125.65.99: bytes=32 time=87ms TTL=50

Ping statistics for 74.125.65.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 87ms, Average = 86ms

This shows two things:

1. You can get to the outside world
2. DNS is working properly

Now copy the IP address returned by this command (74.125.65.99 in my case) and copy it into the URL bar of your browser. If google shows up, then you have a DNS problem. What that means is that the translation from web addresses (www.google.com) to IP address (74.125.65.99) is not working. Go back and check you entry for DNS servers in ipconfig / all. Is that number identical to your Default Gateway?

How to set up DNS manually:

1. Click on start
2. Go to control panel
3. If your control panel is in classic view click on Network Connections
4. Right click on your Wireless network icon
5. Click Properties
6. Select Internet Protocol(TCP/IP)
7. Click on the Properties button
8. Now select the following option: "Use the following DNS server address"
9. Under "Preferred DNS server address" enter 208.67.222.222
10. Under "Alternate DNS address" enter 208.67.220.220
11. Click on OK until all windows are closed
    

Some points on your modem:

1. If you don't have a manual, you can get it here.
2. Make sure you have entered your user credentials for Bell (see page 11 in the manual)

Ok - sorry for the long post, but I tried to catch all culprits. If there is anything you don' t understand or it is still not working, let me know - I'm happy to help. If the outputs form the command prompt look very different from mine, copy them and post them here.

Easy way to do that? - Go back to your command prompt.

1. Type ipconfig /all > C: ixya.txt (hit ENTER)
2. Type ping 192.168.2.1 >> C: ixya.txt (hit ENTER)
3. Type ping www.google.com >> C: ixya.txt (hit ENTER)
4. Open My Computer, go to your C: drive and you will find a text file called fixya or fixya.txt, which contains all the information.
5. Come back here and paste the information in a comment.

Let me know if this was helpful and what you found out!

Dante

You must check if your PC is getting correct IP from your router by running ipconfig on DOS command. The Default Gateway must shows 192.168.1.1. Just to be sure this IP is accessible, run a ping test (Ping 198.168.1.1).

C:\Users\PC>ping 10.1.1.1

Pinging 10.1.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\PC>

You will see the above results if the test is successful. If it failed, possible a Firewall is blocking the PC to access the Router. Try to disable it and see if it will works. If the same issue or even the test passed but can't access the IP address, reset the router to factory defaults by pressing the small hole at the back of the router. Then do the above steps again to see if you can now access it. Hope this helps.

The wireless network (router) has a different IP address, than your 'hard-wired" connection, so the destinations will need to be re-programmed to match the new IP address of your server (or individual workstations), depending on how it was set up.

Have you check if you have a valid IP address? You could run IPconfig in the DOS window to verify this. If you have a valid IP address, try pinging the default gateway (You should be able to ping it.) Then, try to ping a website. If you could ping a website or URL but still can't browse check your firewall settings and optimize your browser.

Please post here what happen.

Thanks and regards,

BeHar

to confirm if your Network adapter's assigned IP, subnet, Gateway & DNS

• Start > Run > cmd
• at cmd prompt type: ipconfig /all
• look at the parameters given to your Network Device that is connected to the router (IP, Subnet, Gateway & DNS Servers.
• Verify those addresses if they are reachable by pingging. Check your IP, Gateway, then check for the DNS Addresses. Type cmd prompt: ping ip_address << do not omit the periods between the numbers.
• See if there are replies from those addresses. if you get Request timed out, tell us here which part you get one. if you can receive a reply from those addresses (gateway & DNS Servers) definitely you are already connected to the internet. Just check your Browser's connection setting.

I am guessing you are connecting that netgear card wirelessly? Does it get an IP address? Have you tried pinging the router from the laptop once the connection has been made? Try this. Go to the start menu, click the run button and in there type cmd and press enter. Once the black command prompt is open try ping yahoo.com See if that comes up with anything. Also try typing ipconfig and press enter. It will show 3 things.
IP address
subnet
gateway.

The gateway should be your 2wire modem.
Try ping gateway ip and see if that works.

Let me know! thank you.

Ping is one of the first tools to use to check computer, router and Internet connectivity. It's run at a command prompt, but getting the basic information is quite easy. You can do the whole thing in 30 seconds. 1. To run ping, type Start > Run. 2. Type cmd in the Run window, and click OK. A black and white command line window pops up. 3. Type ping followed by an IP address or a DNS address. 4. Press Enter to execute the command. Three useful examples: 1. ping 127.0.0.1 (This is a "loopback ping" ? your computer trying to talk to itself. This tests whether your computer is able to handle Ethernet traffic. If this has a negative result, the computer has an operating system problem.) 2. ping 192.168.1.1 (If the result is "Request timed out", type ping 192.168.0.1. If that also times out, then the computer is not making a connection to your router.) 3. ping www.netgear.com. (Tests whether your computer can contact Internet computers.) When there is no problem, the ping results look as shown in the following screenshot. Three items of interest in the results are highlighted with arrows. The first arrow shows the computer being contacted is replying. (The DNS address "www.netgear.com" is converted by ping into the equivalent IP address, 10.1.1.86.) This shows both that your network is connnected to the Internet, and that that computer on the Internet is running normally. www.netgear.com is always running, so this is a good test address to use. The second arrow shows that Ethernet packets have "0% loss". This is the best possible result. It means that the network connection is lightly loaded, and that it has not been necessary to transmit any of the same information twice. The third arrow shows the average time it took to answer. "Average = 0ms" is the best possible result. Probably you'll only get responses this quickly from computers on your own network. Interpreting Ping when There's a Problem As far as NETGEAR equipment, the problem you're most likely to run into is "Request Timed Out". This means there is no connection. Read these posts: http://www.fixya.com/ThreadView.aspx?prdid=252225&thid=102077 and http://www.fixya.com/ThreadView.aspx?prdid=252225&thid=102074 Another error is "Unknown host", which just means that the DNS or IP address you typed doesn't exist. Probably, you made a typo. Other problems are generally outside the scope of NETGEAR support. Often they are problems with your ISP ? contact them with concerns. A controversial situation is when packet loss is not 0%. Sometimes this indicates a severe problem, but in other situations it doesn't indicate any problem whatever. However anything higher than 5% is definitely a problem. If the average round trip time is > 500 ms, there' s possible latency problem. Again, contact your ISP. Limitations of the Ping Tool * Ping is not a good tool for diagnosing intermittent problems. * Good results are reliable, but ?bad results? could be caused by any number of things, and are not necessarily reliable! * Ping uses ICMP, which has low priority, showing speeds that are slower than regular network traffic. Some computers reject ICMP, and therefore pinging, entirely. * When an IP appears between the source and destination in a traceroute command it does *not* mean that that IP must be pingable.