Jump to content

Problems Gettting To Hf


Recommended Posts

I had that problem a while back, then one of my mac-using friends sent me a virus (noobs... haha) and I restored. Works fine now.

Not really sure what it is that did it, I cleared all my cookies, defragged, re-installed my browser/network drivers... couldn't figure a thing.
Link to comment
Share on other sites

I've checked, you're not IP banned or restricted in any way from our end.

As stupid as it sounds, clearing cookies DOES actually help with log in and oter issues. Let me know if you still cant get in after clearing them.

Sorry about the problems.
Link to comment
Share on other sites

QUOTE (mushrat @ Nov 9 2008, 12:06 PM) <{POST_SNAPBACK}>
I've checked, you're not IP banned or restricted in any way from our end.

As stupid as it sounds, clearing cookies DOES actually help with log in and oter issues. Let me know if you still cant get in after clearing them.

Sorry about the problems.



Dont worry about the problems. I cleared all the cookies and still no luck. I get a network timeout error. I don't get it.
Link to comment
Share on other sites

My brother had the same problem with a Pink Floyd forum... I'm pretty literate when it comes to computers, and I couldn't figure it out for the life of me.

Try downloading Google Chrome (browser) and see if it works on that.
Link to comment
Share on other sites

I'm (still) experiencing the same problem from my home network (any computer on my home network, not just my own computer). I have Comcast Cable. Here's a topic I posted a little while back on the same issue: http://www.hookahforum.com/?showtopic=24078#entry285748

After posting that, I called Comcast technical support, and a very helpful lady (who, most importantly, didn't try to spoon feed me with the normal "restart your computer" crap) told me that she sees nothing on Comcast's end that could be causing the problem. She was able to access HookahForum from their offices with no problem.

It's not a DNS issue, since I can ping www.hookahforum.com and receive an IP address and a response. The only thing I can think of is that it's some random glitch with our specific instance of the cable internet service...

For now, I've just been getting around the problem from home either by VPN'ing into my work computer or by using a proxy like http://ninjaproxy.com . I'd prefer not to have to use workarounds to access this site, but it's the best I can do for now.
Link to comment
Share on other sites

QUOTE (peterjmag @ Nov 11 2008, 12:59 AM) <{POST_SNAPBACK}>
I'm (still) experiencing the same problem from my home network (any computer on my home network, not just my own computer). I have Comcast Cable. Here's a topic I posted a little while back on the same issue: http://www.hookahforum.com/?showtopic=24078#entry285748

After posting that, I called Comcast technical support, and a very helpful lady (who, most importantly, didn't try to spoon feed me with the normal "restart your computer" crap) told me that she sees nothing on Comcast's end that could be causing the problem. She was able to access HookahForum from their offices with no problem.

It's not a DNS issue, since I can ping www.hookahforum.com and receive an IP address and a response. The only thing I can think of is that it's some random glitch with our specific instance of the cable internet service...

For now, I've just been getting around the problem from home either by VPN'ing into my work computer or by using a proxy like http://ninjaproxy.com . I'd prefer not to have to use workarounds to access this site, but it's the best I can do for now.


dns and routing are different.
Link to comment
Share on other sites

QUOTE (chinamon @ Nov 10 2008, 06:01 PM) <{POST_SNAPBACK}>
QUOTE (peterjmag @ Nov 11 2008, 12:59 AM) <{POST_SNAPBACK}>
I'm (still) experiencing the same problem from my home network (any computer on my home network, not just my own computer). I have Comcast Cable. Here's a topic I posted a little while back on the same issue: http://www.hookahforum.com/?showtopic=24078#entry285748

After posting that, I called Comcast technical support, and a very helpful lady (who, most importantly, didn't try to spoon feed me with the normal "restart your computer" crap) told me that she sees nothing on Comcast's end that could be causing the problem. She was able to access HookahForum from their offices with no problem.

It's not a DNS issue, since I can ping www.hookahforum.com and receive an IP address and a response. The only thing I can think of is that it's some random glitch with our specific instance of the cable internet service...

For now, I've just been getting around the problem from home either by VPN'ing into my work computer or by using a proxy like http://ninjaproxy.com . I'd prefer not to have to use workarounds to access this site, but it's the best I can do for now.


dns and routing are different.


I know, my reply wasn't a direct response to yours. I'll post the tracert results from my home computer in a moment.
Link to comment
Share on other sites

CODE
C:\Windows\system32>tracert www.hookahforum.com

Tracing route to hookahforum.com [74.55.183.23]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms    14 ms    20 ms  ge-2-2-ur01.fortcollins.co.denver.comcast.net [68.86.105.201]
  4    11 ms    10 ms    14 ms  te-9-3-ur02.longmont.co.denver.comcast.net [68.86.103.157]
  5    25 ms    16 ms    27 ms  te-9-1-ur01.longmont.co.denver.comcast.net [68.86.103.161]
  6    12 ms    10 ms    29 ms  te-3-1-ar01.denver.co.denver.comcast.net [68.86.103.154]
  7    14 ms    13 ms    16 ms  68.86.91.201
  8    13 ms    13 ms    15 ms  pos-0-10-0-0-cr01.denver.co.ibone.comcast.net [68.86.86.22]
  9    31 ms    27 ms    27 ms  pos-0-6-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.174]
10    30 ms    32 ms    30 ms  68.86.88.50
11    45 ms    33 ms    54 ms  et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]

12    35 ms    32 ms    33 ms  et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]
13    34 ms    37 ms    35 ms  po1.car04.hstntx1.theplanet.com [207.218.223.14]

