.....where are you?.....

.....what cable provider?.....

.....little more info.....

Try the numerical URL so you don't have to go through the DNS lookup:

http://206.112.97.70/

Are you using 206.112.97.70?

Well CIB-173RDABN, seeing your Army I suggest that you turn off your cable modem and computer box them back up and return them, you really shouldn't use equipment that your not trained with. Silly soldier kicks are for trids < /grin >

It sounds like you are being filtered. Check with your ISP.

Try this for a quick fix.

go here : http://world.altavista.com/tr

Select spanish to english, and have the engine translate the website. You will have to surf FR through the frame but it might help. Because you pick spanish to english, and there is very little spanish, it should just leave everything in english.

When I hooked up to cable last Sept. I was able to access Free Republic readily through a search on GOOGLE. Silly me, I was unable to recall my login Password. A quick e-mail to Mr. Robison to reset it for me worked a like a snap.

Occasionally my cable provider can find http://www.freerepublic.com but not http://freerepublic.com -- and vice versa. Try both

(1) Go to a DOS prompt (assuming Windows!) and type:

ping 206.112.97.70

This command should respond with several lines each describing how long the answer took. If it does that, then proceed to step (2).

Otherwise, are you able to get to other web pages? Apparently, someone has blocked the IP address!

(2) Assuming you can ping the numeric address. Type:

ping www.freerepublic.com

This should respond the same way as the prior numeric ping.

If it does, then proceed to step (3).

Assuming the prior ping did not work, but you are able to get to other web pages, then examine the files on your system named /windows/hosts and /windows/lmhosts

Neither one of these files should have lines which refer to freerepublic [unless they have 206.112.97.70 as an IP address]. Some people added address assists when there were DNS problems in the web, but they should be deleted as soon as they are not necessary in case FreeRepublic changes IP addresses.

If you had no such lines in either file, then someone is blocking freerepublic by name. Ask your ISP to perform a traceroute to try to find the offending DNS server. In the meantime, you should be able to get around the problem by adding:

206.112.97.70 www.freerepublic.com #PRE

to your hosts and lmhosts files. Actually, only one is required, but I can't remember which and it won't hurt to do both.

(3) Make sure that you are trying to connect to the URL:

www.freerepublic.com

It the hosts file.

JABit,

Thank you.

I should have added that you should boot after you change the hosts file. You could actually use the nbtstat command, but I think it might be easier to boot.

nbtstat -R --- will reload DNS cache from hosts file

nbtstat -c --- will show current cache file content (it should show new entry for freerepublic)

When I first started at my previous emplyer I thought they were blocking FR also.

An MIS guy told me that they didn't blaoc any sites, and anytime I had a problem just to put a slash / at the end of the address I was trying to reach.

It worked like a charm and I never had a problem again.

Try it:

http://www.freerepublic.com/

Cyberax

California (central valley)

Charter.net

balrog666

Tried the number (without www), just says that the page cannot be displayed

all your cable modems are belonging to us.

SERE_DOC

As long as I keep the computers out of the mud they seem to work ok :-}

VannroxChecked with them, they say they are not filtering anything.

Spent almost an hour with their tech.

I think you guys here on free republic know more.

woofer

When everyone was having problems I also found by going to google I could get in, but it does not work this time.

If you have Excite @ Home, you might have BIG problems tomorrow.