IIS redirect

[mic_y]

Hi guys,

I need to allow access to an IIS server running on my machine. The server hosts a small website for a project for uni (basically just a silverlight app).

In any case, I originally set everything up on my PC side, then went to the router, made sure that the DHCP address allocated to my PC was set to be static, and then also configured a port 80 redirect. Also enabled the built-in dyndns client to automatically update my dyndns account with the current IP address.

Initially, everything seemed to work perfectly (I could access the site from wherever, with no problems).

A couple of weeks later, I needed to bridge my 2 Ethernet connections for some stuff and obviously things stopped working (as now the router thought i was connecting with a different MAC, and was now allocating a different IP address to the machine).

After deleting the bridge, my PC got assigned the normal IP address (192.168.0.4). For some reason though, I cant access the site from anywhere outside my network. Internally, I can access it from any of the PC's, but externally, nothing. Dont see anything in the IIS logs either.

I checked on an outside machine, and the IP addess resolves correctly, and I can ping the domain name.

My machine is running Win 7 Ultimate. Router is a DLink DSL-2540U.

Any ideas on what could be wrong?

Thanks in advance.

 

[bleh69]

get linux?

 

[The_Unbeliever]

get linux?

hehehe, no you'll need to forward port 80 on your router to the PC running IIS

 

[mic_y]

hehehe, no you'll need to forward port 80 on your router to the PC running IIS

ah oops, sorry for the incorrect terminology, by port 80 redirect in the opening post, I meant, I had forwarded port80 to the PC's IP (192.168.0.4)

any other ideas?

 

[bleh69]

portscan your IP (or dyndns domain) from outside to see if port is open. If not --> problem with router settings / If open --> problem with server settings.

 

[mic_y]

ah guys, figured it out... everything was set up fine on my side. If forgot to mention that my ISP is MWEB and by default they block incoming connections on port 80 only found out about it by mistake. That would explain why it had not been working the whole of May (since I moved to MWeb)... in your ADSL client zone thingy on mweb, there is an option to turn off "ADSL Protected Access" which is what blocks the incoming connections.

any case, hopefully someone runs into the same problem and finds this thread useful.