IIS newbie, Loosing hair and sleep. 1

[milesy]

I realy hope that someone out there can shed a little light on my problem.

Ok here goes.

I have a Windows 2000 server.
I have installed IIS 5 and I have a small intranet site.
I can access the site from the LAN either by typing the ip address of the server, or by typing the name of the server Web-Server into the address bar.
But I cannot access the site from the WAN.
I have forwarded port 80 to point at the server

I have registed a domain name. xxxxxxx.com

I have registed with DynamicDNS ( as i have a dymanic ip)
the dynamic dns side is realy sorted and works fine.

What am I doing wrong? The only thing that I can find on the forum is some thing about the router not supporting 'Loop Back' ???

Some one please throw me a life line, I'm going bald!!

 

[patchkit]

I know that this is mosty likely already been checked, but make sure that your DNS server entry is correct on the far side of the WAN connection. You may want to add the DNS server address in the remote system as a secondary.

Easy way to test if this is the issue, you can place a static entry in your host file and test it.

 

[milesy]

Thanks Patchkit.

Yep checked that and its all ok.

Do you think my ISP (BT) may be blocking port 80?? its a long shot!

 

[WhoKilledKenny]

You could go to

http://www.grc.com

(Gibson Research Center) and run a program called shields up. This will run a port scan from the Internet to your machine. This will answer your question of port 80 being blocked...

 

[milesy]

WhoKilledKenny tanks
What a nice little bit of software that is. Cheers.

The bad new is the report says that port 80 has been stealth blocked!

But surly if port 80 is blocked, shouldent by web browser be having major problems?

 

[WhoKilledKenny]

The scan you did with "Shields Up" scans from the Internet to your network. It shows port 80 inbound as blocked. You are able to surf the net because port 80 outbound (from you network) is open. Check any Software or Hardware firewall you have in your environment, That may be the culprit. Continue to test with "Shields Up" until you see port 80 open.

 

[WhoKilledKenny]

PS - Do you "Sheilds Up" testing from the Web server...

 

[milesy]

OK its sorted.

Just incase anyone else has the same problem, there is what was wrong.

Port forwarding and port triggering, there is a differance..

This is something new to me, I fowarded port to port 80 and this did not work. After looking at my router setting I had never used port triggering so I thought I could not loose anything and shure enought I triggered port 80 external to port 80 internal and it works fine.

Thanks for all the help.