I have a WRT54G router with 6 computers wireless pulling signal, all have good signal but internet is not displaying. I have checked all cables all is connected correctly and have reset the router and modem. Also have went into the router, and saved the correct settings for my ISP and still nothing. A webpage will come up, sometimes, but after a few minutes nothing.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Signal to router is good but not internet.
- Thread starter ggambill
- Start date
Have you verified if WEP is enabled? Sounds like you are not authenticating to your AP...
Thanks,
Matt Wray
GFH
Thanks,
Matt Wray
GFH
- Thread starter
- #3
Have you verified that you receive an IP address?
Can you ping Can you ping 216.109.118.71?
Can you ping the Access Point itself?
Thanks,
Matt Wray
GFH
Can you ping Can you ping 216.109.118.71?
Can you ping the Access Point itself?
Thanks,
Matt Wray
GFH
- Thread starter
- #6
Got to a command prompt, Start-> Run-> CMD.
Type ping and see if it replies or times out.
Try and ping 216.109.118.71 and see if it replies or times out.
Try and ping the Access Point itself.
Thanks,
Matt Wray
GFH
Type ping and see if it replies or times out.
Try and ping 216.109.118.71 and see if it replies or times out.
Try and ping the Access Point itself.
Thanks,
Matt Wray
GFH
If the router shows connected, the problem lies outside the router on the client side.
1. See my notes and the utilitiy recommended in this FAQ: faq779-4625
2. On the client, disable 802.1x authentication. Until you resolve the connectivity issue, disable WEP and/or WPA on both client and router.
3. If XP as client, be certain you have applied this rollup for wireless connections:
4. Do not disable SSID broadcast on the router until every other connection issue is resolved.
5. Change the SSID to something unique, and change the default channel to 1 or 11. Set the router to "Mixed" mode, even if using all B or all G devices.
6. See the firmware choices available from third parties from Wi-Fi Box and Seavsoft:
In any case, search with the keyword "WRT54G" and spend some time reading the responses.
7. You do not specify your broadband link. If using DSL, configure the router, and all clients to an appropriate MTU and RWIN value. The only sane way to do this is to test it. Use the BroadBandReports site, and the freeeware DRTCP to establish the valid values for the clients. The WRT54G on its setup page allows you to set a Manual MTU that is appropriate for your site:
Make sure you make the recommended changes at both router and client. For example, most DSL requires 1492, most cable systems the default 1500. But there are many exceptions to this.
1. See my notes and the utilitiy recommended in this FAQ: faq779-4625
2. On the client, disable 802.1x authentication. Until you resolve the connectivity issue, disable WEP and/or WPA on both client and router.
3. If XP as client, be certain you have applied this rollup for wireless connections:
4. Do not disable SSID broadcast on the router until every other connection issue is resolved.
5. Change the SSID to something unique, and change the default channel to 1 or 11. Set the router to "Mixed" mode, even if using all B or all G devices.
6. See the firmware choices available from third parties from Wi-Fi Box and Seavsoft:
In any case, search with the keyword "WRT54G" and spend some time reading the responses.
7. You do not specify your broadband link. If using DSL, configure the router, and all clients to an appropriate MTU and RWIN value. The only sane way to do this is to test it. Use the BroadBandReports site, and the freeeware DRTCP to establish the valid values for the clients. The WRT54G on its setup page allows you to set a Manual MTU that is appropriate for your site:
Make sure you make the recommended changes at both router and client. For example, most DSL requires 1492, most cable systems the default 1500. But there are many exceptions to this.
sounds like a weak signal from your isp? are you on a cable modem? if you can ping router with no packet loss then the next hop is the problemo. i have seen the ip on the isp side and still didnt have an upstream channel lock with the cable modem. called the cable modem isp and they jacked up the signal strength. also make sure if you are using any type of splitter that the it is rated for at least 1 ghz or better to ensure proper channel seperation.
There should be stated two possibilities:
. You have disabled the broadcast of SSID on the router. It is my opinion that disabling broadcast of the SSID is a very weak security step, and really makes Windows clients unhappy;
. Two, you may have a defective product. If all of the suggetions above to not resolve the issue, the likeliehood that you got a bum router increases substantially. Do a cross-ship replacement of the router using this link: You should have a replacement in 3 business days.
. You have disabled the broadcast of SSID on the router. It is my opinion that disabling broadcast of the SSID is a very weak security step, and really makes Windows clients unhappy;
. Two, you may have a defective product. If all of the suggetions above to not resolve the issue, the likeliehood that you got a bum router increases substantially. Do a cross-ship replacement of the router using this link: You should have a replacement in 3 business days.
Just curious - are you using the wireless router as the "main" router or is it connected to your network which has another router for the internet traffic?
For example: We have a Cisco 1700 Router + Sonic Wall Firewall (not recommended) that handles out internet traffic for our entire network. We have 9 laptop users that wanted to go wireless. So, like a dunce, I bought a Netgear wireless Router/switch. This has given me nothing but headaches - although I think I finally figured it out.
Our firewall (or main gateway) uses the IP of 192.168.0.1. The Wireless Router uses 192.168.0.3. So under Internet IP Address, the wireless router is given a static IP of 192.168.0.3, and the gateway IP address is 192.168.01. THe DNS is set to the IP of the DNS server on OUR netowork (not the ISP). Then under the LAN settings, the LAN TCP/IP Setup - the IP Address is 192.168.0.3.
The other trick was to set the wireless router as the DHCP for the wireless connections. I could not for the life of me get our main DHCP server to give IP's to the wireless connections...
For example: We have a Cisco 1700 Router + Sonic Wall Firewall (not recommended) that handles out internet traffic for our entire network. We have 9 laptop users that wanted to go wireless. So, like a dunce, I bought a Netgear wireless Router/switch. This has given me nothing but headaches - although I think I finally figured it out.
Our firewall (or main gateway) uses the IP of 192.168.0.1. The Wireless Router uses 192.168.0.3. So under Internet IP Address, the wireless router is given a static IP of 192.168.0.3, and the gateway IP address is 192.168.01. THe DNS is set to the IP of the DNS server on OUR netowork (not the ISP). Then under the LAN settings, the LAN TCP/IP Setup - the IP Address is 192.168.0.3.
The other trick was to set the wireless router as the DHCP for the wireless connections. I could not for the life of me get our main DHCP server to give IP's to the wireless connections...
- Status
Similar threads
- Locked
- Question