Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hidendra]

Hi everyone,


I had bought a D-Link router a few months ago because my Linksys before that stopped working completely. I'm liking the new one a lot, just one problem :c

Right now I have a broad range of ports forwarded to my computer, one of which includes 80. My ISP blocks no ports at all. Now, if I use http://localhost it works splendidly. If I connect to my IP, it times out connecting. If I connect to my IP on a proxy or get a friend to, they can open it just fine.

So I'm just asking: why is it blocking my connections? I am on wireless by the way, and I think I have it configured right.. This has happened on Ubuntu, Windows xp and 7. So it's not a os-specific issue..


Also, if this helps at all, with a small game server, when I try to connect to myself via direct ip, it says 192.168.0.4 connects and then it immediately is closed. If I use localhost to connect to the server, the expected is 127.0.0.1 connects and doesn't drop (which of course is how it goes).


Thank you!

[rcarty]

If you connect to the 192.168.0.4 address locally (from another 192.168.0.X computer) I don't see how the router could be affecting it. If your wireless connection from whatever 192.168.0.X computer you are connecting from works fine then your wireless connection is not the problem. If you are connecting from the Internet to the local 192.168.0.4 computer on port 80, I expect, because you have multiple incoming virtual server ports configured, you know the connection has to be to the public IP address of the router, in other words the address on the Internet side. If other ports work and only 80 doesn't it may be a firewall issue on the router.