View Full Version : Can't access FWS =(
Erizo
June 20th, 2008, 14:00
Hi o.o
I can't access FWS normally, right now i'm on a proxy T_T Since yesterday at night i couldn't, is there something wrong? O.o
Dynash
June 20th, 2008, 14:23
Check it's not your net?
Erizo
June 20th, 2008, 14:25
Maybe, but this is the only site i visit, that i can't access now :S
AdamJ
June 20th, 2008, 14:32
Maybe your ISP has classed it as an over-used site and they've blocked it. Aparently some do actuley do that..
Dynash
June 20th, 2008, 14:44
Could be a AV? Modem problem? I've had a problem like this before, where I couldn't connect to nearly 8/10 websites without using a proxy.. It was my net settings on my PC, I had to reinstall my OS, after that it worked fine.
What error do you get? connection timed out? That's what I always got.
SC-Daniel
June 20th, 2008, 14:55
Try using OpenDNS instead of your ISPs DNS servers...
Comcast had a minor outage a couple weeks ago in my area, some sites would resolve and others wouldn't. I reported the problem numerous times and they kept denying the fact that it was a DNS issue with them. After I got fed up I switched over to OpenDNS and everything started functioning properly.
I thought maybe it was just my LAN or something, so I had a neighbor check and they were having the same problem.
Erizo
June 20th, 2008, 15:09
Maybe your ISP has classed it as an over-used site and they've blocked it. Aparently some do actuley do that..
I'm in Mexico, i hardly doubt my ISP has the knowledge to do that... :P
Could be a AV? Modem problem? I've had a problem like this before, where I couldn't connect to nearly 8/10 websites without using a proxy.. It was my net settings on my PC, I had to reinstall my OS, after that it worked fine.
What error do you get? connection timed out? That's what I always got.
The connection has timed out
The server at freewebspace.net is taking too long to respond.
And as i said, this is the only site i can't access.... :(
Dynash
June 20th, 2008, 15:10
Give it time, if it starts on other sites, then it is your computer settings.
sep
June 20th, 2008, 18:18
What is the exact error you're getting?
Cannot find server? Taking too long to load (timeout)? Connection was reset?
Dynash
June 20th, 2008, 18:21
He gets timed out. It's in the quote above my post.
Richard
June 20th, 2008, 18:48
Try and post the following to the FWS domain:
Tracert
Ping
Jan
June 20th, 2008, 19:36
Try connecting with the IP :) I used to periodically have that problem here.
Erizo
June 21st, 2008, 15:33
I cannot access with IP either, this is driving me crazy >.< It seems it may be my ISP, there are some other sites i can't access... :(
JonnyH
June 21st, 2008, 15:49
Restart your modem? Or like people suggested use OpenDNS?
Dynash
June 21st, 2008, 17:33
It's your computer. I've had this before. Fiddle with your settings, see what's causing it. When I got this sometime last year it was like 5 months long, it was driving me insane, then it settled and everything started working again. I had to do a OS reinstall once though, because it wouldn't go away.
Erizo
June 21st, 2008, 17:41
I don't think it would be my PC, as i didn't moved around the settings =( It just, from one day to the other, started failing... (Couldn't access FWS), and yesterday i was searching for ratdvd on google, and i couldn't open a lot of sites :S
Dynash
June 21st, 2008, 17:44
I never changed mine when it happend to me. Use another computer, I'm sure you will connect.
Darknight
June 21st, 2008, 23:46
Test in a different browser.
Erizo
June 22nd, 2008, 15:49
UPDATE: It seems it's my ISP.... because i was talking with some friends that also have the same ISP, and they all say some pages are unaccesible....
I would call their support line, if i wasn't so busy trying to recompile apache and PHP again >_<
SC-Daniel
June 22nd, 2008, 15:51
UPDATE: It seems it's my ISP.... because i was talking with some friends that also have the same ISP, and they all say some pages are unaccesible....
I would call their support line, if i wasn't so busy trying to recompile apache and PHP again >_<
Hmm, have you tried OpenDNS? I had the same issue and when I switched to OpenDNS all was fine ;)
Erizo
June 23rd, 2008, 03:54
I've tried OpenDNS as you suggested, but went worse xD Somehow i couldn't even open now more sites XD
Anyways, i gave up, i'm using a web proxy, lol. Called support a few hours ago, they put on a report...
Oh, well, just have to wait, i guess. The first time i could't access FWS i was like "zomg, fws is down? O.o" Then went ahead to host-tracker and it was up... So it was "my internets" :P
Dan
June 23rd, 2008, 08:54
Just turn your modem off for about 15 minutes, restart your PC and turn your modem back on when the PC is coming back up. This will flush your DNS and also should give you a new IP as well.
iBrightDev
June 23rd, 2008, 10:23
you could do a more simple way and just open the commend prompt and type in...
ipconfig /flushdns
;)
hamster
June 23rd, 2008, 10:25
you could do a more simple way and just open the commend prompt and type in...
ipconfig /flushdns
;)
Usually, that doesn't work for me.... dunno why... maybe it's because of my pathetic local ISP.
iBrightDev
June 23rd, 2008, 10:27
i normally release my ip first, but, flushdns should always flush it. :S
Erizo
June 23rd, 2008, 12:44
I had already flushed my DNS Settings and didn't worked.... But now it works.
After a little big chat with their technical support, i found out that it was due to an "automatic" firmware update from the modem (2wire), and that resetting the settings to fabric solves the problem, lol.
Dynash
June 23rd, 2008, 13:19
Isn't it:
ipconfig /release
ipconfig /renew
?
Erizo
June 23rd, 2008, 13:29
Yeah, it's ipconfig /renew
iBrightDev
June 23rd, 2008, 14:11
Isn't it:
ipconfig /release
ipconfig /renew
?
ipconfig /release (releases the IP)
ipconfig /renew (renews the IP)
ipconfig /release (flushes the dns)
[AS]Richard
June 23rd, 2008, 15:08
Probably something wrong with your firewall.
iBrightDev
June 23rd, 2008, 17:12
I had already flushed my DNS Settings and didn't worked.... But now it works.
After a little big chat with their technical support, i found out that it was due to an "automatic" firmware update from the modem (2wire), and that resetting the settings to fabric solves the problem, lol.
Probably something wrong with your firewall.
already resolved ;)
Powered by vBulletin® Version 4.1.7 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.