Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: kevincallan on July 09, 2008, 09:01:41 PM
-
Hi, all.
I have a network setup like this: ISP----DSL Modem----SME Server 1----SME Server 2
Both SME servers are running 7.x.
SME1 has IP address 192.168.1.1 on the internal network and a port forwarding rule set in the manager panel to:
Protocol: TCP
Port: 8080
IP Address: 192.168.1.2
Dest Port: 80
SME2 has IP address 192.168.1.2 and a web server running on port 80. Its default gateway is set to 192.168.1.1.
When I browse to 192.168.1.1:8080 on my LAN, I get nothing. That's OK with me.
When I browse to sme.homeip.net:8080 (fictitious), I also get nothing. This seems like an error is setup or software. I'm betting on setup being the problem.
Any suggestions?
-
sme.homeip.net:8080 (fictitious)
This is not helpful at all.
The only way to test your forward is to get outside of your network
ISP----DSL Modem--V--SME Server 1----SME Server 2
V
V
In front of this.
And try your.server1.wan.ip:8080 This should put you through to port 80 on the SME Server 2
-
When I browse to 192.168.1.1:8080 on my LAN, I get nothing. That's OK with me.
When I browse to sme.homeip.net:8080 (fictitious), I also get nothing.
If you are doing that on your LAN, then that is not surprising. As I have said here many times now, the two most common cause of port forwarding not "working", are because someone is trying to use it from the LAN (it doesn't and can't work from the LAN), or they don't have the default gateway set correctly on the internal system (must point back to the gatway machine which is doing the forwarding).
-
Yes, I am sorry I was not more clear. When I said
When I browse to sme.homeip.net:8080 (fictitious), I also get nothing.
I meant to indicate that it was from outside my LAN.
So given the advice from both posters, and having done those things already, it seems that the behavior is not as expected.
-
mercyh, Charlie,
Now I feel like an idiot. It is actually working fine. I asked a friend to try it from his computer and it worked for him. The router at work must have that port blocked and I assumed that it was my SME setup. Sorry for the nuisance post.
Thanks,
K
-
Sorry for the nuisance post.
Its not. The next person that has this problem may read this and say "Hey, maybe I should have a friend check this forward for me............" :cool: