Forum Home
Press F1
Thread ID: 100978	2009-06-27 21:23:00	Network Timeout	LarsJohann (13010)	Press F1

Post ID	Timestamp	Content	User
786360	2009-06-27 21:23:00	Hello, i am trying to set up a website through Apache and i am using a DynsDNS address. I have forwarded my ports so that Apache can function and i can connect to the website through my DynsDNS address on my computer. However, whenever other peoples try to access the website, they get a Network Timeout error. Anyone know why?	LarsJohann (13010)
786361	2009-06-27 21:29:00	I can't help but some info in here might. pressf1.co.nz	Sweep (90)
786362	2009-06-28 02:22:00	Have you forwarded the ports yet?	Blam (54)
786363	2009-06-28 03:20:00	Go to www.canyouseeme.org and test the ports that you need open and make sure that they are actually working from the internet.	CYaBro (73)
786364	2009-06-28 05:01:00	Hello, i am trying to set up a website through Apache and i am using a DynsDNS address. I have forwarded my ports so that Apache can function and i can connect to the website through my DynsDNS address on my computer. However, whenever other peoples try to access the website, they get a Network Timeout error. Anyone know why? Generally if they're getting a timeout, it can be occurring in one of four places. The first (and most likely) is that you haven't set up port-forwarding correctly. As a result, your router is dropping all the packets, and as far as the client trying to connect can see, nothing is happening. Once it gets tired of waiting for a reply, it fails with a timeout error. The second possibility is the firewall on the system you are serving the page from is misconfigured, and is dropping the packets. Symptoms are largely identical to the above. The third option is a misconfigured DynDNS setup. If you go to whatismyip.com does the reported IP match what your domain is currently set to? If your IP isn't being correctly resolved, they will be trying to contact one of your ISPs other customers, who most likely doesn't have a webserver running! The fourth possible location for a timeout is the webserver itself, occurring after the connection has been made and the client has sent a request, but before the response is sent. This generally happens when a badly written script takes too long to run. Often, the server is smart enough to figure this out on its own and will give you a more detailed error message explaining the problem, but this isn't always the case. If you're not using dynamic scripts / webapps or CGI programs, this will not be your problem. Even if you are, it's unlikely - investigate the top three first.	Erayd (23)
786365	2009-06-28 23:25:00	ok so i went to www.canyouseeme.com and i checked port 80, well it gives me this error : Error: I could not see your service on 24.215.29.64 on port (80) Reason: Connection timed out Yes i do have the port forwarded on my router at the correct local ip address and i do have Apache initalised. I do not understand why this is happening and this could be the source of my problem.	LarsJohann (13010)
786366	2009-06-29 00:15:00	Its obviously not forwarded properly...try again..	Blam (54)
786367	2009-06-29 00:28:00	You may also need to change the port the your router web config is on as this will be using port 80 at the moment.	CYaBro (73)
786368	2009-06-29 00:34:00	Ok i think it's because i tried to forward the port in Virtual Server instead of Port Forwarding.	LarsJohann (13010)
786369	2009-06-29 02:26:00	Ok, here's a picture of my Virtual Server page and Port Forward page on my D-Link WBR-2310 router. Virtual Server page: www.freeimagehosting.net Port Forward page: www.freeimagehosting.net You'll notice that i have forwarded both port 80 and 443 which are both ports portforward.com recommend i forward while using Apache. And peoples who try to connect to my website still get a network timeout error. And also could someone explain to me what CYabro means? Regards, Lars.	LarsJohann (13010)
1 2