Http Timeout

[Trekky]

Hi, i thought i would make this post a little more formal than incorporating it into someone elses problem :rolleyes:

I have tryed to get a http server going on Fedora Core 3 and it seems to be working perfectly fine. But the problem is it's not accessable from outside my lan.
I can access it by putting in the lan ip. But my mate cant access it.

He gets a Timeout error.

I have used no-ip.com for the DNS url. And put in my IP.
The URL to get to my site is http://xcell.sytes.net

Now if you click that you will find that you will get a timeout error.

My problem is, My mate and I have done everything we can think off. and still we get the timeout error.

If anyone knows of this issue or may have a valid opinion please post, even if it's small.
It is possible we have overlooked something.

Thankyou

[raghavendra]

Hi
Check with your service provider........Yours may not be a publically visible ip
Just go to
www.whatismyip.com
get your ip
and let your pal try that ip in the browser
http://yourip/

Edit: The internet service provider might have also blocked your incoming 80 port

[AndyGreen]

system-config-securitylevel

click the http box

You might also need to set your gateway router to forward accesses to your public IP port 80 to your machine's internal IP port 80.

[Trekky]

Hmm.. i'll try them, i'll let you know what happens

[Trekky]

Hmm.. i'll try them, i'll let you know what happens

Yea. i knew about the security level bit, i'm just pondering about the port forwarding, because what i can remember it should be forwarded but i'll recheck.

[Trekky]

Ok what you suggested i checked and made no difference unfortunately. I still haven't found out about that port 80 block from my ISP, but i'm with iinet so i dont know whether anyone would happen to know that answer.

so yea.. i'm still getting timeout errors :/

[AndyGreen]

Well it did make a difference... with that box unchecked it was never going to work, now you are one step closer.

What exactly have you done on your router to perform the port forwarding action?

[lindamus]

iinet australia does block incomming ports (not all, but the most common types)

[Trekky]

Well it did make a difference... with that box unchecked it was never going to work, now you are one step closer.

What exactly have you done on your router to perform the port forwarding action?


Umm.. the box was checked before i went and rechecked btw just to let everyone know, sorry it's kinda late.

Um.. just to be sure that it's not a blocked 80, i forwarded that to the Linux IP. And i am aware no-one has successfully got to the server yet.

[AndyGreen]

Lol... okay, I accept in that case it truly made no difference.

What exactly have you done on your router to perform the port forwarding action? Because if that ain't right nobody will get to your server either.

[Trekky]

Lol... okay, I accept in that case it truly made no difference.

What exactly have you done on your router to perform the port forwarding action? Because if that ain't right nobody will get to your server either.


Ok.. well considering my Modem/Router is very wierd to me (Netgear DG834G)

And i'm not a wizz at forwarding.

I forwarded port 80 (HTTP service) for inbound services to go to my linux Box (Have i done that right?)

[AndyGreen]

Maybe... it should have some kind of "port forwarding" display that is on the one hand asking

Internet Side

Protocol: UDP | TCP
Port: _____


Network Side

Destination IP: ___.___.___.___
Port: _____


So we want Internet accesses to TCP port 80 to be forwarded to your Linux Box's internal IP also port 80.

[AndyGreen]

Hey, here's a good idea.

Add another port forwarding mapping from TCP port 81 on the Internet side to you Linux Box's Internal network IP port 80

Then try to access your webserver on http://your-external-ip:81

That will do an end run around any port 80 blocking that might exist.

[Trekky]

Yes that does sound like it. And i think i have done it correctly if thats what you say.
i'll have anothing look

[Trekky]

Hey, here's a good idea.

Add another port forwarding mapping from TCP port 81 on the Internet side to you Linux Box's Internal network IP port 80

Then try to access your webserver on http://your-external-ip:81

That will do an end run around any port 80 blocking that might exist.


Woh brain wave.. ok i'll give it a shot

[AndyGreen]

Another good idea: if you have a second box on your network, point a browser on it to http://your-linux-box-internal-ip/ and see if you get your content or not. That will establish that your box is willing to serve to external clients.

