Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Desperate

Status
Not open for further replies.

RH610

Programmer
Aug 7, 2001
152
US
This is not about a Raptor firewall, but it is about a firewall problem and I am desperate, so I throw myself upon your mercy. I also should say that I am a firewall/WEB server semi-newbie.

I have a WEB server (installed by the provider who wrote the web-site) behind a router and firewall (SonicWall). The WEB server has an internal IP number. I set up a rule in the firewall to allow HTTP access on PORT 80 (the port of Microsoft IIS) and pointed the rule at the internal IP of the WEB server. The setup of the WEB server software, which is done from the WEB server, has me put in the URL of the web-site. It then contacts the site and updates a config file if successful. If I put in the internal IP of the WEB server, it says it cannot connect. If I put in the local name of the WEB server box, it saves and I can connect from another PC inside the firewall, but not from outside it. I have no idea what to put as the URL of the WEB server so outsiders can see it through the firewall. Do I put the public IP of the firewall? Do I need to buy a domain for it and register the domain with the internic and put that name in as the URL of the WEB server? I just don't know.

SonicWall wants $40 per 10 minutes to talk to me (thanks) and the WEB Server provider won't talk to me about firewalls ("we only provide the WEB server"), so here I am.

Thank You in advance.
 
You need a public IP address to host a site on the web. It must be registered( i forget the site to register, it costs money)and associated with a domain.
I think you will need another network card on your web server with the public IP.

That should get you going.
 
Hi, Thank you very much for the reply. You are the only person who was nice enough to talk to me about this. You would think it would have been easy enough for either the company who sold us the firewall or the company that sold us the web-site could have told me this. How long could it have taken them to at least do that.

I guess what you are saying is that the public IP of the firewall is not going to work (even though I have set a rule to send HTTP (port 80) to the internal IP of the WEB server. Is that right? If that is the case, are you saying we should run the WEB server outside the firewall? If so, doesn't that defeat the whole purpose of the firewall? Also, if so, how do I route that server around the firewall? Will I need to get a second router and/or line? Also, if I do register this server, what do I use for DNS servers? Do I have to get them set up here internally or can I use our existing ISP's DNS servers?

As you can see, I am fairly new at this and not all that knowledgeable and have a lot of questions. Thanks for putting up with that and again for your help. I think I will speak with our ISP also and see what they think, but please let me know if you have answers to the above.

 
Boy you are a newbie...

YOu should be able to connect via the public IP of your firewall. You can register a domain to it but nonetheless the ip should work. If you can connect internally but not externally ... Check your router to make sure that port 80 is port forwarded to your firewall. Sounds stupid but just check it. Then verify you firewall settings. This is pretty complicated stuff so please read read read.
 
Where you able to get this working ?

From your post it sounds as if your a little over your head.

Send me an e-mail and I would be happy to help walk you through the soloution
-cheers -Danny
dan@snoboarder.net






 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top