Port Forwarding Problem [Very Difficult]

[-Fáng-]

Hey Everyone,

I've been working on getting my server to be hamachi free for beta testing directly off of my laptop. I'm using PFPortChecker by Portforward.com. I checked my port 80 and it's going out on TCP and being seen by UDP. So... it works... but when you all try and see it, you can't.

I'm not going to give you my real ip address yet, so here you are:
#REMOVED LINK SO I DON'T GET BANNED

I know that that website is linked to my host laptop... (Won't do much good since I'm going offline... but if you see my green light on in the left corner of this post then you can check yourself).

The static IP works... (obviously since it works with PortChecker...).
All firewalls are allowing the port to pass...
So does anyone have a clue why it's being like this?
Me and my friends are all stumped.

Sincerely,
Fang

[Korvacs]

When setting up the website did you assign its ip address to the network one? Or "all unassigned".

[-Fáng-]

Originally Posted by Korvacs

When setting up the website did you assign its ip address to the network one? Or "all unassigned".

My router has a partnership with DynDNS.org. It does it automatically.
That's not the problem Korvacs. If you want to be HELPFUL though, you can respond to my PMs instead of ignoring me like a ***.

[bone-you]

Originally Posted by -Fáng-

I'm not going to give you my real ip address yet, so here you are:

Things like that are why you do not get why it's not working. All someone has to do to get your ip is to dns that host. How else are people able to connect to you? Their comps dns the host to get YOUR ip. Knowing networking is quite useful when trying to figure out why a port forward does not work. Chances are your ISP blocks port 80. Many do it.

[Korvacs]

Originally Posted by -Fáng-

My router has a partnership with DynDNS.org. It does it automatically.
That's not the problem Korvacs. If you want to be HELPFUL though, you can respond to my PMs instead of ignoring me like a ***.

Your router isnt where you setup the website, im talking about on the webserver, when you setup a website on the webserver it will ask you what ip address you would like to be associated with the website so that when the webserver receives a request on the dns name it knows what to do.

Your router doesnt come into that process, all your router will do is forward data to and from the webserver, and thats not what i asked.

Also i dont need to respond to you if theres no reason to, and there isnt.

[-Fáng-]

Originally Posted by Korvacs

Your router isnt where you setup the website, im talking about on the webserver, when you setup a website on the webserver it will ask you what ip address you would like to be associated with the website so that when the webserver receives a request on the dns name it knows what to do.

Your router doesnt come into that process, all your router will do is forward data to and from the webserver, and thats not what i asked.

Also i dont need to respond to you if theres no reason to, and there isnt.

stop giving me infractions. I know you want me gone but being a terrible moderator isn't the way to do it. You're being unfair now.

And no, I know what I'm talking about.
AppServ --> port 80 --> 192.168.1.2 --> (my public ip) --> port 80
and
AppServ --> port 80 --> 192.168.1.2 --> #REMOVED LINK SO I DON'T GET BANNED --> port 80

My router has it programed into it. I might be lost with what the problem is but I'm not blind. Plus it doesn't work with the public ip either.



That's what I get yet people can't connect still to the website.

And yes, please just stop responding. I'm done with it.

Originally Posted by bone-you

Chances are your ISP blocks port 80. Many do it.

Does the picture above support that claim?

[bone-you]

Originally Posted by -Fáng-

Does the picture above support that claim?

Yes. HTTP does not use UDP. It uses TCP.

[-Fáng-]

Originally Posted by bone-you

Yes. HTTP does not use UDP. It uses TCP.

*** blocks port 80. You're right.
Thank you. =]

EDIT: Problem Resolved. Thank you =]