[Trekky]

sorry for my lack of knowledge here but external-ip being my ip address... right?

[Trekky]

Another good idea: if you have a second box on your network, point a browser on it to http://your-linux-box-internal-ip/ and see if you get your content or not. That will establish that your box is willing to serve to external clients.


Yea thats the thing.. i can reach the linux server through LAN via ip address, but it's not accessable from the net (i.e. http://xcell.sytes.net )

[AndyGreen]

I mean like

http://xcell.sytes.net:81

[Trekky]

I mean like

http://xcell.sytes.net:81


Well it says connection refused

Could it do something with no-ip.com?

Because the no-ip DNS url is linked to my IP, so it's should be redirecting to the linux server, shouldn't it?

[AndyGreen]

xcell.sytes.net is resolving to 203-59-13-233.dyn.iinet.net.au right now. Maybe you can check if your router also believes that is its current IP.

[Trekky]

xcell.sytes.net is resolving to 203-59-13-233.dyn.iinet.net.au right now. Maybe you can check if your router also believes that is its current IP.

Possibly reset the modem? so that it gets a new ip, No-ip will automatically change IP because it Dynamic.

I'll check the modem out.

[Trekky]

Yea router is saying the right IP, so i'm still lost. Sounds like i'm gonna need to reinstall Fedora. And then Restart all over again.

[Trekky]

I was told to see if i could use Telnet to get to the server using my IP using Port 80, i'm not sure how that solves my problem, does this mean if it works, that my router is forwarding Port 80 towards the Linux server?

[raghavendra]

Hi
I would like to make this point
Forget about the no-ip account for a moment
Just your publically visible ip
Go to www.whatismyip.com
Get your ip address
Now configure Apache to listen to a port other than 80 say x....This step is important.
Now in your browser give
http://yourip:x/
Lets see if this works.

[Trekky]

Ok.. i did that, Configured it to listen to all addresses on Port 90
How am i sposed to see if this works without someone else outside my lan, it will just direct me to my Router wont it?

[raghavendra]

Hi
Yes if your router is configured even though I dont have much idea about it.
You can ask anybody outside your LAN to just give it a try, maybe you can post your publically visible ip here and anyone one of us can try out here :)

[Trekky]

Thats a security risk aint it :P

[raghavendra]

Hi
Yes it might lead to security issues.
But since yours is not a static ip your publically visible ip keeps changing everytime you log-on
So maybe it would be difficult to break the security issues.............But the last word can only be from an experienced Hacker:)

[Trekky]

I found something.. when setting it up, it says the host name is xcell.mshome

That doesn't sound right to me... like it's fedora yet it's host name has MShome on the end.. WTF
Could that have anything to do with it?

[raghavendra]

Hi
I dont think there is any problem with it.
Though we have to wait for others in the forum to confirm it.

[Trekky]

well the ip is directing my computer to the router as per usuall. Just waiting for someone on MSN to tell me if the site isn't timing out. God this has been alot a trouble just for a http server. I can only imagine the questions when i get to mysql

hehe

[Trekky]

Ok i got someone to check it and again it timed out "Grr"

I seriously dont know what to do.. I could just Screw around in settings and stuff. But i know if i'm diving deeper into crappola.

[raghavendra]

Hi
I think there are two things:
1. Yours is not a publicall visible ip then.
My friend too had the same problem with his service provider.......Whenever he used to access the ip of his comp it used to take to his service providers webpage.
2. There maybe some setting we maybe missing out........But I think you have tried out everything.

[Trekky]

Ok... is there anyway i can get around the Public Visible IP then? Please say Yes! Switching ISP is not an option but :P

SHall i ring my ISP for some help?

[raghavendra]

Hi
First confirm it with your ISP whether they are NATting you, because we are not yet sure whether it is the problem with the settings or ISP.
I dont have much idea about getting around with this...........Maybe somebody in the forum knows the answer :)

[AndyGreen]

You're up on

http://xcell.sytes.net:90/

