ADSL has the problem of setting up a web server through IIS

DNS check: Run the nslookup command to check whether the dynamic DNS instance takes effect.

If that's not possible, go back to your intranet and access it on your server to see if it's possible.

If this is not possible, check**.

If possible, continue to try to access your** from other computers on the intranet.

If possible, try connecting the ** server directly to the network, skip the router, and try line 3 again. The reason may be that the router inherently occupies port 80 (many routers will occupy this port by default on the external web management side).

If this is not possible, check if the server has software such as a firewall. And try again.

If you are sure that the router will not occupy 80, you may still want to move the router out of the network and let the web server be directly exposed to the Internet with an external network address. On the one hand, even if some routers change the web management port, 80 still belongs to the default occupation range, on the other hand, it may be that your web server program is set up incorrectly, the common phenomenon is that Apache is only bound to the private IP address, etc., by removing the device that may be an obstacle, you can easily diagnose where the problem is.

Do you set up a web server to access the card? Have you ever counted how many people will get stuck when they visit together?

You're fine with all of this, except for one missing step: port mapping.

Map the "port 80" of the machine where you set up the web server through the router, so that the external network can access the web pages of the web server.

First floor Well said!

I once showed it to my friends here!

I made a web server!

Here is also for interested friends to take a look!

Right-click on Network Neighbor - Properties, right-click on Local Connection - Properties, and under the Advanced tab of Local Connection Properties, check Allow other network users to connect through this computer's Internet connection - OK.

This way, the virtual machine can also access the Internet. You fill in the web server, but you generally need the router to do a NAT and map the private IP of the private network to the external public IP.

If ADSL is to automatically get the IP address, you have to go to the next software called Peanut Shell, and then select all unassigned IP addresses in the web server.

The NAT mode of the virtual machine and let the virtual machine automatically obtain the IP address.

Set up a web server according to the method of several people upstairs, and verify that there is no problem with the private IP.

Then under the mapping on the NAT mode, the peanut shell can be accessed by the public IP after setting.

Hope it helps!!

Select Bridge the virtual machine and check Copy Physical Network Connection Status and check the status as Connected and Connected When Power On.

Set the IP in the virtual machine to the same IP range as the physical machine's IP, and set your virtual machine's gateway and DNS to be consistent with the physical machine's.

Then you can install components such as IIS and hang up.

What a virtual machine This kind of mess is never used!

Peanut shells are recommended!

web server I see you'll rack! The main problem is how to get access to your server!

Peanut shells! Ah, peanut shells!

Generally, the user permission is not set, if you are local, you can give the permission of everyone to the directory.

If your virtual directory is a folder.

If you specify the folder B in the virtual directory A, then you need a folder B in the real folder A, even though the folder B may be in another location on the computer.

IIS is a component that is used to run **. You can use the Guardian God Host Master to install the IIS+ASP+ host system with one click.

First of all, it depends on what you use, the network of the electric imitation hidden communication is generally the backbone network of telecommunications, and there are other networks, but only the network of the power bureau guesses the letter is the most stable, and other networks can not be accessed, and it may be a problem with the network node.

1. Do not bind an IP

2. Don't enable directory browsing.

3. As long as the port mapping is fine, theoretically there is no problem, or the corresponding error will be reported.

4. You give everyone the permission to modify.