SOHO with a webserver 1

[winkshog]

I have a soho run off a cable modem i can see out through the server but i can not see in. I am setting up Novell web server to run groupwise iand and from what i can see i can not get to the server from the out side. am i missing something.

Thanks for all you help.
wink

 

[Ntr0P]

You will need to add to your inbound rules for port 80, the private IP address of your web server. It will then be accessible from the outside via the public IP address of your SOHO.

 

[winkshog]

I have the port open and when it try to open the web page I get page not there. how do i know that when i ping the ping is comming from the server and not from the fire wall?

sean

 

[Ntr0P]

Does the site work internally on port 80?

 

[winkshog]

if i type 192.168.111.100 i get to the web site. i go out side the net work and type 66.227.XXX.XXX and i get site not found. is this what you mean by working internally on port 80?

sean

 

[Ntr0P]

You answered the question, but what I was getting at was whether you could view the site when you were on the same network as the web server.

When you try to access the site via the 66.227.xxx.xxx address, do you see any deny messages in your log on the firewall?

 

[winkshog]

When I try to access the web server from 66.227.xxx.xxx address I look at the log on WatchGuard I don't see anything that looks like access deny. I see entrys like this "Packet allowed from 192.168.111.3 port 1936 to xxx.xxx.xxx.xxx port 80 (TCP)(allow by HTTP)"

 

[winkshog]

is there tool that i can use to tell what post are open on the fire wall???
at this point I allow all and i am still not getting to the web server.

sean

 

[Ntr0P]

Open ports on SOHO. No there are no tools, but this is easy enough to do. All WG products take the default stance of deny all except that which is explicitly allowed. So, only the ports you have opened are your open ports. Hopefully that is a short list.

If you access Inbound when looking at the SOHO configuration, your HTTP port 80 rule should be set to "allow" and the IP address should be set to your internal IP of 192.168.111.100 or whatever your web server's IP is.

It is that simple.

 

[winkshog]

Get this. i found a web site that will scan for open ports i have a port on the watchguard open and the web site tells me that the only open site is the HTTPS and low and behold it works but all the other ports are closed. is there something wrong with the watchguard. the watchguard configuration setting pages shows all ports open... so i thought what would happen if i closed the https would that close the port and yes it does. so the big Question is why can i not do this with any other port.

lose and need to find the path to enlightenment

sean

live free or die trying

 

[winkshog]

To let you know what happend the the rourter had all the ports cloesed. now i have a web server that is up and running

thanks for all your help

sean