IIS issues (www)

[DynamicNetSolutions]

Hello All.

I am having a problem hosting my website. The directory is all set right. The server has all the correct name servers and what not. I can successfully ping all neccessary addresses.

mail.____.com
smtp.____.com

http://www._____.com

etc..

But outside my network the page will not show up. All ports are open just to eliminate it being a port issue.

Any tips or suggestions?

 

[monsterjta]

Can you ping these addresses from the outside? Did you create these A records with your registrar?

Hope This Helps,

Good Luck!

 

[DynamicNetSolutions]

Hey thanks! Yes. I can ping all these addresses from the outside. A records in the DNS right?

Thank you!

 

[monsterjta]

Do you have a static public IP address? You need to FORWARD the ports to the web server, not just open them. What are you using for a gateway/firewall?

Hope This Helps,

Good Luck!

 

[DynamicNetSolutions]

Yes I do have a static IP address. My gateway is a Linksys WRT54G Router.

 

[monsterjta]

Ok. So are you forwarding your public IP to the private IP of the web server? This is a static forward.

Hope This Helps,

Good Luck!

 

[DynamicNetSolutions]

Yes, my public IP is static on my router. My local IP on my server is static. And within my router I have all ports forwards to my static IP address on my server. I have set DMZ in the router to my server, to eliminate it being a port issue.

 

[monsterjta]

Can you ping the public IP address from the Internet? Not from inside, but from outside...

You asked earlier

"A records in the DNS right?"

This is correct, but not on an internal DNS server. Who is your registrar for your domain? This is where you need to setup your A records.

Try this...go to dnsstuff.com. There are many tools there to help resolve. This will assure that you have your A records setup correctly. Use the PING tool and the NSLOOKUP tool.

Hope This Helps,

Good Luck!

 

[Teknoratti]

correct monsterjta,

Internally it doesn't even matter b/c you are behind your LAN. You should have those DNS records registered in the public space, unless you want people to connect to your web server using your public IP from your ISP, i.e

http://xxx.xxx.xxx.xxx

That's what I did before. I was too cheap to purchase a domain name, so I just connected to my server via IP address.

Register the domain, then point the A record to your public IP address, then configure port forwarding on your linsys router.