I have just recently installed Genymotion and VirtualBox on Solus and when I start a virtual device y I get this error:
The connection to the virtual device has been lost.
Please restart the virtual device.
When I start the machine the screen loads but it's all in black and then I get that error.
I googled that and I found that I must reconfigure de Host-only network adapter but unfortunatly it didn't resolve the problem.
I also tried reinstalling virtualbox and genymotion but it didn't solve the problem.
Here's my log file: http://pastebin.com/CsdCJAw3 (I posted it in pastebin because it exceeds the characters limit here)
Thanks in advance
Are you running a VPN client like Cisco Any Connect. I was running it and Genymotion was continuously showing me the same issue. I just had to stop the VPN and close the VPN app if any.
Restart Genymotion and voila it connected.
You can start your VPN after that and it should work.
In case it still doesn't work. After stopping the VPN or if you're not running the VPN client before starting Genymotion try running this command.
This used to help me when something was causing an issue with the virtual box daemon.
sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart
Related
so i setup a centOS vm in VMware workstation, installed qradar..everything ran fine. I call this vm as QR1.
I was able to use qradar console on QR1 from my host machine, the internet works perfectly fine in QR1.
I make a full clone of QR1 called it QR2.
I boot it up and only running QR2 vm (QR1 is closed) but there is no internet on this vm. Even though all the network setting are same as QR1 and QR1 works just fine(i double checked).
QR2 has same adapter, same ip, same gateway and dns as of QR1 but it doesnt work...
previously i was thinking that i cannot have them both running at same time but QR2 just doesnt connect.
I am also not able to ping QR2 from my host and other way around.
What could be causing this ?
According to this vmware link reference, try these steps:
To change the MAC address of the Linux operating system:
Connect to vCenter Server using the vSphere Client Right-click the
virtual machine and click Edit Settings. Click Network adapter and
note the MAC Address.
For example, you see a MAC Address similar to:
xx:xx:xx:xx:xx:xx
1.Power on the Linux virtual machine.
2.Open a console and log in as root.
3.Change directory to etc/sysconfig/network-scripts.
4.Edit ifcfg-eth0 using a plain text editor and update the MAC address to reflect the MAC address in Step 3.
I face a problem that I can ping to correct IP address, it have no loss. And also I use nmap ping the pi address, and I get it correctly. Then I using VNC viewer to try access to pi, but it always show up "The connection was refused by the host computer"
Did u all have any idea ?
Your problem indicates that your Raspberry Pi was reached by the connection attempt, but that no service was running on the relevant port and hence the connection was refused. I think, this is because the VNC service is not running on your Raspberry Pi.
Update 1
Raspbian now comes with the server by default thanks to a partnership with RealVNC, it just needs to be enabled.
Original
You must enable VNC Server on your Raspberry Pi using terminal
sudo apt-get update
sudo apt-get install realvnc-vnc-server
or you can also enable VNC Server on the command line using the sudo raspi-config command.
Advanced Options->VNC:Yes
Now you can connect to the VNC Server using a application such as VNC Viewer.
I have been having this issue with my Raspberry Pi Zero W even though it worked perfectly beforehand. This page https://www.realvnc.com/en/connect/docs/raspberry-pi.html should help.
I ran vncserver in a ssh window after verifying the interface settings in raspi-config.
It started the VNC Server and gave me the VNC Server catchphrase and the IP address with Port Number as shown in the photo linked below.
vncserver output
After running that command I was able to get the VNC Viewer on my windows machine to connect to the pi.
I then ran sudo systemctl enable vncserver-x11-serviced.service in the ssh window so that it would start automatically on subsequent reboots.
I've had this same problem but found a different reason. I found three ways to get around this error message.
Plug a mouse or keyboard into the Raspberry Pi zero, waking up the screen and the VNC connection.
Wait about 5 - 10 minutes which is the amount of time for the screen saver to kick in which seems to wake up VNC connection. but don't wait to long other wise run this command to get things going via ssh "systemctl start vncserver-x11-serviced.service".
I am hoping the new update they just published will fix this problem. I don't see this as much with the Raspi B3+ as with the Zero H.
The last was plug in both monitor and mouse and that for sure fixes the VNC issues but defeats the headless connection. It seems that running headless and the screen/saver are somehow related but just not smart enough to figure it out.
For people using newer version of Raspberry, VNC option is found under:
Config>Interface Options
pinging to any service will only tells us that whether the server is currently listening on that port or not. It will not tell you the possible result to connection request asked by client.
It seems that, you have installed VNC server but not started it properly. Use this command to start it...
# vncserver start
Also recheck the port number is correct or not.
With the Rasp Pi 4 - had connecting fail after rebooting both the server and client (both Rasp Pi 4s).
Took a while to realize that I have two clients: One named "VNC Client", the other "VNC Viewer for Google Chrome".
The former works, the latter doesn't.
I'm following this article https://msdn.microsoft.com/en-us/library/windows/hardware/mt269367(v=vs.85).aspx and I've gotten to the step where you run the command to start WinDbg.
WinDbg –k net:port=50000,key=1.2.3.4
However, when WinDbg restarts it is stuck on "Waiting to reconnect..." and it shows "Debugee not connected" at the bottom. I've tried unplugging the Ethernet cable multiple times as well as restarting the target multiple times. I can also ping the host computer from the target. Oddly, I can't ping the target from the host.
The host machine is running Windows 7 and the target machine is Windows 8.
So I turned off the firewall on the host and it started to work.
I'm trying to do some local RDC testing using VirtualBox. The host is OSX.8, the VM is ubuntu, and VirtualBox is version 4.1.22.
The VM starts fine without any problems. I shut it down and choose "Enable Server" from the Remote Display section of the Display options and start again, and again it starts fine. Note that the port is left default and the authentication is "null".
I start Microsoft's RDC (v2.1.0) and type in 'localhost' and get: You were disconnected from the Windows-based computer because of network problems.
I try 127.0.0.1 and get the same error. Then I type in the IP of my (host) computer and get the same error. I know the loopback address avoids the firewall but I turned it off anyway and got the same error.
I get the same error whether I'm using NAT networking or bridged. What am I doing wrong?
I should note that this is a vanilla install of VirtualBox and I haven't added any extensions or guest additions or anything like that.
Seems I'm doing everything right. What am I missing? Thanks for the help!
Problem Solved! You have to install the "VirtualBox 4.1.22 Oracle VM VirtualBox Extension Pack" (available on the VB download page) to make RDC work. I wish it would tell you this when you click "enable server" but I guess that's asking too much. I hope this helps someone else.
I have an android emulator I'm running from eclipse and just trying to connect to a simple socket server I wrote in .NET (c#).
The server is running on the same machine on port 4505. I am able to telnet (through PuTTy) to the server and it works just fine, but when I try to connect to the server with the android emulator I get a: java.net.ConnectException - localhost/127.0.0.1:4505 - Connection refused at org.apache.harmony.luni.net error.
I'm assuming this is because the emulator is on a different subnet or something? If that were the case though I would think I would be getting a different error that would be caught in the UnknownHostException catch block...
According to Emulator Networking IP 10.0.2.2 should be used instead of localhost/127.0.0.1.
I got this figured out. If I use the internal ip it works fine (192.168.1.%) address.
Sorry for the wasted space here but maybe someone else will be able to use this.
the 127.0.0.1 is for the device (emulator) itself.
instead of 'localhost' put your address (192.168.1.%)