webramp with webserver behind it

Pinkpig

Member
Jul 12, 2001
134
1
81
Hello all.

I need some help setting up my webramp to allow user's from the outside to access my webserver to see my pages. I can surf and get on the internet fine. I have cable and my ISp gives me an IP by dhcp. Everything works fine before with my Dlink router until i setup the webramp.

here is how i configured mine:

Under
Access: I added a service (my web) with port 6049, so it looks like myweb[6049,6]

then under Rules
my setup is
Action=allow
Service=myweb
source=WAn
destination=192.168.1.1
and enable is checked off

the rest of my rules are (this is for temp only until i get everything working)

Action=allow
service=default
source=LAN
Destination=*
enable=yes

Action=allow
service=default
source=*
destination=LAN
enable=yes

any help on how to set it up so i can have my webpage hosted would be great!

I can go to my own website on the inside by going to http://192.168.1.1:6049 and it works but just not from the outside world

Also under general>network i have network mode setup to NAT and DHCP client.
after i rebooted i got two IP's (i think ) from my ISP this is my WAN settings

Lease expires: 02/25/2003 21:04:41.000

WAN Gateway (Router) Address: 24.XX.XX.XX
SonicWALL WAN IP (NAT Public) Address: 24.23X.XX.XX
WAN Subnet Mask: 255.255.255.127

so which is my real IP? i can ping my WAN router address but i cant ping SonicWall Wan IP (NAT public) addy.

Sorry for all the questions, but i really need some help on this little wonderfull device =)

Thank you
Laura
 

xyyz

Diamond Member
Sep 3, 2000
4,331
0
0
WAN Subnet Mask: 255.255.255.127

i've never seen that SM before... how does that work?

i don't know if the webramp works like access list rules... where the order of the rules matter. you might want to put the hole for the webserver before the other rules and try that.

the WAN IP address is jwell the SonicWALL WAN IP. the other is the gateway for your outmost network... sorta like the gateway you'd have on the dlink router.

oh yeah one more thing... i wasn't too clear on your explanation...

the DHCP... that's set on the WAN side? not the LAN side right?

oh yeah... this might help too

then under Rules
my setup is
Action=allow
Service=myweb
source=WAn
destination=192.168.1.1
and enable is checked off

might wanna check that "enable" box :)
 

Pinkpig

Member
Jul 12, 2001
134
1
81
Opps mi-typed some words ack, sorry.

WAN Subnet Mask: 255.255.255.128 not 255.255.255.128

then under Rules
my setup is
Action=allow
Service=myweb
source=WAn
destination=192.168.1.1
and enable is checked off ---> what i meant here is enable=yes checked of meaing its checked to yes hehe sorry that it wasnt to clear.


xyyz so SonicWALL WAN IP (NAT Public) Address IP is my real IP address correct? that everyone should be able to ping etc..??

i tried pinging myself on that IP and it doesnt work. But if i ping myself on WAN Gateway (Router) Address it works.

Thanks
Laura
 

mboy

Diamond Member
Jul 29, 2001
3,309
0
0
your sonicwall Wan IP is your really ip addy for the outside world to hit.

Try having someone form outside your Lan try to access the server. I would also set up a static IP on the server (u can still enable dhcp on ther sonicwall for ther rest of your LAN).

In your rules, change the allow for myweb to:

allow
service: my web
source *
destination* lan servers IP

See if that helps.

Oh, also make sure under the services tab (is tab under the Access section) that your LAN ip is showing next to the neame of your myweb service.
 

Pinkpig

Member
Jul 12, 2001
134
1
81
mboy i tried what you said but it still doesnt work.

i tried pinging my own IP and i had someone else ping my IP also but it time's out. Why does that happen? Maybe thats why i cant see my webpages being served off my webserver.

THanks
Laura
 

mboy

Diamond Member
Jul 29, 2001
3,309
0
0
pinging it shouldnt have anything to do with it.

Have them try to access the web page.
 

xyyz

Diamond Member
Sep 3, 2000
4,331
0
0
the sonicwall allows for a static route. try entering one for your webserver. see if that works.