Endless Paradigm

Full Version: Getting a webserver going....
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
The port checker says that 51889 is closed when Apache is set to use it...

So Apache is the problem I'm guessing...
I'm actually not sure whether the port checker checks UDP or TCP.  Which ones have you forwarded?
TCP...

Though BitTorrent and HTTP both use TCP so it should work...
Well I'm out of ideas then.  Netstat says Apache is listening on the port, the router is forwarding it, but nothing can get a connection through...  ISP can't really block it either...
am i right in assuming the server machine connects directly to the router used for the internet connection? if so do you have another pc connected to the same router directly (i.e. not via router hub switch etc.)? im not clear on how its configured but it definetly sounds like the server has an issue with the connection. if you are able to connect to the server within your network (i.e. alternative machine connected to the same router that's used for the internet connection, and can connect to the server) then simply put the problem is from the router onwards, and as you have checked your ports via utorrent it means the port forwarding is ok so i would strongly suggest contacting the isp. if however a second machine within your network cannot connect i would suspect the firewall on the server (if one is running), and if not then all connections should be checked (software and hardware). i once had a problem that was traced down to a faulty lan cable - it turns out one wire was broke meaning the connection was established but nothing could get through - weird but true, and yes sorry but completely off topic.
Pages: 1 2 3
Reference URL's