This is an archived, read-only copy of the United-TI subforum , including posts and topic from May 2003 to April 2012. If you would like to discuss any of the topics in this forum, you can visit Cemetech's
Technology & Calculator Open Topic subforum. Some of these topics may also be directly-linked to active Cemetech topics. If you are a Cemetech member with a linked United-TI account, you can link United-TI topics here with your current Cemetech topics.
Computer Tech Support =>
Technology & Calculator Open Topic
| Author |
Message |
|
Arcane Wizard
`semi-hippie`
Super Elite (Last Title)
Joined: 02 Jun 2003
Posts: 8993
|
 Posted: 09 Jun 2007 06:30:13 pm Post subject: |
|
|
http://62.195.169.118 ends up at my router 192.168.2.1, clearly the timeout shows it is not actually forwarding the port to 192.168.2.101 (also 192.168.0.1 for the server's subnet) which forwards the port just fine to my server, but it used to work in this exact configuration.
Any thoughts?
Last edited by Guest on 09 Jun 2007 06:32:19 pm; edited 1 time in total |
|
| Back to top |
|
|
Newbie
Bandwidth Hog
Joined: 23 Jan 2004
Posts: 2247
|
| Posted: 09 Jun 2007 07:58:16 pm Post subject: |
|
|
Have you recently installed any new firewalls/antivirus or changed their settings?
Edit: I've always had port forwarding problems while running McAfee. After uninstalling it and reinstalling a new firewall (Comodo) I no longer have problems where I can't play online games.
I see your router has DMZ, trying enabling that for your internal IP address.
Last edited by Guest on 09 Jun 2007 08:04:55 pm; edited 1 time in total |
|
| Back to top |
|
|
alexrudd
pm me if you read this
Bandwidth Hog
Joined: 06 Oct 2004
Posts: 2335
|
| Posted: 09 Jun 2007 08:56:50 pm Post subject: |
|
|
Why does screenshot 2 show 192.168.0.101 instead of 192.168.2.101?
Do you have two routers? (Internet > "Broadband router" > D-Link Wi-fi > You)
If so, why is first router not forwarding to the second router, instead of your computer?
You do have a static IP address, right? |
|
| Back to top |
|
|
Arcane Wizard
`semi-hippie`
Super Elite (Last Title)
Joined: 02 Jun 2003
Posts: 8993
|
| Posted: 10 Jun 2007 07:13:45 am Post subject: |
|
|
Newbie wrote: Have you recently installed any new firewalls/antivirus or changed their settings? I don't use software firewalls or antivirus on any of my own computers. Plus, I can reach my server just fine from my desktop and laptop on 192.168.0.x. The problem is that some ports forwarded from 192.168.2.1 to 192.168.2.101 work but 80 times out.
Quote: I see your router has DMZ, trying enabling that for your internal IP address.[post="107363"]<{POST_SNAPBACK}>[/post] Doesn't make a difference and is not an option. Disabling the router firewalls for either router also makes no difference.
Quote: Do you have two routers? (Internet > "Broadband router" > D-Link Wi-fi > You) Yes.
Quote: If so, why is first router not forwarding to the second router, instead of your computer? It is forwarding all kinds of ports to the second router, but port 80 times out. The first router forwards nothing to my own desktop.
Quote: You do have a static IP address, right? Internally yes, depending on MAC address.
A diagram of my network is attached.
The only problem is that accessing port 80 on my WAN IP times out while ports 10000-10099 work fine and they're set the exact same way on the Sweex router (forwarded to 192.168.2.101) the only difference is the DLink router forwards those to my desktop and port 80 to my server. However, that DLink is forwarding fine as I can access port 80 to my server from withint 192.168.0.x just fine.
Last edited by Guest on 10 Jun 2007 01:13:57 pm; edited 1 time in total |
|
| Back to top |
|
|
alexrudd
pm me if you read this
Bandwidth Hog
Joined: 06 Oct 2004
Posts: 2335
|
| Posted: 10 Jun 2007 11:51:25 am Post subject: |
|
|
I just got through to the 403: Forbidden message, which means you changed something (?) and port forwarding is working now. Now just set the permissions properly on /var/www or whatever you have it set up as.
EDIT: Got through once, but now it's not working any more. Check your server logs; is it being hit by DOS or something?
EDIT2: Got through again.
Last edited by Guest on 10 Jun 2007 12:18:39 pm; edited 1 time in total |
|
| Back to top |
|
|
Taricorp
Member
Joined: 09 Mar 2006
Posts: 188
|
| Posted: 10 Jun 2007 12:23:15 pm Post subject: |
|
|
| Looks fine now, I also got through to the 403. |
|
| Back to top |
|
|
Arcane Wizard
`semi-hippie`
Super Elite (Last Title)
Joined: 02 Jun 2003
Posts: 8993
|
| Posted: 10 Jun 2007 01:37:05 pm Post subject: |
|
|
It's timing out now and I haven't changed anything. I guess its not the port forwarding then.
Now I'm checking the logs over SSH and could connect via my WAN IP. Port 80 is also working for now.
Code:
KRISKSERVER:~# ls -Rl /var/log | grep 2007-06-10 | grep .log
-rw-r----- 1 root adm 121610 2007-06-10 20:17 auth.log
-rw-r----- 1 root adm 9803 2007-06-10 13:15 daemon.log
-rw-r--r-- 1 root root 956 2007-06-10 13:15 dirmngr.log
-rw-r----- 1 root adm 81558 2007-06-10 13:15 kern.log
-rw-rw-r-- 1 root utmp 292876 2007-06-10 20:14 lastlog
-rw-r----- 1 root adm 282 2007-06-10 13:15 lpr.log
-rw-r----- 1 root adm 138174 2007-06-10 20:35 syslog
-rw-r----- 1 root adm 16892 2007-06-10 20:27 access.log
-rw-r----- 1 root adm 10747 2007-06-10 20:27 error.log
-rw-r----- 1 Debian-exim adm 60984 2007-06-10 20:15 mainlog
-rw-r--r-- 1 root root 1740 2007-06-10 14:51 20070610.log
-rw-r--r-- 1 postgres postgres 15564 2007-06-10 13:15 autovacuum_log
-rw-r----- 1 postgres postgres 157413 2007-06-10 20:35 postgres.log
-rw-r--r-- 1 root root 84474 2007-06-10 15:29 log.ad-45648dae4e2d
-rw-r--r-- 1 root root 180488 2007-06-10 13:30 log.kriskdesktop
-rw-r--r-- 1 root root 2196 2007-06-10 13:21 log.nmbd
-rw-r--r-- 1 root root 1386 2007-06-10 13:29 log.smbd
Apache access logs only show the ones that get through, obviously. Nothing strange there. There's me just now and Taricorp almost an hour ago.
Error log is just showing the 403's that are correctly there and a 404 or two from an old image in the photoshop topic which I guess is sometimes getting through.
Only entry for today in /var/log/daemon.log is whining about not having been closed correctly when I turned the server off last night from this morning when I started the server (~13:15).
Nothing exessive or strange in kernel.log, auth.log either.
And now it's timing out again and ssh via WAN IP is too.
Last edited by Guest on 10 Jun 2007 01:38:12 pm; edited 1 time in total |
|
| Back to top |
|
|
|
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.
»
Go to Registration page