14    37 ms    32 ms    37 ms  17.b7.374a.static.theplanet.com [74.55.183.23]

Trace complete.
Link to comment
Share on other sites

Sorry for the triple post, but I can't edit my previous post anymore...

Here's my routing table from my WRT54G:

CODE
Destination LAN IP          Subnet Mask          Gateway          Interface
0.0.0.0                 255.255.255.0         71.56.234.32    WAN (Internet)
0.0.0.0                 0.0.0.0                71.56.234.1     WAN (Internet)
71.56.234.0             255.255.254.0         71.56.234.32    WAN (Internet)
192.168.1.0                    255.255.255.0         192.168.1.1     LAN & Wireless
Edited by peterjmag
Link to comment
Share on other sites

QUOTE (peterjmag @ Nov 11 2008, 12:07 AM) <{POST_SNAPBACK}>
CODE
C:\Windows\system32>tracert www.hookahforum.com

Tracing route to hookahforum.com [74.55.183.23]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms    14 ms    20 ms  ge-2-2-ur01.fortcollins.co.denver.comcast.net [68.86.105.201]
  4    11 ms    10 ms    14 ms  te-9-3-ur02.longmont.co.denver.comcast.net [68.86.103.157]
  5    25 ms    16 ms    27 ms  te-9-1-ur01.longmont.co.denver.comcast.net [68.86.103.161]
  6    12 ms    10 ms    29 ms  te-3-1-ar01.denver.co.denver.comcast.net [68.86.103.154]
  7    14 ms    13 ms    16 ms  68.86.91.201
  8    13 ms    13 ms    15 ms  pos-0-10-0-0-cr01.denver.co.ibone.comcast.net [68.86.86.22]
  9    31 ms    27 ms    27 ms  pos-0-6-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.174]
10    30 ms    32 ms    30 ms  68.86.88.50
11    45 ms    33 ms    54 ms  et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]

12    35 ms    32 ms    33 ms  et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]
13    34 ms    37 ms    35 ms  po1.car04.hstntx1.theplanet.com [207.218.223.14]

14    37 ms    32 ms    37 ms  17.b7.374a.static.theplanet.com [74.55.183.23]

Trace complete.


problem at hop 2... thats probably at comcast's router.
Link to comment
Share on other sites

here is my traceroute...

CODE
Tracing route to hookahforum.com [74.55.183.23]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     8 ms    11 ms  10.21.208.1
  3     8 ms     5 ms     6 ms  69.63.242.37
  4     5 ms     8 ms    17 ms  dgw02.mtnk-ten/0/15/1/0.mtnk.rogers.com [69.63.2
48.10]
  5     8 ms     7 ms     7 ms  gw02.wlfdle-ge7/1/2.mtnk.rogers.com [69.63.248.5
]
  6    23 ms    25 ms    23 ms  64.71.241.110
  7    23 ms    33 ms    23 ms  eqix.asbn.twtelecom.net [206.223.115.36]
  8    53 ms    53 ms    53 ms  hagg-03-ge-1-0-0-538.hsto.twtelecom.net [66.192.
246.210]
  9    54 ms    55 ms    54 ms  et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153
]
10    54 ms    53 ms    54 ms  po1.car04.hstntx1.theplanet.com [207.218.223.14]

11    64 ms    62 ms    63 ms  17.b7.374a.static.theplanet.com [74.55.183.23]

Trace complete.
Link to comment
Share on other sites

QUOTE (peterjmag @ Nov 11 2008, 12:20 AM) <{POST_SNAPBACK}>
QUOTE (chinamon @ Nov 10 2008, 06:18 PM) <{POST_SNAPBACK}>
problem at hop 2... thats probably at comcast's router.


Yeah, that makes sense... Is there any accessible admin interface for those crappy cable modems that they lend you?


i dont think so.
only comcast techs can fix that. their router is usually outside on the street somewhere.
Link to comment
Share on other sites

QUOTE (chinamon @ Nov 10 2008, 06:21 PM) <{POST_SNAPBACK}>
QUOTE (peterjmag @ Nov 11 2008, 12:20 AM) <{POST_SNAPBACK}>
QUOTE (chinamon @ Nov 10 2008, 06:18 PM) <{POST_SNAPBACK}>
problem at hop 2... thats probably at comcast's router.


Yeah, that makes sense... Is there any accessible admin interface for those crappy cable modems that they lend you?


i dont think so.
only comcast techs can fix that. their router is usually outside on the street somewhere.


Something makes me think they wouldn't be thrilled to try and fix something like that... Heh. I'll give them a call and see what can be done though. Edited by peterjmag
Link to comment
Share on other sites

You cleared the cache and cookies? Ok this happens at my BF's house, you need to call comcast and ask them to 'clear the lines'. What happens (aparently) is that sometimes their routers/lines get a sort of 'stray information buildup' and it causes internet problems.

Also restart the router. I get it ever so often on mine (dialup), but it usualy ends with me beating the router against a table until internet works again.
Link to comment
Share on other sites

QUOTE (Bulldog_916 @ Nov 10 2008, 09:44 PM) <{POST_SNAPBACK}>
Have you tried clearing your IP stack and reloading it?

ipconfig /release

ipconfig /renew

That generally works for most problems that arent related to comcast's service issues.


Yeah try that. Do this in cmd:

ipconfig /release

ipconfig /flushdns

ipconfig /renew
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...