stud Posted April 9, 2008 Posted April 9, 2008 New box I'm setting up.. Connected to wifi (open) router in my home just fine. Established ip, I can ping the router but when I try to request any webpage (ex: google.com) it says "web site found, waiting for reply" a few times and just times out after that. I have 2 other computers on this router with no problems.. one is hardwired ethernet and another is wireless.I can ping the router with 3ms responses and after I've requested google.com I can run netstat -a and see an established connection to eh-in-faa.google.com I also tried going directly to 64.233.167.99 (google ip address) and same time out thing. Act's like it see's the other side but can't complete the connection for some odd reason.. what's up with this? Thanks for any advice!
stud Posted April 9, 2008 Author Posted April 9, 2008 Can you ping and/or tracert google.com?Yes, ping and tracert successfully to google.com
cluberti Posted April 9, 2008 Posted April 9, 2008 Hmmm. Hate to state the obvious, but I'd plug in directly to the internet source and try it to make sure it wasn't a browser/TCP stack issue. Assuming that works, it would seem as if packets outbound from you to the router (and the internet) are working, but they're dying on the way back. If other boxes work behind that router, it would stand to reason perhaps the router isn't sending the packets back to you in response to the ones you sent out (and it does seem it did set up a session with the web server for you, or you wouldn't get a "waiting for" and we know it resolves and you can tracert it)...
stud Posted April 9, 2008 Author Posted April 9, 2008 (edited) Hmmm. Hate to state the obvious, but I'd plug in directly to the internet source and try it to make sure it wasn't a browser/TCP stack issue. Assuming that works, it would seem as if packets outbound from you to the router (and the internet) are working, but they're dying on the way back. If other boxes work behind that router, it would stand to reason perhaps the router isn't sending the packets back to you in response to the ones you sent out (and it does seem it did set up a session with the web server for you, or you wouldn't get a "waiting for" and we know it resolves and you can tracert it)...I'm thinking it's this old wmp11 linksys card. Everything works fine when plugged in through a 3com 10/100 nic. Edited April 9, 2008 by stud
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now