I have a virtual machine on VMWare Workstation with Windows Server 2008 R2.
There are some not admin users. They have to have an internet access for theirs work (for example, to use SVN, Maven and so on). But at the same time, I have to close access to the Network for them.
What i have already tried:
I've tried to turn off network discovery in Network and Sharing Center. But it disables network only via gui(explorer), so users still can access other devices like that \\SOME_MACHINE_PC. More then that, users (which are even not admins) can change back this option in Control Panel.
I've tried to edit registry, adding such configuration:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Network]
"NoEntireNetwork "=dword:00000001
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"NoNetHood"=dword:00000001
But it have not changed anything at all.
I've tried to change Network Adapter config in WMware to Host-only: A private network shared with the host.
But this turns off internet.
So, is there any other variants?
You can create an extra subnet for the VM, and don't route from this subnet to the company network.Then you can access the VM via the Host System (I am doing it via vnc). When the VM doesn't need access to the host network, it should work.
If the VM needs access to the company lan:
You could create a second VM for the internet only use, and use the existing VM for its current purpose.
Related
I am running a Hyper-V lab for a client to test the functionality of a Powershell script and due to memory constraints, I would like to move my file and database VM servers off of my main desktop PC to my laptop. I set up Hyper-V on the laptop, and successfully exported/imported the VM's into the other Hyper-V server. I can boot them, all the configuration and files are intact however, I am predictably having trouble reconnecting to the domain they were a part of prior to the move. I understand I need an External virtual switch to handle that communication, as internal and private will not reach outside of the Hyper-V server they reside in. Obviously I would prefer to not use an external, but this is strictly to continue testing. I've trouble-shooted entering different DNS server values from the client machine's IPv4 properties and changing the virtual switch to External for the existing Hyper-V server, and re-register the DNS records on the DC. All result in the same error when I try to connect to the domain: "(error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc."... "The DNS SRV records required to locate a AD DC for the domain are not registered in DNS".
In summary, I want to move a VM from the first server listed to the second, and then re-connect to the domain they were part of previously. Both machines are just running Windows 10, not Windows Servers, if that matters. Another note, I can do remote sessions from the desktop to the laptop just fine which would lead to believe this is not related to a firewall. Thanks!
The best it to set up a VLAN. If you can't do that, change the network class of your AD lab machine (192.168.55.x ?) to another in order to avoid conflicts.
Your DNS server has to be AD to make your machines connecting to it.
And last but not least, if you're on 2 different hyperV servers, you have to use external switch in hyperV:
https://redmondmag.com/articles/2018/05/04/hyper-v-private-networks.aspx
I've set up Windows Server VM instance on GCP. I've set up a static IP for that server and I'm able to remote desktop in without problem using the inside IP address as I have a VPN connection between my on premesis network and my GCP network. On the Windows Server, I've set up a sharing folder with the proper permissions.
Now, on my local PC running Windows 10, I'm trying to map a network a drive to that shared folder on the VM. What's the correct path to specific it to map to? I tried \\ but it doesn't work.
I have enabled network discovery, checked all firewall rules and enabled file and print sharing.
I can ping from my local pc to my Windows VM instance.
Thanks in advance
I have opened up the following ports on GCP Network:
tcp-access Ingress Apply to all IP ranges: 192.168.84.0/24
tcp:135-139
udp:445
Still unable to access.
I thought by default google had all ingress ports open on the local IP?
I checked the firewall on the server and everything is open as well.
Thanks in advnace.
I'm using a Windows Server 2019 server from Microsoft Azure. I have installed Hyper-V with the management tools and am now trying to setup a Ubuntu 14.04LTS VM inside of Hyper-V. I create a new External Switch however when setting up the Ubuntu instance there it tells me that there is an issue with the DHCP server. When I check my network connections for the newly created switch there is IPV4 connectivity, with packets being sent and received.
Things that I have tried:
-Ensured that inside of the Virtual Switch Manager that in my newly created virtual switch, the external network is selected as my main internet adapter. And that the "Allow management os to share this network adapter".
-Tried selecting "Internal Network"
-Inside of the ubuntu server, tried dchlient -r and dhclient eth0 to try to retrieve a new IP (For internal network this has worked, but without internet access, for external ip it hangs on the command dhclient eth0)
-In Network Connections I have tried bridging the two connections (out of desperation, "bricks" the vps causing me to not be able to rdp, must create a new azure vm)
-I have tried right clicking the main "ethernet" inside the Network Connections and allowing sharing options to other users.
Please help as I'm quite lost as to why the Ubuntu Guest is not connecting to the internet with the new network switch
The virtual switch connection types are very confusingly named, and sharing is somewhat flaky. I've had best results with the Internal Network. Most of the time it just works but there are certain situations when the NAT service breaks and you will have to restart some combination of the host and guest machines, possibly both -- I've not found a way to just restart the virtual switch service without restarting the host OS.
If you need to use the External Network type, be aware that your actual physical router will be in the mix, so you must make sure that it is properly configured, especially if you're doing MAC filtering on your router and the guest is not using the hardware MAC. This usually happens because of the virtualisation process itself, even if it's not something you've configured in the guest.
I am trying to rdp from my local mac to an Azure instance through a (IKEv2) vpn connection. I am never prompted for a password, and it looks like the connection just times out. The error code I get is 0x204.
I have tried using both Microsoft Remote Desktop 8 and 10 for mac.
The connection is active and reports that it is connected.
From the mac, I can connect to another VM (in the same azure account) which is not running behind a vpn.
From Parallels Desktop (with networking set to Shared mode and the vpn connection active on the mac), I can successfully connect using the windows rdp client.
So it seems the Microsoft RDP-client for mac is not using the vpn connection.
Is there a way to make it do so?
Is there another solution, that will allow me to rdp to an Azure VM from my mac (without going through Parallels)?
Note: This is not the same question as this, since that is not about going through an azure vnet gateway.
I needed to add hosts file entries for each azure site I needed to access.
For example for accessing my-vm-name.someregion.cloudapp.azure.com, I needed to add a hosts file entry for it's private IP within the subnet. E.g. 10.2.0.100.
The reason everything worked in Windows under Parallels, is that the relevant entries had already been added to the hosts file previously.
I'm current using Xammp,and have created a website in the htdocs. I want to know if i can access this from another computer (not in the same network) and work on the site from that other computer.
You can do this by using the dynamic dns service provided by noip.com. Download the noip client and setup an account in it (try Googling on it).
After that you must edit the conf files in XAMPP to allow outside network to communicate with your network.