I have created a website in iis on my home computer. The computer is on a d-link network.
The binding ip i 192.168.0.103
Whenever I try to go to the url, it takes me into the d-link configuration instead of the webpage why???
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
first off - what operating system?
follow one of these guides to configure IIS
http://www.bigbilly.com/bb
http://www.bigbilly.com/bb
during those steps you will find the IP address of your pc (we'll assume it is 192.168.0.103)
follow this guide to configure host headers - but in your case , leave the host header value blank
and instead of all unassigned, select your IP address
http://www.visualwin.com/h
good luck
bbdc
On the D-Link interface, there should be a section for "Virtual Servers". You can configure a virtual server for HTTP (port 80) to point to the IP address of the IIS server. On some of the D-Link routers, it won't show you the IP address, but will instead require you to point the virutal server to the name of the server.
I just looked on mine and it is under Advanced | Virtual Server. There is already one configured called "Virtual Server HTTP". If yours is the same, edit that one to point to the IP address of your IIS Server. Then, restart the D-Link device (unplug it).
That should allow outside computers to get to it. However, if internal computers can't get to it, there is probably something else wrong with your IP settings. Try the http://localhost and let us know what happens.
The IP address of the router? If so, then issue the following command on one of the workstations that is using that router to get to the Internet.
1. Go to Start | Run and type "cmd" (without the quotes)
2. At the command prompt, type "ipconfig /all" (without the quotes)
3. Look for "Default Gateway".
The default gateway is the IP address of the router.
Or did you mean "localhost"? Localhost is an actualy name, so you would actually type the entire address "http://localhost" (just like it is, but without the quotes)
And then you also have two different sets of IP's in your case. Your 'external' and your 'internal'.
Your firewall should do something called NAT...Network Address Translation. The IP addresses you use on the inside of the network are theoretically unavailable to the rest of the Internet. So you router has an 'external' or 'real' IP address. It keeps track of which computer inside asked for which item and routes any incoming traffic to the correct locations as long as it is allowed within the firewall rules. The problem you are encountering is that there is no rule set up to do anything with inbound port 80 traffic so it defaults to the routers own internal web server.
Business Accounts
Answer for Membership
by: btpringlePosted on 2007-09-26 at 14:25:23ID: 19966878
I assume that the URL that you are using is http://192.168.0.103. Is that correct? If so, try http://localhost and let us know what happens.