I install QNX Neutrino OS on VirtualBox and Momentics on Win.
My Win10 PC IP is 192.168.1.4 and QNX IP is 10.0.2.15
In VB i forward port:
TCP
Host-adress 192.168.1.4
Host-port 8000
Guest-adress 10.0.2.15
Guest-port 8000
I type "qconn" and did next -- first and second.
But command "ping 10.0.2.15" from cmd return "Request timed out."
And QNX Target in Momentics return "Not connected" to each my attempts.
Thank you in advance for your help.
P.S.-- Sorry for my English.
I change VirtualBox to VMWare with same .iso and it just work.
Related
I have ZorinOS 15 Lite as a Linux guest on my Windows 10 host machine.
The aim is to mount from my Windows 10 host to this Linux NFS server.
The NFS client setup on Windows 10 is done.
The NFS server setup on Zorin OS is done.
But still there are problems with mounting.
On Zorin guest nfs-kernel-server installed and edited /etc/exports/ file:
/data 192.168.0.0/24(rw,sync,no_subtree_check,insecure)
/data/ - the folder which I want to be shared between Win10 host and Zorin guest.
192.168.0.0/24 - share directory for IPs between 192.168.0.0 and192.168.255.255
Doing ipconfig I know this:
Windows host IP address - 192.168.1.66
Linux guest IP address - 192.168.56.1
When I'm trying to mount from Win10 host, I get this error:
C:\Users\Alibek Kaparov>mount -o nolock -o anon \\192.168.56.1\data I:
Network Error - 53
Type 'NET HELPMSG 53' for more information.
What am I doing wrong? I'm not experienced with NFS and VBox.
As it was pointed out in comments, thanks Mark Setchell, I changed IP address and mask to * pattern glob, copied IP address of virtual machine from it via ifconfig (not from Win10 host ipconfig) and could mount to it from host.
I've been following this guide https://medium.com/#pellea/using-adb-with-wsl2-7aebbb070a47 and so far have gotten to the point where WSL2 can see the emulator(s) running on Windows through Android Studios -> AVD manager. For example, on both Windows and WSL2, adb devices correctly shows:
List of devices attached
emulator-5554 device
However, when I go to my expo app and try to launch the Android emulator, I get the following error message:
Couldn't start project on Android: could not connect to TCP port 5554: Connection refused
This is after I've tried the following:
exporting ADB_SERVER_SOCKET=tcp:<MY IP>:5037 in my WSL2 profile(s)
Unblocking WSL2 vEthernet connections from my Windows firewall via (from the above link)
Set-NetFirewallProfile -DisabledInterfaceAliases "vEthernet (WSL)"
I've portforwarded 5554 from Windows to WSL2, as well as 5037 (from 0.0.0.0 to 127.0.0.1):
$WSL_CLIENT = bash.exe -c "ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'";
$WSL_CLIENT -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';
$WSL_CLIENT = $matches[0];
iex "netsh interface portproxy add v4tov4 listenport=5554 listenaddress=127.0.0.1 connectport=5554 connectaddress=$WSL_CLIENT"
The ports are as follows:
netsh interface portproxy show all
Listen on ipv4: Connect to ipv4:
Address Port Address Port
--------------- ---------- --------------- ----------
127.0.0.1 8081 172.25.38.171 8081
0.0.0.0 5037 127.0.0.1 5037
127.0.0.1 5554 172.29.149.0 5554
Just had the same issue with Expo.
Here is what fixed it for me:
Check for a process that uses port 5555 (Terminal)
netstat -ano | findstr 5555
Kill the process using its ID (PowerShell)
Stop-Process -ID [PROCESS_ID] -Force
Then it started working.
I had the exact same problem, but with a different setup (using Expo with the Metro bundler on a Mac). I worked around it by trying different virtual device images. Maybe the same can help you.
The virtual device that works with me so far is the one selected in this screenshot: https://i.stack.imgur.com/CFTJ0.png. The other two in the screenshot have the same problem. I don't really know the actual reason, must be something with port access with those other emulated devices.
Image details:
Name: 4 WVGA (Nexus S) API 29
API: 29
Target: Android 10.0 (Google APIs)
CPU/ABI (x86)
I'm sure other images work as well (or configuring the others somehow), i just haven't tried many more because it takes so long and they're so big.
Did you try to map port 5554 to Windows IP instead? (or localhost). The Android emulator is running on Windows, not WSL2, so the port proxy should be from WSL2 to Windows, not backwards.
Have you already solved it in another manner?
I have not had this problem in the past.
I have searched the internet but not found a solution.
I have asked the same question in Virtualbox forum but not received any answers.
I have the following setup
Host: Windows 10 (192.168.86.35), wired eth.
VirtualBox v6.0.16
Networking: Bridged Adapter
Guest 1: Ubuntu 18.04 (192.168.86.29)
Guest 2: Ubuntu 18.04 (192.168.86.26)
Both host and guests recieves IP from the same DHCP server and is on the same subnet.
Both host and guests can ping the DHCP server successfully or any WAN address for that matter.
The problem: However neither can ping each other.
Guest ping
avec#GUEST:~$ ping 192.168.86.35
PING 192.168.86.35 (192.168.86.35) 56(84) bytes of data.
^C
--- 192.168.86.35 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3050ms
Host ping
C:\>ping 192.168.86.29
Pinging 192.168.86.29 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.
Ping statistics for 192.168.86.29:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
What I have tried
Host: Turned Avast Shields off. There is no difference. I have not
tried to uninstall Avast it as I do not think this is the problem.
Guest: Condirmed Ubuntu firewall have "status: inactive"
Host: Repaired later reinstalled Virtualbox
Host: Started guest as Ubuntu Live cd. All is the same as running from the vdi (disk)
Host: Created a second Guest (cloned Guest 1 vdi)
Does anyone have any idea what the problem might be? I'm stuck.
I have found the solution and it had nothing to do with VirtualBox or the configuration/setup.
I had NordVPN installed and running as a background process on the host.
There is a setting in NordVPN called "Invisibility on LAN" defaulting to ON. That was the problem. As fast as I turned that setting to OFF host and guests could reach each other.
Turn 'invisibility on LAN' to OFF
I've searched docs for this but having no luck... Running VMware 8.5.7 for Mac, from the Windows guest I need to reach a port like 8888 that is available to my host (but actually running in VirtualBox on the host -- not sure if that matters but could be important to know.)
Any suggestions? There seem to be very few configuration options for VMware ports, or maybe I'm just looking in the wrong place.)
Thanks
I have laravel app which is running in my windows local server. This laravel app is running port:80. I want to load this app in my Ubuntu VirtualBox.
My IP Config:
IPv4 Address : 192.168.8.157
Subnet Mask : 255.255.255.0
Default Gateway: 192.168.8.1
I have config my virtualbox as Bridged Adapter. In my /etc/hosts (ubuntu virtualbox), I have this :
127.0.0.1 localhost
127.0.1.1 asus
192.168.8.157 v2.my.local
I have made a hello word app (node.js) in my local windows which is running on port :3000, and it is running in my VirtualBox by typing v2.my.local:3000, but if I type v2.my.local on my VirtualBox, it is not working (although app is running on windows local machine). it says:
This v2.my.local page can’t be found
Any suggestion? Thanks in Advance.
May be windows firewall blocking connections via port 80. turn off firewall and try it, if it works. Start windows firewall and add firewall rule to allow connections via port 80. If your windows version is 10 then, it will block all virtual box related connections. make sure to add correct rules.