RedRocket1647545505 Posted July 13, 2008 Author Report Share Posted July 13, 2008 Tried some DNS stuff tonight. Well, what I could find on Google anyways. ipconfig /flushdns ipconfig /refreshdns A lot of people said this fixed their problem. It didn't fix mine. I also tried another possible fix I found, by designating 2 distinct DNS Servers instead of allowing the computer to find them itself. That didn't work either. Anymore suggestions? Quote Link to comment Share on other sites More sharing options...
Twistedrx7 Posted July 13, 2008 Report Share Posted July 13, 2008 Lather rinse and repeat? Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 13, 2008 Author Report Share Posted July 13, 2008 Lather rinse and repeat? Cut wrists and bleed? Quote Link to comment Share on other sites More sharing options...
s14steve Posted July 13, 2008 Report Share Posted July 13, 2008 well if you can get onto someone elses wireless network or for that matter just take your laptop to another place to get internet. That way you would know if its YOUR internet or you laptops problem for sure. Although you did say it was every computer in the house so... Does it immediately say the page cannot display or does it timeout Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 13, 2008 Author Report Share Posted July 13, 2008 well if you can get onto someone elses wireless network or for that matter just take your laptop to another place to get internet. That way you would know if its YOUR internet or you laptops problem for sure. Although you did say it was every computer in the house so... Does it immediately say the page cannot display or does it timeout That. Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 13, 2008 Author Report Share Posted July 13, 2008 hardlining didn't work Quote Link to comment Share on other sites More sharing options...
Akula Posted July 14, 2008 Report Share Posted July 14, 2008 tracert http://www.ohio-firearms.com where does the trace die? Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 14, 2008 Author Report Share Posted July 14, 2008 tracert www.ohio-firearms.com where does the trace die? Will check when I get home. Quote Link to comment Share on other sites More sharing options...
Hwilli1647545487 Posted July 14, 2008 Report Share Posted July 14, 2008 I'm not computer savy. Are you being serious, or Howard? It's like you've known me forever, but we have barely hung out . I noted that because you could be just timing out when attempting to access it. Where do you live again? Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 15, 2008 Author Report Share Posted July 15, 2008 Where do you live again? I guess my concern was that it's always worked before. It just recently decided it didn't want to work. Trashville. Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 15, 2008 Author Report Share Posted July 15, 2008 tracert www.ohio-firearms.com where does the trace die? Not sure what all of this means, but: Microsoft Windows [Version 6.0.6000] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Windows\system32>tracert www.ohio-firearms.com Tracing route to ohio-firearms.com [72.167.131.9] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 67-54-211-159.cust.wildblue.net [67.54.211.159] 2 2273 ms 1281 ms 1248 ms 10.25.128.1 3 1998 ms * 1777 ms 10.243.20.1 4 1274 ms 1272 ms 1320 ms 10.243.30.26 5 2599 ms 1163 ms 1183 ms 10.243.30.1 6 1251 ms 1274 ms 1190 ms 10.243.100.2 7 1372 ms 1247 ms 1365 ms 10.243.110.2 8 1255 ms 1509 ms 2803 ms 12.117.193.25 9 1347 ms 1454 ms 1485 ms tbr1.n54ny.ip.att.net [12.123.0.162] 10 1845 ms 1311 ms 1441 ms cr2.n54ny.ip.att.net [12.122.16.133] 11 1762 ms 1518 ms 1328 ms cr2.wswdc.ip.att.net [12.122.3.38] 12 1843 ms 1226 ms 1286 ms cr1.attga.ip.att.net [12.122.1.173] 13 1744 ms 1393 ms 1293 ms cr2.dlstx.ip.att.net [12.122.28.174] 14 1673 ms 1242 ms 1420 ms cr1.dlstx.ip.att.net [12.122.1.209] 15 1568 ms 1461 ms 1255 ms cr1.phmaz.ip.att.net [12.122.28.182] 16 1363 ms 1254 ms 1555 ms tbr1.phmaz.ip.att.net [12.122.22.130] 17 2885 ms 1457 ms 2736 ms 12.122.108.5 18 1321 ms 1261 ms 1371 ms 12.122.255.106 19 1503 ms 1275 ms 1342 ms mdf001c7613r0004-gig-12-1.phx1.attens.net [63.24 1.130.174] 20 1760 ms 1257 ms 1251 ms 63.241.142.126 21 2860 ms 1259 ms 1377 ms ip-208-109-112-178.ip.secureserver.net [208.109. 112.178] 22 1317 ms 1520 ms 1408 ms ip-208-109-112-149.ip.secureserver.net [208.109. 112.149] 23 1572 ms 1222 ms 2682 ms ip-216-69-188-45.ip.secureserver.net [216.69.188 .45] 24 * * * Request timed out. 25 1283 ms 1243 ms 1430 ms p3slh154.shr.phx3.secureserver.net [72.167.131.9 ] Trace complete. C:\Windows\system32> Quote Link to comment Share on other sites More sharing options...
Akula Posted July 15, 2008 Report Share Posted July 15, 2008 Not sure where this web host is located, looks like Phoenix. The ultra long response times you are experiencing coupled with the crazy routing to get to this host lead me to believe the webserver isn't allowing the connection. I guess the next thing you could try is type telnet http://www.ohio-firearms.com 80 <enter> get <enter> This should give you some response from the webserver. It looks like this site is hosted on an apache box. At this point if you get a response, I would believe it is latency related. Quote Link to comment Share on other sites More sharing options...
RedRocket1647545505 Posted July 15, 2008 Author Report Share Posted July 15, 2008 Not sure where this web host is located, looks like Phoenix. The ultra long response times you are experiencing coupled with the crazy routing to get to this host lead me to believe the webserver isn't allowing the connection. I guess the next thing you could try is type telnet www.ohio-firearms.com 80 <enter> get <enter> This should give you some response from the webserver. It looks like this site is hosted on an apache box. At this point if you get a response, I would believe it is latency related. Not sure what I did wrong?? Microsoft Windows [Version 6.0.6000] Copyright © 2006 Microsoft Corporation. All rights reserved. C:\Users\Austin>telnet www.ohio-firearms.com 80 'telnet' is not recognized as an internal or external command, operable program or batch file. C:\Users\Austin> Quote Link to comment Share on other sites More sharing options...
Akula Posted July 15, 2008 Report Share Posted July 15, 2008 this is windows xp, no? I just did this on an XP VM and it worked fine... my guess is still that it is your provider messing with you, either via latency or due to them blocking the site. set your dns to 198.6.1.2 Quote Link to comment Share on other sites More sharing options...
excell Posted July 15, 2008 Report Share Posted July 15, 2008 He's on Vista (Version 6.0.6000) and telnet is not installed by default. It's ridiculous, I know. Quote Link to comment Share on other sites More sharing options...
matris77 Posted July 15, 2008 Report Share Posted July 15, 2008 He's on Vista (Version 6.0.6000) and telnet is not installed by default. It's ridiculous, I know. That is ridiculous. I just read through the thread and I was going to have him try the telnet. Give us stats from "tracert www.ohio-firearms.com" and "tracert www.google.com". If you can access the site just fine from your laptop when you are at work the problem should lie with your home internet connection. Just to clarify when you use your laptop at work are you wired or wireless? Have you noticed any problems with any other sites from home? Quote Link to comment Share on other sites More sharing options...
Mrb00st Posted July 15, 2008 Report Share Posted July 15, 2008 have u tryed direct pluging the laptop into the router? try a firmware update on the router. Quote Link to comment Share on other sites More sharing options...
Mrb00st Posted July 15, 2008 Report Share Posted July 15, 2008 telnet is built into vista. just not installed. open run type pkgmgr /iu:TelnetClient done. telnet installed. FTW Quote Link to comment Share on other sites More sharing options...
excell Posted July 15, 2008 Report Share Posted July 15, 2008 telnet is built into vista. just not installed. open run type pkgmgr /iu:TelnetClient done. telnet installed. FTW Yes, but troubleshooting network or connectivity issues over the phone is a pain without basic tools loaded by default. Extra steps for the technician, extra typing and frustration for the customer, it's a no-win. Quote Link to comment Share on other sites More sharing options...
Mrb00st Posted July 16, 2008 Report Share Posted July 16, 2008 that my friend, is why i am no longer a computer tech Quote Link to comment Share on other sites More sharing options...
excell Posted July 16, 2008 Report Share Posted July 16, 2008 that my friend, is why i am no longer a computer tech Believe me, I know it. I still have a couple legacy clients that were good to my company in the "good old days" so while I don't do it much anymore, I still have to occasionally. Ah well, keeps me sharp. Quote Link to comment Share on other sites More sharing options...
87GT Posted July 16, 2008 Report Share Posted July 16, 2008 just download putty. it is better then telnet in dos Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.