SCVMM client-to-Virtual Machine Communication Mechanism Summary

A problem occurred a few days ago. In the external network, the virtual machine in SCVMM in the Intranet is accessed through the portal self-service and cannot be connected. The system prompts that the IP address cannot be resolved. As a result, I want to discuss it with each other.

First, let's talk about the role of the SCVMM portal autonomous service. The installation method is not described.

The Virtual Machine Manager self-service portal is a website where you can create and operate your own Virtual machines in a controlled environment. Using the self-service portal, the self-service user can only view their own virtual machines, and can only perform operations permitted by the user role associated with the virtual machine.

 

There are no installation problems, but the following problems may occur during running:

Problem 1: The system prompts that the address of the hyper-v host cannot be resolved.

650) this. width = 650; "style =" background-image: none; border-bottom: 0px; border-left: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; border-top: 0px; border-right: 0px; padding-top: 0px "title =" image "border =" 0 "alt =" image "height =" 249 "src =" http://www.bkjia.com/uploads/allimg/131228/03140GW6-0.png "/>

Solution: we all know that you can add domain name resolution to the hosts file. Do not explain.

Problem 2: The certificate is faulty. It is not a trusted Certificate and cannot be connected. See:

650) this. width = 650; "style =" background-image: none; border-bottom: 0px; border-left: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; border-top: 0px; border-right: 0px; padding-top: 0px "title =" image "border =" 0 "alt =" image "height =" 405 "src =" http://www.bkjia.com/uploads/allimg/131228/03140K600-1.png "/>

According to the situation, it is not possible to import the certificate to a trusted organization. However, in actual conditions, N import operations are performed, but it is still not possible. I do not know what the situation is, however, this situation is divided into several situations:

1. In the Intranet, that is, it is the same network segment and is not added to the domain. On the Windows xp client, you need to change the Registry to log on to the portal and allow the network identity to log on.

2. In the Intranet, it is also the same network segment, not added to the domain, Windows 2003 client, failed access, should be the same as Windows xp, You need to enable Network Authentication, but do not know how to enable.

3. In the Intranet, the IP address range is the same. If the IP address is not added to the domain, the Windows 2008 client can be accessed successfully and the connection is normal without any changes.

4. On the Extranet, all appeals fail.

 

In view of the above problems, we have conducted multiple tests and can understand as follows. Through the independent portal service, two access methods are provided when accessing internal virtual machines, one is normal Remote Desktop, that is, access port 3389 through an IP address for remote access. The other is access through a program through the scvmm internal mechanism, without setting the internal virtual machine IP address, which can be accessed. This situation is more suitable for users who need to provide external services and allow customers to create their own virtual machines. That is to say, the second method serves the same purpose as the SCVMM console.

 

After learning about the above, the problem arises. There is no problem in accessing through the console, but the hyper-v host address can be resolved. Why cannot I connect to an internal virtual machine?

 

Question 2 has not been resolved yet. I hope you can give me some advice on this blog. I also hope that the project has been set up successfully or the test environment has been tested.

This article is from the blog, please be sure to keep this http://beryung.blog.51cto.com/6235304/1068582