Let me make sure something clearer. You servers act as if they are physically seperated from your host. So with that in mind they need to be setup the same way as if they were seperated. That means that they need a route in their routing table. Why? Because right now their default route is to the internet via your gateway, NOT your host.
In short, approach the problem the way you would if they were not VM's and they were real servers on your network.
But as I aksed in my initial repsonse, Are they like VMWare bridged adapters. If they are what I say stands. If they are not, then thats a different story. FOr example, if they are setup in a NAT with your host, VPN should already work. Any other situation will require further investigation and more information.
Setup some routes in your routing tablke. It really depends on how its setup but if you can access your corp network fine on the host, then setup the routes in your vm machines.
Also, as I am not familiar with that VM, are the network adapters like VMWares bridged adapaters? If so you need to setup the route to route to your host.
就像我说的,你需要设置一些路线。 通过您的主机作为网关添加到您的公司 LAN 的路由。 仅凭您告诉我它从家庭 DHCPP 获取的事实就告诉我这就是问题所在。 您的虚拟机只能看到 1 个默认网关,即通往互联网的网关。 虚拟机根本不知道主机上有 VPN。 添加该路由(在 VM 计算机上)会导致 VM 向公司网络的子网发出的任何请求都通过您的主机而不是家庭路由器进行路由。
在您的虚拟机上添加如下内容:
route ADD 10.0.0.0 MASK 255.0.0.0 192.168.1.30
将执行以下操作:对 10...* 网络发出的任何请求都将通过 IP 地址为 192.168.1.30 的计算机进行路由。 因此,将 10.0.0.0 和子网替换为您的公司 LAN,并将 192 ip 替换为您的主机 IP。 这应该可以解决这个问题。
Like I said you need to setup some routes. Add a route to your Corp LAN via your Host as the gateway. Just the fact alone you telling me that it gets it from home DHCPP tells me that is the issue. Your VM's only see 1 default gateway, and that is to the internet. The VM's have no idea whatsoever that the Host has a VPN on it. Adding that route (on VM machines) causes any requests that your VM's make to the subnet of your corp network to route through your host rather than the home router.
Adding something like this:
route ADD 10.0.0.0 MASK 255.0.0.0 192.168.1.30
on your VM'S would do this: Any requests made to the 10...* network would route through the computer with the IP address of 192.168.1.30. So replace the 10.0.0.0 and subnet with your corp lan, and the 192 ip with your hosts IP. That should take care of the issue.
发布评论
评论(4)
让我确定一些更清楚的事情。 您的服务器就像在物理上与您的主机分离一样。 因此,考虑到这一点,它们需要像分开一样进行设置。 这意味着他们的路由表中需要一条路由。 为什么? 因为现在他们的默认路由是通过您的网关访问互联网,而不是您的主机。
简而言之,如果它们不是虚拟机而是网络上的真实服务器,请按照您的方式解决问题。
但正如我在最初的回答中所询问的那样,它们是否像 VMWare 桥接适配器一样。 如果他们是我所说的那样。 如果不是,那就是另一个故事了。 例如,如果它们与您的主机一起设置在 NAT 中,则 VPN 应该已经可以工作。 任何其他情况都需要进一步调查和更多信息。
Let me make sure something clearer. You servers act as if they are physically seperated from your host. So with that in mind they need to be setup the same way as if they were seperated. That means that they need a route in their routing table. Why? Because right now their default route is to the internet via your gateway, NOT your host.
In short, approach the problem the way you would if they were not VM's and they were real servers on your network.
But as I aksed in my initial repsonse, Are they like VMWare bridged adapters. If they are what I say stands. If they are not, then thats a different story. FOr example, if they are setup in a NAT with your host, VPN should already work. Any other situation will require further investigation and more information.
在路由表中设置一些路由。 这实际上取决于其设置方式,但如果您可以在主机上正常访问您的公司网络,则可以在虚拟机中设置路由。
另外,由于我不熟悉该虚拟机,网络适配器是否像VMWares桥接适配器一样? 如果是这样,您需要设置路由到您的主机的路由。
Setup some routes in your routing tablke. It really depends on how its setup but if you can access your corp network fine on the host, then setup the routes in your vm machines.
Also, as I am not familiar with that VM, are the network adapters like VMWares bridged adapaters? If so you need to setup the route to route to your host.
您使用什么类型的 VPN? 您使用的是内置的 Windows VPN 客户端,还是必须安装客户端?
您可以在每个虚拟机上独立设置 VPN 客户端,前提是允许多个同时连接。
我认为设置路由不起作用,因为那样您还需要在公司网络上设置路由。
What type of VPN are you using? Ar you using the built-in windows VPN client, or do you have to install the client ?
You could just set up the VPN client independently on every VM, providing you are allowed multiple simultaneous connections.
I don't think that setting up routes would work because then you will also need to set up routes on your company network.
就像我说的,你需要设置一些路线。 通过您的主机作为网关添加到您的公司 LAN 的路由。 仅凭您告诉我它从家庭 DHCPP 获取的事实就告诉我这就是问题所在。 您的虚拟机只能看到 1 个默认网关,即通往互联网的网关。 虚拟机根本不知道主机上有 VPN。 添加该路由(在 VM 计算机上)会导致 VM 向公司网络的子网发出的任何请求都通过您的主机而不是家庭路由器进行路由。
在您的虚拟机上添加如下内容:
将执行以下操作:对 10...* 网络发出的任何请求都将通过 IP 地址为 192.168.1.30 的计算机进行路由。 因此,将 10.0.0.0 和子网替换为您的公司 LAN,并将 192 ip 替换为您的主机 IP。 这应该可以解决这个问题。
Like I said you need to setup some routes. Add a route to your Corp LAN via your Host as the gateway. Just the fact alone you telling me that it gets it from home DHCPP tells me that is the issue. Your VM's only see 1 default gateway, and that is to the internet. The VM's have no idea whatsoever that the Host has a VPN on it. Adding that route (on VM machines) causes any requests that your VM's make to the subnet of your corp network to route through your host rather than the home router.
Adding something like this:
on your VM'S would do this: Any requests made to the 10...* network would route through the computer with the IP address of 192.168.1.30. So replace the 10.0.0.0 and subnet with your corp lan, and the 192 ip with your hosts IP. That should take care of the issue.