LunarFalcon Posted September 7, 2006 Share Posted September 7, 2006 Is anyone having problems accessing www.google.com today? I can't get into that site with firefox nor IE7. I also can't sign in to windows live messenger...weird...they all worked yesterday Link to comment Share on other sites More sharing options...
Lare2 Posted September 7, 2006 Share Posted September 7, 2006 Fine on my part, maybe something wrong on your part, any recent changes to your pc before that. Link to comment Share on other sites More sharing options...
LunarFalcon Posted September 7, 2006 Author Share Posted September 7, 2006 Nothing has been installed or changed on my PC in several days. Any ideas that I can troubleshoot? All other websites load fine, with the exception of mail.live.com... Link to comment Share on other sites More sharing options...
+BudMan MVC Posted September 7, 2006 MVC Share Posted September 7, 2006 can you resolve it? C:\>ping www.google.com Pinging www.l.google.com [72.14.203.99] with 32 bytes of data: Reply from 72.14.203.99: bytes=32 time=50ms TTL=243 Do you get an IP address? ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 604175 IN CNAME www.l.google.com. www.l.google.com. 3 IN A 72.14.253.104 www.l.google.com. 3 IN A 72.14.253.147 www.l.google.com. 3 IN A 72.14.253.99 Link to comment Share on other sites More sharing options...
LunarFalcon Posted September 7, 2006 Author Share Posted September 7, 2006 I tried to ping it, but got no response Link to comment Share on other sites More sharing options...
+BudMan MVC Posted September 7, 2006 MVC Share Posted September 7, 2006 did it RESOLVE.. did it return a IP.. or just give you unknow host? Which one did you get? C:\>ping sljdslfjsfsd.msdfjsldjfslfnsd Ping request could not find host sljdslfjsfsd.msdfjsldjfslfnsd. Please check the name and try again. or this C:\>ping www.google.com Pinging www.l.google.com [72.14.203.99] with 32 bytes of data: Link to comment Share on other sites More sharing options...
LunarFalcon Posted September 7, 2006 Author Share Posted September 7, 2006 I entered C:\ping www.google.com then got this: Pinging www.1.google.com [xx.xxx.xxx.xxx] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Link to comment Share on other sites More sharing options...
+BudMan MVC Posted September 7, 2006 MVC Share Posted September 7, 2006 (edited) it returned "xx.xxx.xxx.xxx" ?? I highly doubt that! Or do you think hiding the IP for google is a security thing?? That would be googles IP -- not your :rolleyes: What you don't want me to know googles IP? ;) Knowing what it returned will help us figure out what is going wrong.. here do a trace of where your getting the IP.. C:\>nslookup Default Server: dp2-400.local.lan Address: 192.168.1.2 > set debug > www.google.com Server: dp2-400.local.lan Address: 192.168.1.2 ------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.google.com.local.lan, type = A, class = IN AUTHORITY RECORDS: -> local.lan ttl = 38400 (10 hours 40 mins) primary name server = dp2-400.local.lan responsible mail addr = root.local.lan serial = 1126877464 refresh = 10800 (3 hours) retry = 3600 (1 hour) expire = 604800 (7 days) default TTL = 38400 (10 hours 40 mins) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 3, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 4, authority records = 6, additional = 0 QUESTIONS: www.google.com, type = A, class = IN ANSWERS: -> www.google.com canonical name = www.l.google.com ttl = 164042 (1 day 21 hours 34 mins 2 secs) -> www.l.google.com internet address = 64.233.167.147 ttl = 252 (4 mins 12 secs) -> www.l.google.com internet address = 64.233.167.99 ttl = 252 (4 mins 12 secs) -> www.l.google.com internet address = 64.233.167.104 ttl = 252 (4 mins 12 secs) AUTHORITY RECORDS: -> l.google.com nameserver = d.l.google.com ttl = 1662 (27 mins 42 secs) -> l.google.com nameserver = e.l.google.com ttl = 1662 (27 mins 42 secs) -> l.google.com nameserver = g.l.google.com ttl = 1662 (27 mins 42 secs) -> l.google.com nameserver = a.l.google.com ttl = 1662 (27 mins 42 secs) -> l.google.com nameserver = b.l.google.com ttl = 1662 (27 mins 42 secs) -> l.google.com nameserver = c.l.google.com ttl = 1662 (27 mins 42 secs) ------------ Non-authoritative answer: Name: www.l.google.com Addresses: 64.233.167.147, 64.233.167.99, 64.233.167.104 Its possible your getting an invalid IP for google.. if it returned xx.x.x. yeah that would be invalid! if you feel the IP is a invalid one - you could always check with one of their name servers directly.. nslookup server -- pick one from the above list then look it up. Try flushing your local cache ipconfig /flushdns Edited September 7, 2006 by BudMan Link to comment Share on other sites More sharing options...
LunarFalcon Posted September 7, 2006 Author Share Posted September 7, 2006 The 'x's were there because I didn't know if the numbers were relevant, thinking only that the fact that it timed out was the important part. I don't know a lot about networking so I didn't want to take any chances by entering the IP address - so thanks for picking on me! :devil: I ended up resetting my modem/router, and now everything seems to work fine. Thanks for all of your suggestions. (Y) Link to comment Share on other sites More sharing options...
+BudMan MVC Posted September 7, 2006 MVC Share Posted September 7, 2006 For future reference.. giving out the IP address of some website is not a issue, giving out your PRIVATE ip is fine as well.. ie 192.168.1.1, 10.1.1.3 etc.. when your behind a router. When asked if you resolve and IP.. yes the actual numbers can be important -- if your resolving to the wrong one, etc.. Glad its working for you. When your behind a router - normally you point to your router for dns.. it then caches entries.. When you reboot it - any cached info would of been lost, etc.. Knowing what IP you were getting - and where you were getting it from would of been helpful in figuring that out.. ie the set debug on nslookup. Link to comment Share on other sites More sharing options...
siddhs Posted September 8, 2006 Share Posted September 8, 2006 Just wondering why did that happen to you ! Do you use any caching sofware ? Did you check out your router logs ? Link to comment Share on other sites More sharing options...
+BudMan MVC Posted September 8, 2006 MVC Share Posted September 8, 2006 Just wondering why did that happen to you ! We will never know -- since troubleshooting to find out root cause, and maybe gaining some insight to how the stuff works, is too much work. It's much easier to reboot the magic boxes with the pretty blinking lights on them, cross your fingers and hope for the best. Link to comment Share on other sites More sharing options...
LunarFalcon Posted September 8, 2006 Author Share Posted September 8, 2006 We will never know -- since troubleshooting to find out root cause, and maybe gaining some insight to how the stuff works, is too much work. It's much easier to reboot the magic boxes with the pretty blinking lights on them, cross your fingers and hope for the best. Seriously ;) Link to comment Share on other sites More sharing options...
Recommended Posts