Gentlemen,
I have recently upgraded to Vista which came with IIS 7. IIS 7 is greatly enhanced over IIS 6 and IIS 5.5 with a pretty nice interface however....

I am having a devil of a time accessing my web services, which are resident on my IIS 7 (Vista) server from the outside world. I can access the web services which run rather well BTW from within my network and even (very odd) from my laptop from the outside world but I can not get to my WS calls from any of the other servers in the world. Here's a URL which should bring up the list of web services under the Visual Studio 2008 "test harness". It does from my server but not from anyone elses. I have opened port 80 (HTTP) on both my Windows firewall and on my Linksys wired router...no change.

Any suggestions? Any success viewing my web services?

Thanks guys

When you are within your network, you can access the webpage by typing in 'localhost' right?

Your PC with the webpage on will have to have a static IP address, and when accessing the webpage outside your network, you will need to type in the IP address of your router to access your web page...


Sorry if you have done all of this already

Jam

__________________

What exactly do you mean by "web services?" Do you mean the ability to review your pages? or do you mean the ability to manage your IIS.

Did you make sure your files in your /inetpub/wwwroot/%website% directory are set to allow viewing by everyone? (file/folder permissions)

When you pull up your web site, what do you see? What errors (if any) do you get?

Do you use a Dynamic Host Name service?

__________________
I'm here, you may now make your next two wishes.

Beat Me, Whip Me, Make Me Use Windows!!

Every Piece of Electronic Equipment runs on a finite amount of smoke. The systems are normally very efficient at reclaiming the smoke and recycling it, however, should you do something to let the smoke out, your system will become useless.

SAVE THE SMOKE !!

New PC :
New: Phenom 9500 Quad 2.2, 4gb ram XP Pro 64-bit (Sata 0), XP Pro 32 bit (sata 1), 40 eide HDD (music), Pioneer Blu-Ray Burner, HP Multidisk CD-RW/DVD-Rom, 2x250 Seagate HDD's, ATI Radeon 3870, Asus M3A32-MVP Deluxe WiFi-AP

Old PC:
P4 1.5GHz, 768 Ram, hda-80Gb (80Ubuntu), DVD R/RW

I have a static IP from Comcast and that is what I am using. I succeed from within my LAN using both "localhost" and the actual ip but I fail using the actual IP from outside of my firewall. I have opened port 80 on both my Linksys and on the Windows firewall yet a port checker says that port 80 is blocked. Comcast says that it is not and I tend to believe them so my inclination is that Vista is blocking the port. The port checker shows 127.0.0.1 Port 80 blocked which leads me to that conclusion. ANy thoughts?

Check to see if your A/V (norton or mcafee) has its firewall blocking the port.

Vista will open the firewall port when you install the IIS, which leads me to think it's the A/V.

Also, make sure your router is sending any http requests to the proper computer. That is, check for port forwarding to your internal computer with IIS installed. Make sure that it has a static IP inside your lan while you're at it, as port forwarding goes to an IP, not a MAC-address.

__________________
I'm here, you may now make your next two wishes.

Beat Me, Whip Me, Make Me Use Windows!!

Every Piece of Electronic Equipment runs on a finite amount of smoke. The systems are normally very efficient at reclaiming the smoke and recycling it, however, should you do something to let the smoke out, your system will become useless.

SAVE THE SMOKE !!

New PC :
New: Phenom 9500 Quad 2.2, 4gb ram XP Pro 64-bit (Sata 0), XP Pro 32 bit (sata 1), 40 eide HDD (music), Pioneer Blu-Ray Burner, HP Multidisk CD-RW/DVD-Rom, 2x250 Seagate HDD's, ATI Radeon 3870, Asus M3A32-MVP Deluxe WiFi-AP

Old PC:
P4 1.5GHz, 768 Ram, hda-80Gb (80Ubuntu), DVD R/RW

Thank you for the suggestions. I was only running Windows Defender at the time but have since re-activated Trend. Thanks for reminding me to open port 80 on it though. I am about to get down and dirty and debug this hummer logically by starting with the removal of the router from the mix then moving upstream to locate the source of the problem. I have a static IP from my ISP and I have set a static IP internally as well but again, thanks for the prod to check these once again. I hate cable stuff but....