IIS and DNS Issues?

[TamedTech]

Hello Guys,

I'm pretty new to server administration and i've been playing around this afternoon with getting it up and running.

I've got it all working internally on my network, I've got a website up and running on the box and if i view it localy on

http://192.168.1.100

then the page displays exactly as i would expect it to do.

However i've been trying to get external access to the site by setting up port forwarding for port 80 on my router to the servers IP address.

However when i access my public IP address i just get the administration panel for my router and it doesnt appear to be forwarding onto the server correctly.

So next i try changing the IIS settings so the site is sat on port 90 instead, so now i have to access it localy with

http://192.168.1.100:90

and it still works fine.

So i then set port forward for port 90 on my router to go through to 192.168.1.100:90, and yet when i go to my public ip address with the :90 on the end, it sits and spools for a moment before getting a 'page cannot be displayed' error message.

Any ideas what might be causing this?

Thanks,

Rob

 

[REVENUE]

If possible, disable router management from the WAN side. Then your site should appear properly.

SHV

http://www.stephenscomputerservices.com

 

[REVENUE]

In addition, in windows, add the public DNS addresses provided by your ISP in addition to your local dns server for the NIC with IP address 192.168.1.100

SHV

http://www.stephenscomputerservices.com

 

[TamedTech]

Thanks for getting back to me Revenue,

I've been playing around this morning and managed to sort the issue, it must be some form of DNS confusion, i've never been able to get my head around it.

Basicly my router is currently running as my DNS and DHCP server, so when i was plumbing in my public IP address from within the network the router was kicking me over to its local address without forwarding the ports.

If i access the public IP address from outside of my network, such as another building then it forwards port 80 onto my website and i can get access to it and FTP through port 21.

One thing you may be able to reccomend me a littl help with though, is setting up a perminant website.

I'm a ColdFusion developer and we're currently building a substantial application which really requires some dedicated hosting and cant be sat on a shared account with my ISP.

dedicated hosting isn't cheap at the best of times, and it makes complete sense for me to host it inhouse as we already have servers controlling our internal network.

Whats the deal with enabling external access to the site through a proper domain name, i have several .co.uk domains registered and unhosted at the moment, it would make sense to point those at our inhouse webserver would it not? how do i go about doing this kind of thing?

Thanks,

Rob

 

[REVENUE]

For editing public DNS, you can either use the provider in which you purchased your domain name, or you can use

http://zoneedit.com

- Zone Edit is free, easy to use, and provides all necessary instructions.

http://www.stephenscomputerservices.com

 

[TamedTech]

Thanks for that Revenue,

I'm more than happy to keep the domain with my current ISP and just edit the DNS with them to point it at my internal server.

How does this work however? do i simply assign a static IP on my line and then point the DNS IP's toward that IP adddress, then enable forwarding on my router to the internal DNS server that hosts my site?

Thanks,

Rob

 

[REVENUE]

Yes, assign a static public ip to your site, then point your domain name to that static ip. Finally, you will need to point your router to the local ip address of your web server. You don't have to point the router to your local dns.

Like you mentioned earlier, you can access

http://192.168.1.100

from outside your lan. All you will need to do is point your domain name to the public ip that accesses the 192.168.1.100 address. Then you can access 192.168.1.100 with your domain name.

SHV

http://www.stephenscomputerservices.com