I have a problem configuring RDP. This is the situation:
PC1 (host): Windows 10 Pro with Hyper-V
The guest-VM is Windows 10 Enterprise
I also have another PC in the WLAN, a FritzBox router and an external PC in the internet.
The routers external IP is mapped through dynDNS.
On the router I have forwarded TCP port 3389 to the host PC1.
Host PC1 has one active WLAN adapter. It has a 2nd LAN adapter that is not connected and disabled.
The guest VM has internet access through the default internal switch of Hyper-V, that is not configurable an uses the WLAN adapter. The WLAN adapter is configured for shared connections. A second (external) switch can't be configured with Hyper-V, as the only active adapter is already used by the default switch.
All systems have RDP enabled, port 3389 open, and network discovery enabled. They all belong to WORKGROUP. A domain is not configured.
I can open the following RDP sessions:
from host PC1 to the guest VM
from PC2 to PC1
from the external PC via internet to PC1
What doesn't work and what I need to configure:
from WLAN PC2 to VM guest on PC1
and, most importantly:
from external PC to VM guest system in PC1.
What is wrong or missing?
Solved:
Choose a port number (10000) an verify that it is not used on the host PC1:
netstat -anp TCP
Open incoming port 10000 in firewall on PC1
Forward incoming traffic on host WLAN adapter 192.168.0.29:10000 to internal IP 192.168.162.151 of virtual adapter of the VM
netsh interface portproxy add v4tov4 listenaddress=192.168.0.29 listenport=10000 connectaddress=192.168.162.151 connectport=3389
Configure (FritzBox) router to forward incoming traffic for port 10000 to the host 192.168.0.29:10000
Now I can connect on host:10000 directly with RDP to the VM
Related
I want to make genymotion's android phone's internet to work with tor proxy.
I added
Proxy server: 127.0.0.1:9150 - To access Tor port
Rule player.exe with 192.168.58.* port with Virtual Box only network action. To isolate genymotion -> virtual box communication.
Genymotion's phone runs correctly, but without internet. How should I route 5555 wifi port for adb.exe to access internet? Got 10049 error from Proxy SOCKS5 127.0.0.1 via Virtual Box host-only network.
Currently I have an Ubuntu VM that is set up with an internal network virtual switch, that is connected via ICS Internet Connection Sharing with the host's Ethernet connection. This puts the VM on a 192.168.137.xxx internal NAT IP address and I can't connect to PCs in the host LAN with 192.168.0.xxx IP addresses. I need to be able to connect to 192.168.0.50:9182 for Prometheus data, from 192.168.0.49's internal NAT address of 192.168.137.15 for example. I cannot ping from the VM to the target IP, how do I accomplish this?
Use Bridged Adapter
Then your virtual machine will get its own IP on the local network.
I've been searching around and found no similar issues have been asked.
My desktop (windows 7) is in LAN, has IP (192.168.3.121).
I installed vmware (windows 7), using NAT connection (172.168.174.128). The guest is able to access internet without problem.
In guest, if I "ping 192.168.3.121", this will be ok.
If I "ping 192.168.3.xxx", will also be ok.
If I "ping 192.168.174.2" (DNS), this will be ok.
If I "ping 192.168.174.1", can't ping.
Note my host Vmnet8's ip is indeed 192.168.174.1. Ping from host also doesn't work.
From host:
"ping 192.168.174.128" (guest IP), does not work
"ping 192.168.174.2", does not work
Both host/guest windows are installed without any other "security/defender/firewall" related softwares.
Anywhere can go wrong?
Thanks.
If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host, or anywhere else for that matter, without configuring port forwarding for that virtual NAT network.
If you would like to be able to access your VM from your host you can either:
A) Change the mode of the network adapter for the VM to a bridged adapter. This will make the VM act as if it is just another computer on the same network your Desktop is and will be accessible at an IP such as 192.168.3.122
or
B) Add a Host-Only network adapter to the VM. This second NIC will be connected to a network that has no internet access, but is connected to the host and any other VMs on the same host-only network
Also, check the firewall settings to allow inbound ICMP inside the VM.
You mean that you cannot ping to the VMnet8 interface of your physical PC.
Maybe it is not activated.
It should be activated first by issuing the command at the cmd prompt with the admin's privilege.
C:\Windows\system32>netsh interface set interface name="VMware Network Adapter V
Mnet8" admin=ENABLED
I have seen this issue with two different windows 10 machine & two different version of vmware workstation ( 15 & 16).
One way it works is I start the wireshark & under capture options I select on VMWARE8(default for workstation/need to adjust according to your NAT Interface) & than start ping from My Local Machine to NAT IP of the VM .
It takes time but it works. I do not what triggers this .
My initial thought was it's one of the Windows 10 upgrade but with two different version of windows 10 & this old issue resurfaced.
Navigate to "Control Panel\Network and Internet\Network Connections".
Disable and Enable the VMware Network Adapter VMnet8 and try again.
I was having same problem after the latest release of VirtualBox-6.1.6-137129-Win update. "NAT Network" on any of the guest machine was not working. So i downgraded my virtual box version to 6 and works fine with all my VMs but problem remains in Kali Linux.
NAT Network was successful in giving IP to kali machine but Internet was not working. Problem i found was somehow gateway of kali wasn't set. Then i configured both Gateway and DNS manually and it worked for me.
Make sure that you Uncheck the option "Use this Connection only for resources on this network."
Kali manual configuration for IP, DNS and Gateway
i'm working on an academic project (nothing professional) and wonder if i can set a rule that will permit me to redirect my local ip address to my virtual machine address, the virtual machine is an HTTP server, so i need to check my website from other computers on the same network, in other computers i will write the IP of my server computer(containing a vm) and then that IP will be translated to my vm IP.
From the host machine you could use the following Netsh command under cmd with administrator privileges:
netsh interface portproxy add v4tov4 listenport=80 connectaddress=192.168.0.10
providing that the vm IP address is 192.168.1.10 (replace with the actual one and make it static), the HTTP server is on port 80, and IPv4 is used.
After successful entry you may confirm the rule by using the following command:
netsh interface portproxy show all
For more information you may consult the following link:
http://technet.microsoft.com/en-us/library/cc731068(v=ws.10).aspx#BKMK_1
Two options:
1) Use a bridged NIC. The VM will have an IP address in the same subnet as the host machine, assuming DHCP is active. That's the simplest.
2) If VMware Workstation, attach the VM to the NAT switch. In Network Configuration you can then port forward so when your host IP receives traffic on port X it can forward that traffic to NAT client IP port X (or Y). I can't remember if VMware Player has NAT port forwarding.
I have windows server 2012 installed on a VM along with windows 8 to do DHCP lab (I am new to networking), but the server cannot assign an IP address to windows 8.
I am using a wireless router.
In the server's powershell, I type ipconfig /all to see my IP address and subnet mask and my default gateway,
which is IP address:
10.0.2.15 255.255.255.0 10.0.2.2
I went to network to set static IP address the same as above and the preferred DNS server is 10.0.2.15.
Then I create a DHCP range: 10.0.2.100 to 10.0.2.200 and DNS server is and I can see my scope in the DHCP view.
I boot up windows 8 on my VM to see it works.
I go back to server to refresh the address release but nothing happens.
In windows 8 , I command prompt the ipconfig /all
Ipaddress : 10.0.2.15 (which is server address?) subnet mask: 255.255.255.0 default gateway: 10.0.2.2 DNS server : 192.168.1.1
What am I doing wrong? Is the problem with my DNS configuration?
Hmm...It's not quite clear what steps you took to set up your server :(.
Exactly why is your DNS server (192.168.1.1) in a different Network? Are you using a relay Agent?
I will assume you have already installed DHCP server role and feature and
hence have DHCP manager up and running.
Go through the checklist below.
did you activate the scope?
did you specify the domain name server (006) IP and Router (003) IP?
did you check the 'Address Lease' column to see if DHCP is leasing any Add?
did you make sure DHCP guard is not enabled?
Install Network monitor to view DHCP transaction between Client and Server.
You should try runnning ipconfig /release and ipconfig /renew on client instead of server.
The site link below might also help.
https://technet.microsoft.com/en-us/library/hh831538.aspx
Since DHCP server is using broadcast method to release IP address, you might run into the situation where you have more than 1 DHCP server in your network. Run the IPCONFIG /ALL again to make sure you got the IP from the right DHCP server.