Accessing IIS 5.1 on Windows XP SP 2

Are there any specific measures that IIS 5.1 users need to make in order to view their website from outside the localhost? If I bring down Windows firewall, users inside my school campus can view my website. If not, they can't.

In addition, regardless of whether or not I have Windows firewall up, users not internal to my university's campus can not view my website by simply browsing to my IP address. For the default web site properties in IIS management, do I need to specify what my IP address is under the web site tab?? Right now I just have it as 'All Unassigned'.

I'd like to get some idea of what I can do to make external users have the ability to view my files before screwing around myself (I've destroyed existing IIS websites before by just toying around in the management tools)...

do you have a private or public ip. if public there should be no problem.
If private then you have to forward port 80 to yours ip at the router.

it is possible to open up programs and ports in Windows Firewall so you dont have to bring it completely down.

I do indeed have a public IP address. I just found out from a friend who works with the school's residential net service that they block port 80 on outgoing connections.

I changed the port for my site in IIS to 8080, but it still would not resolve outside campus. Any other ideas??

You have to open an exception for port 80 or whatever port your webserver is using in the windows firewall (and any other firewalls) to allow outside access to your web server. Many ISP's block port 80 outside your location.

Thanks to all have responded thus far.

My follow up question the prior post is if I open up the port using TCP or UDP? Also, what should I should specify the name as if I am using IIS 5.1??

This will most likely solve my problem of not being able to access the website when the firewall is up, however, it will most likely not solve the problem of people outside of my university being able to view my website (I have tested this out on numerous different ports with the firewall down)..

The name is decided by DNS. You will need DNS to resolve to your IP address, or a DDNS package if your external IP changes because you use DHCP.

All of these things are not controlled by IIS.

I think you might have mistunderstood my question, I just now realized that I wrote a question that looked like I spoke Chinese as opposed to English.

In Windows Firewall, what would I specify the Name to be when I am adding a port exception? The port would be 80 right? Is it as simple as 'IIS 5.1' or 'Internet Information Services' for the name?

afaik you can give an exception any name you wish, it's just for reference I believe.

I think I used something sophisticated like "httpd" or something for the name of my webserver exception