it's working fine. ( Sphyrix Networks: We ARE the future! Because In The Present We Can't Serve On Port 80!) Therefore either you fumbled the port forwarding for port 80 (perhaps not so likely given the time you spent staring at it) or your ISP does indeed reject attempts to make connections to your port 80.

Assuming it is the ISP, that's a stupid and cheap 1990's type thing to do and buggers you up. Unless you are willing to get everyone to add :90 to your URL, it means you either need to get a friend with a server on port 80 to do a redirect to your IP port 90, which will look messy in the browser address bar, or you need to stump up some dollars for some hosting space and maybe a domain name. Or, you can get a new ISP with better bandwidth that does not block port 80.


PS: I know it can seem depressing after a while when things are not working, but that Windows-style "uh no I guess I have to reinstall to fix it because I don't understand it" is MUCH less often the right idea on Linux.

[Trekky]

Oh ok.. wow, cheers for that.
I'm just happy it's accessable.

Now to sorting out the port 90 Crap.
I dont think it rejects Port 80, i think possibly there's something i've missed.
But i'm not gonna touch it till i get some tech support.

Thankyou so much you guys, really helped me.

[raghavendra]

Hi
Its great to see that it is working.
AndyGreen can he try to do anything of the below:
1. Can he use something like tinyurl?
www.tinyurl.com
2. Can he give the ip with 90 to no-ip.com?
I know it will be tedious.
What about the first suggestion?

[AndyGreen]

Nice idea raghavendra.

http://tinyurl.com/c7em9

I assumed no-ip was just providing raw DNS, but I go and look and you're right on that too, they offer redirection. Trekky, see if you can use the redirection feature of no-ip to send folks to :90.

Also, back in comment #8 on p1, Lindamus says:

iinet australia does block incomming ports (not all, but the most common types)

That they are blocking port 80 is the most satisfying explanation at the moment.

[Trekky]

Hmm.. ok, sorry i missed that.

I'm a amiture at this so it's kinda Throw idea's at me "In Stupid form so i can understand it"

I'll try that redirect thing


Edit// Ok did that port 80 redirect, hopefully it's up to scratch now :)

[Trekky]

OMG... i was waiting for this

It's now accessable from the net.. But not by lan. I cant not access it by Lan ip or http://localhost/

Someone else in this forum had this problem, i'll have a look to see if there was a solution in another thread

i can access it by puTTy still but

[AndyGreen]

Heh heh -- you're up now just from

http://xcell.sytes.net

thanks to raghavendra's no-ip redirect method. The only "issue" is that the browser address bar ends up saying, eg,

http://203.59.13.233:90/


You must still be able to access it by LAN ip if I can access it externally! What is the URL you are giving and what is the results?

[raghavendra]

Hi
Nice to see its working........I think as Andy said you should get it working in your LAN.
Do retry it by going through the settings of Apache :)

[Trekky]

In Address bar i'm putting in the Linux box Lan LP. And it says Connection refused.

Then when i put in http://localhost i get a connection Refused error as well.


I try going through the setting of apache.. I'm an Amiture so i'm not to wizz bang at this.

BTW hehe thats bad that it says my ip :(

[Trekky]

Ok.. i still cannot reach the localhost through lan.
It's accessable from the net but through lan is a different story.
I dont know where to go or what i did to prevent myself from getting to http://localhost



Edit// i can access it now by IP still not by URL http://localhost

but it will do i spose

[raghavendra]

Hi
I think this may have to do something with the security settings but I am not sure.
I was just browsing for your problem and found this post (This post is for windows but the problem is similar)
http://forums.aspfree.com/showthread.php?threadid=54215
You can also try editing the /etc/hosts file
See this link......the post by
Firewing1
http://www.fedoraforum.org/forum/showthread.php?t=51054&highlight=access+localhost
Hope that helps :)

[Trekky]

ok cheers for taken the trouble to help

[sezer]

this can be anything.

[Trekky]

It ok now it working fine.
i can see it now through lan, but not http://localhost
But i'm not anoyed by that.

FTP is working, and i'm about to get mysql configured.

I just like to say thankyou to everyone that help me.
Cheers heaps