We help IT Professionals succeed at work.

How do I set up IIS so that the server's IP address resolves to a virtual directory in the default website?

Medium Priority
244 Views
Last Modified: 2012-05-06
Hi - We are running IIS 6 on a dedicated web server. There are two virtual directories set up within the Default Website. The host header value is blank - ie (server ip address | 80 | <blank>)
- Right now, we can access the two sites on the web server using http://localhost/<virtualdirectory>
- We'd like to be able to access the site from outside the server - serveripaddress/<virtualdirectory>

Is there any way to accomplish this without creating a new website? Ie, keep the IIS structure as is.

Your feedback is appreciated.
Comment
Watch Question

Kyle AbrahamsSenior .Net Developer
CERTIFIED EXPERT

Commented:
As long as IIS is configured to serve all IPs there should be no issue with this, should happen automatically.

Author

Commented:
I've confirmed that the IP Address field on the Web Site tab of the Default Website is set to (All Unassigned) with the only identity being:
Default     |     80    |    <null>
There are no other websites.

When I go to http://<ipaddress>/<virtualdirectory> I get the following messages:
IE - Internet Explorer cannot display the webpage
Firefox - just times out.
What else should I check?
Kyle AbrahamsSenior .Net Developer
CERTIFIED EXPERT

Commented:
can you ping the ip address?  

What kind of routers or what not?  It's most likely a networking issue, but to confirm that on the server can you hit the URL by IP from there?

Author

Commented:
I can ping the IP Address.
Packets: Sent 4 Received 4 Lost 0
Minimum = 95ms, Maximum = 96ms
If I go to http://<ipaddress> on the web server , I get an Under Construction message
If I go to http://<ipaddress>/<virtualdirectory> on the web server, I get the website just fine.

Does this prove your networking issue suspicion?

I have TS access to the server,  but I am not sure of the routers that are being used by my client. What should I ask and check on the routers?
Senior .Net Developer
CERTIFIED EXPERT
Commented:
on the router port 80 should be forwarded to IP of the webserver.  
443 as well if you're using SSL.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Kyle AbrahamsSenior .Net Developer
CERTIFIED EXPERT

Commented:
internally if everything is working fine it is a networking issue.

Can an internal machine (not the server) hit the website via URL (just to absolutely confirm).

Author

Commented:
we'll do some more checking in the morning and i'll get back with you... THANK YOU!
Kyle AbrahamsSenior .Net Developer
CERTIFIED EXPERT

Commented:
just adding a comment so my icon gets reset.  Let me know if it's the case.

Author

Commented:
Opening port 80 in the firewall resolved the issue. Thank you very much!
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.