自托管集成运行时中的远程访问问题 [英] Remote access issue in Self hosted Integration Runtime
问题描述
我有两个VM A和一个. B. A-VM已成功安装自托管集成运行时.这个已经运行了一段时间(我没有安装它).
I have two VMs A & B. A-VM has successfully installed Self hosted integration runtime. This has been running for a while(I did not install it).
I tried to install a new VM and it fails on key registration . So I swapped the OS disk from successfully running VM. Then the difference I find is that B-VM has no remote access enabled, rest everything is the same as A-VM. Both VMs have private IPs and they both use the same Subnet and NSG.
(New-Object System.Net.WebClient).DownloadString("https://we.frontend.clouddatahub.net/")
当我在VM-A上运行它时,会给出正确的'403'
错误.
但是在VM-B上它给出"The underlying connection was closed: An unexpected error"
When I run this on VM-A it gives the correct '403'
error.
But on VM-B it gives "The underlying connection was closed: An unexpected error"
我仍然认为问题是VM-B没有启用远程访问,但是当两个VM使用相同的NSG + Subnet时怎么可能?两个NIC + NSG + Subnet上的有效安全规则也相同.
I still think the issue is VM-B is not enable for remote access but how is that possible when both VMs use same NSG+Subnet? Effective security rules on both NICs+NSG+Subnet are the same too.
我试图以此启用远程访问,但是它在命令提示符下给出了空白响应.
I tried to enable remote access with this but it gives a blank response on Command prompt.
Dmgcmd -era 8060
如何找出两个VM之间的区别?也许是微不足道的,但是VM-A使用DSVM映像(数据科学),而VM-B使用普通的VM映像,但是由于我交换了OS磁盘,所以它们都具有相同的DVSM.
How can I find out the difference between the two VMs? May be it is trivial but VM-A uses DSVM image(datascience) while VM-B used normal VM image but since I swapped the OS Disk they both have same DVSM.
推荐答案
由于VM无法发现URL,因此需要一个主机文件条目.
A host file entry was needed as the VM was not able to discover the url.
- X.X.X.X we.frontend.clouddatahub.net
- Y.Y.Y.Y ne.configuration.dataproxy.clouddatahub.net
这篇关于自托管集成运行时中的远程访问问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!