I am running two vms:
One is a linux webserver
The other is windows 7 used for testing purposes
I can easily forward traffic from my host machine to the webserver using the vmnet8/nat.conf configs.
I need localhost web traffic on the windows vm to go to my linux vm, but nothing is apparent.
Any ideas?
Just put the network cards on both VMs on bridge. Then both VMs can see each other like classic network :)
Related
I created a Server 2019 VM in Azure and want to use nested virtualization. On the 2019 VM, I created a Windows 10 VM in Hyper-V. The problem is that the Windows 10 VM does not have internet connection. Even though a virtual switch was created on the 2019 VM, the nested Windows 10 VM is not able to reach the Azure gateway.
Here's the Server 2019 Network settings
This is the Hyper-V Switch
And finally this is the Windows 10 VM network settings. It never gets an IP address from the host and even when assigned a static IP it cannot route to the gateway. What am I missing?
The overall problem I'm trying to solve is to have Apache Guacamole able to connect to nested VMs, which isn't possible with NATing.
You cannot reach the internet because your default gateway is blank.
You are getting auto configured IP addresses without default gateway (169....) (probably) because you do not have a DHCP server.
You can configure the DHCP server on the Hyper-V host running in Azure
or on a nested Hyper-V VM if needed.
see: https://www.nakivo.com/blog/hyper-v-nested-virtualization-on-azure-complete-guide/
I successfully set up nested virtualization in Azure. Using NAT port forwarding, I can RDP to the guest VMs without any issue. For us, this is not a complete solution as we need to access the guest machine (just on the internal network) by machine name not just through a unique port for each machine. For example, if I have a guest VM called guest1, I should be able to launch explorer and go directly to \guest1\c$ (from not just the host, but from outside the host as well) just as would able to if guest1 were a non-nested VM. All we can do right now is RDP to guest1, that too through a unique port, so guest1:port1 for guest1 and guest2:port2 for guest2.
Is this possible? Thanks in advance!
PS: I followed the instructions here (very useful): https://www.thomasmaurer.ch/2017/07/how-to-setup-nested-virtualization-in-microsoft-azure/
I have IIS running in Windows 8 in a VM on my Mac. With the Networking set to Bridged mode I can access IIS from my Mac using the IP address. This works fine when I'm connected to my network.
What I need to be able to do is access IIS from my Mac when there is no network connection available, and I can't figure it out.
Background: This is so that I can demo a web app to clients in situations where I have no 3G coverage and they don't have wifi I can connect to.
Turns out you need to go to Virtual Machine -> Network Adapter -> Network Adapter Settings, then select Private To My Mac.
The VM won't be able to connect to the internet, but your Mac should be able to connect to the VM on the IP that it's assigned, even when there's no internet connection.
Remember to add rules, or turn off Windows firewall in order to let traffic through to IIS though.
I am running a virtual machine using VirtualBox and I'd like the virtual machine to able to access a site that is hosted in IIS on the host machine (my computer).
How is this possible?
Give your VM networking capabilities, connecting to the same network as the host machine will allow the two to communicate / allow you to browse the site from the VM.
http://www.virtualbox.org/manual/ch06.html
I'm new to Azure (strike 1) and totally suck at networking (strike 2).
Nevertheless, I've got two VMs up and running in the same virtual network; one will act as a web server and the other will act as a SQL database server.
While I can see that their internal IP addresses are both in the same network I'm unable to verify that the machines can communicate with each other and am sort of confused regarding the appropriate place to address this.
Microsoft's own documentation says
All virtual machines that you create in Windows Azure can
automatically communicate using a private network channel with other
virtual machines in the same cloud service or virtual network.
However, you need to add an endpoint to a machine for other resources
on the Internet or other virtual networks to communicate with it. You
can associate specific ports and a protocol to endpoints. Resources
can connect to an endpoint by using a protocol of TCP or UDP. The TCP
protocol includes HTTP and HTTPS communication.
So why can't the machines at least ping each other via internal IPs? Is it Windows Firewall getting in the way? I'm starting to wonder if I've chose the wrong approach for a simple web server/database server setup. Please forgive my ignorance. Any help would be greatly appreciated.
If both the machines are in the same Virtual Network, then just turn off Windows Firewall and they will be able to ping each other. Other way is to just allow all incoming ICMP traffic in Windows Firewall with Advanced Settings.
However there is a trick. Both the machines will see each other by IP Addresses, but there will be no name resolution in so defined Virtual Network. Meaning that you won't be able to ping by name, but only by direct IP address. So, if want your Website (on VM1) to connect to SQL Server (on VM2), you have to address it by full IP Address, not machine name.
The only way to make name resolution within a Virtual Network is to use a dedicated DNS server, which you maintain and configure on-premises.
This article describes in details name resolution scenarios in Windows Azure. Your particular case is this:
Name resolution between virtual machines and role instances located in
the same virtual network, but different cloud services
You could potentially achieve name resolution, if you put your VMs is same cloud service. Thus you will not even require dedicated virtual network.
If your VMs are inside a Virtual Network in Azure, then you have to make sure two things.
Required Port is enabled.
Firewall is disabled on the server.
I was trying to connect to one VM where SQL Server DB was installed, from another VM. I Had to enable 1433 port in the VM where SQL was installed. For this you need to add an MSSQL endpoint to the VM on the azure management portal. After that i disabled windows firewall. Then i was able to connect to the VM from another.