Trouble connecting to just one website

(The $14.95 annually is a much nicer pricetag than the $239 Dell wants to leech from me – and look at the benefits!)

Okey-doke. I can connect to every single obscure corner of the Internet except – except! – the site I use the most often (of course), LiveJournal.com.

I have:

  • Rebooted
  • Tried connecting at several different times/days
  • Tried connecting with two different browsers (Firefox and IE)
  • Tried connecting from different computers (at libraries, labs, etc. – it works there)
  • Cleaned out my Temporary Internet Files folder
  • Beat my fists against the wall
  • Spent 30 minutes on hold while Dell Tech Support determined that they needed to charge me half of next month’s rent to solve the problem.

Does anyone have any more ideas or help? Or should I give up and pony up to Dell to fix (or try to fix) the problem?

Here’s a guess:

If you’ve cleared your cookies and you’re still having problems, the most likely next cause is that somehow there’s a *.livejournal.com entry in your HOSTS file. Some plugins edit the file.

You can manually edit your HOSTS file and check for this.

If you’re not sure how to do that, you can run the installer on this page, which will replace your HOSTS file with one that blocks most advertising.

If you don’t want to block ads, and you can’t find the HOSTS file, let us know what OS you’re running, and we’ll point you there.

You’re kidding, right? Hell, no – you ain’t no fool!

Are you on broadband or dialup?

I knew I could count on you guys. :slight_smile:

I ran the plugin you linked, and I still can’t access the page. I’m running Windows XP with a wireless broadband connection.

Huh. Ain’t a rogue HOSTS entry, ain’t a messed-up cookie (shoulda known that since it’s pan-browser.)

Uh… can you get through if you click here?

That’s a negative on both browsers.

And before I forget, thanks both excessive and effusive for your help! My computer knowledge is in the “fair to poor” range, and although I have a pretty good grip on terminology, I have no idea what to do with all the words. :slight_smile:

Can you try accessing the site through a proxy?

You can find a list here: http://nntime.com/

To set it up in firefox you’d go to tools->options->general->connection settings then fill in the http proxy field.

Yes! That works! THANK YOU!

Does this mean I have to go through a proxy server every time I want to access the site? Or is it indicative of the Actual Problem which can now be addressed?

No, you shouldn’t have to go through a proxy every time. This tells me that it is a problem with your computer(some program is blocking access, or your hosts file is) or your ISP.

Do you have access to another computer which you can try from your network?

Now that I think about it…did you reboot after running the hosts file utility? XP likes to cache entries in the hosts file (checks cache->host file->DNS server when trying to resolve a url) so if you didn’t reboot it may have still been using the old hosts file…

It’s definitely not the HOSTS file – the direct IP link didn’t work either.

Either something local is actively blocking LiveJournal’s IP – or LiveJournal is blocking Tracy Lord’s IP.

Do you have any firewall software installed? If not, maybe send an e-mail off to LiveJournal’s support folks, asking if your IP is on a blacklist? (You can get your IP address here: www.whatismyip.com )

It’s possible that your modem has inherited an IP address that previously belonged to a dickhead.

Otherwise, I got nuthin’, and someone with more geek points will be along shortly to figure it out. :smiley:

The dangers of posting at 4am…I’d go with your analysis over mine

Hmm… what do you get if you type “nslookup livejournal.com” from a command prompt? (that’s “START->run…->cmd”, brings up a black window that looks to all the world like a DOS prompt)

Most importantly, does the string “66.150.15.150” appear anywhere near the name “Livejournal.com”?

I’m thinking maybe there’s an upstream DNS resolution problem rather than one with your own “hosts” file… in which case you will need to talk to you ISP (rather than Dell) – but let’s see what you get, first.

… or, more likely, your computer has cached some invalid DNS translation for livejournal.com. :o
This is not necessarily overriden by rebooting – but should clear itself within hours or days (the Minimum TimeToLive for a client DNS Cache Record is 1 hour, but, IIRC, it could potentially “live” for as long as 72 hours under some circumstances).

You can manually “flush” the DNS cache on your computer by opening a Command Prompt (see my previous post) and typing “ipconfig /flushdns” at the prompt (in case this isn’t clear, don’t type in the quotes I have used to surround the text you should type!)

Try this and then see if you can connect directly (without using the proxy suggested by Nilor)

(BTW, haven’t seen you posting for a while; where have you been?)

Why don’t you just switch over to Firefox as a browser like a significant portion of the people here. That will probably take care of your problem. Note: It is free and you don’t have to get rid of Internet Explorer. You can have both.

I’m sorry. I didn’t read the line about using Firefox before. I will try to figure something else out.

I had an issue once similiar to this. The culprit was my wireless broadband router. Turns out, I just needed to unplug my router for a minute, and that fixed it. FWIW - it’s a LinkSys router.

Larry’s test with the IP address rules out DNS problems, since DNS isn’t consulted if an IP is given directly - as he says, it seems that some step in the route between Tracy and livejournal is failing, be it by accident or due to some sort of deliberate blocking.

Tracy, If you get a command prompt up (start … run … “cmd”) and run the following command:

c:> pathping 66.150.15.150

you should get a list of stages describing the route between your computer and livejournal - if you copy and paste the output here we might be able to see where things are going wrong. You might want to delete the first couple of lines, however, as your own IP address will show up, and is arguably personal information (if you’re bothered about that sort of thing).

True… sorry about that. Sloppy reading on my part.
'Though I suppose clearing out the DNS cache shoudn’t actually hurt anything…

The problem has been going on since Friday, FWIW – I didn’t have trouble connecting to LiveJournal before last week.

Okay, here’s the c/p results of Dead Badger’s test:

"Tracing route to livejournal.com [66.150.15.150] over a maximum of 30 hops:

0 James.pc.ashlandfiber.net [192.168.1.100]
1 10.40.1.1
2 afn-pr-2.ashlandfiber.net [66.241.65.226]
3 afn-border1-qwest.ashlandfiber.net [66.241.65.201]
4 afn-border2-noanet.ashlandfiber.net [66.241.65.202]
5 lsngw-huntercomm.lsnetworks.net [216.110.207.117]
6 * * *
Computing statistics for 150 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 James.pc.ashlandfiber.net [192.168.1.100]
0/100 = 0% |
1 11ms 1/100 = 1% 1/100 = 1% 10.40.1.1
0/100 = 0% |
2 10ms 0/100 = 0% 0/100 = 0% afn-pr-2.ashlandfiber.net [66.241.65.226]
0/100 = 0% |
3 16ms 0/100 = 0% 0/100 = 0% afn-border1-qwest.ashlandfiber.net [66.241.65.202]
0/100 = 0% |
4 12ms 0/100 = 0% 0/100 = 0% afn-border2-noanet.ashlandfiber.net [ 66.241.65.202]
0/100 = 0% |
5 15ms 0/100 = 0% 0/100 = 0% lsngw-huntercomm.lsnetworks.net [216.110.207.117]
100/100 = 100% |
6 — 100/100 = 100% 0/100 = 0% James [0.0.0.0]

Trace complete"

There’s some weird spacing stuff that got lost in the c/p, but can anyone make anything of that?

Humph. Unless someone with more networking experience has a better idea, I’d say that judging by the fact that things don’t seem to be getting past your ISP (or at least, your ISP’s bandwidth supplier), it seems most likely that for some bizarre reason, they are blocking LiveJournal. Not much more to advise, really, except to send their tech support an email (including the output you pasted here couldn’t hurt). Whatever it is, I’d say that at this point it’s certainly not a problem with your computer.

Sorry I can’t be more help… :frowning: