I'm on macOS Sierra, using VirtualBox 5.0.28 r111378, and my Ubuntu VMs frequently get connection reset by peer errors when making outbound HTTP calls via the NAT interface.
My use case often (but no exclusively) involves HTTP calls between the two; if I add an interface on the same virtual network then I don't get the issue. All the while they're using the NAT interface though, I get these very frequent connection resets. Updating the VMs I'm running doesn't seem to make any difference.
I had a very similar problem with VirtualBox 5.1.8 running on macOS ElCapitan as Host OS. Guest OS was Ubuntu 14.04. On https connections I got intermittent connection reset by peer errors. I could overcome the situation by switching from NAT to NAT Network in the settings for the network adapter of my VM.
Related
I have a virtual machine instance running on Google Cloud Compute Engine — a preemptible free-tier CPU running Ubuntu 17.04. The end goal is to connect it to a MongoDB running on my local machine, a 2015 Macbook Pro (OS 10.12.6). But first, I've been trying to ensure the VM can reach my Mac via ping.
Running ping <VM's external IP> from my Mac works.
pinging my Mac from another Mac on the same wifi network works.
Running ping <Mac's IP> from the VM via the browser terminal does not work.
I've disabled my Mac's firewall. I've also configured my VM's firewall rules to allow all inbound and outbound traffic, to no avail:
ingress firewall rules, egress firewall rules
How might I get this instance to ping my Mac successfully?
Does your Mac's IP address begin with 10., 192.168., or between 172.16. and 172.32.? These are private addresses only reachable within your Mac's local network, which is (part of) why GCE cannot reach your VM.
This is part of a very common configuration. An ISP only allocates one (or a small number) of IP addresses to your home or business. A router on the network performs NAT to share that IP addess between computers on the local network, which instead use private IP addresses for themselves. As the router doesn't know what to do with the inbound MongoDB traffic, it blocks it.
There are two common ways around this that are usually found in your router settings:
"port forwarding" where you tell the traffic to forward all traffic on port 1234 to your Mac. This can get MongoDB working, but not ping.
If you have whole extra IP addresses, "DMZ" where your router directly forwards an entire extra IP to your instance. If you have only one IP address this is not an option as that IP is needed to be shared for other devices on the Wifi.
You likely also have a firewall on the router. If you use a DMZ or port-forwarding you must make sure that firewall allows traffic through too.
That said, I'm not sure that this is a sensible thing to do. Opening up your local network to the internet can create major security issues, plus it is likely unreliable more expensive (free tier only provides 1GB egress/month, your db traffic could exceed this).
Actually running MongoDB on instances within GCE is almost certainly a better option in every regard for you.
I am using VMWare. I am using a default NAT setting. I am unable to ping to an external url from within the guest OS. The firewall on the host Windows OS is the Symantec Endpoint Protection and I have created some firewall rules for allowing network traffic on ports 22, 80, 53 etc. I am still unable to ping.
I tried changing the network setting to Bridged but then starting the VM os gives an error message 'Connectivity issues detected'
Can someone help?
I reimported the image and started the VM guest it seems it is working fine.
I tried to install my broker and the broker mosquitto in Google virtual machine but I can not connect with my machine.
I searched for several days the answer, but it still fails.
Already allowed the port 1883 on the server and have also tried disabling the firewall.
The question is whether it is possible to install a MQTT broker on Google Cloud so that accepts publications and subscribe to my local machine or other device?
if yes, what should I do?
If you tried to disable your local firewall, that shouldn't be a problem, since any outbound connections are usually enabled by default.
If you tried to disable remote machine firewall, that is not enough, because there's Google Cloud network firewall in front of your VM.
Configure their firewall to allow incoming traffic to your port, TCP protocol. See https://cloud.google.com/compute/docs/networking
Note how you cannot disable network firewall, because it's a really bad idea. Instead you should configure your firewall to allow certain traffic and reject everything else.
I've installed pfsense 2.3 x64 in virtualbox with 2 adapters; One is bridged to my wifi adapter (adsl modem) (WAN) and the other one set as'Internal network' ('intnet') (Lan);
The problem is that although pfsense can automatically detect dhcp over first adapter and get an IP but my system (the host) can not ping the pfsense server (pfsense can ping both adsl modem gateway and the host).
Note1: Disabling the antivirus and firewall (kaspersky internet security 2016) has no effect.
Note2: I know that this setup works because I use the exact same network configurations for a Kerio Control server (v9.0.2, installed in virtualbox)
Note3: If I constantly ping pfsense server in my host (ping 192.168.1.102 -t) and at the same time restart pfsense server, during the booting phase of pfsense I can get two pings!
After contacting the pfsense official forum, it turned out that the WAN interface blocks everything by default. Therefore, either a rule should be defined to allow WAN to accept traffic or access server from LAN side.
I figured this out without having to go through the WAN interface, answer is on the pfsense forum
Configure host-only network "vboxnet1" (or any of the other host-only networks if you're already using vboxnet1 for other VMs) with the following:
192.168.1.77 (or whatever IP you want your host to appear as on the network)
255.255.255.0
DHCP Disabled
The make sure that the LAN adapter on your pfSense VM is a "Host-only Adapter" and that it's using "vboxnet1" (or whatever network you configured above)
Reboot/re-install and http://192.168.1.1 should work now
I have a windows server 2003 as the guest in VMware player and windows 7 enterprise as the host. I'm trying to connect to the inernet from my guest and i can't. In my VMware player virtual machine settings my network addapter is set to NAT but i can't get it to work.My host is in the work LAn and connected to the internet through it. Could this have something to do with it not working properly? Do I have to perform some special setup?
The problem may be caused by:
You're NATting to the wrong host's network interface in the VM's option.
Your VM's NIC DNS configuration is wrong. To verify this issue, try to PING the host's NIC from the VM.