Scenario:
Windows 10 Virtual Machine hosted using Parallels on MacOS Catalina
Azure VPN - Basic SKU
Shared Network setup using Parallels
I can successfully connect to the Azure VPN using a Point-to-site connection from the Windows 10 installation.
Problem: I would like to use the VPN connection (established by Windows 10 VM) with macOS Host. Is this possible?
I have tried adding a static route on Mac OS as below, where 10.200.0.0/16 is the Azure Network CIDR, and 10.211.55.6 is the IP address of the Windows 10 VM on Parallels.
sudo route add -net 10.200.0.0/16 10.211.55.6
But this does not work. Any suggestions, or is there no way to share the VPN connection even with custom routing configuration?
Note. I understand that you can connect to Azure VPN from MacOS using the Standard SKU of Azure VPN, but would like to see if it is possible without.
Related
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.
Set up is:
Windows 10 Pro 64 bit
All Hyper-V and Container features turned on
Full Sql Server, standard port 1433
Visual Studio 2017
Docker Community Edition Version 18.03.1-ce-win65 (17513)
Stock Windows 10 Firewall rules and security Polices
No additional anti-virus or security
I built a POC .net core 2.1 service in VS2017, added docker support. For test purposes I am trying to connect to the Sql Server from the service. I understand it runs in its own private network. When I run the service as a standalone outside of docker, it connects to Sql fine, so all that is working. Inside of the container it can't connect. I'm specifying the IP of vEthernet (nat).
If I turn off Windows Firewall, then it can connect. When I turn on firewall logging, I can see the packets are being dropped.
In network and sharing, my PC appears in the Network / Private Network group and the vEthernet (default switch) and vEthernet (nat) appear in the Unidentified / Private network group. Access type is No network access.
My PC is connected to the internet via a wi-fi router, so I don't want to open up a big fat security hole, but I'd like the container to be able to connect.
I can't specify the IP of the container since that is dynamic.
How should I set things up to let the containers connect to the Sql?
Maybe, Hyper-V is not connected to the local sever. Open Hyper-V Manager and connect to server...
I am trying to mount a drive on my local on-premises Windows 10 pro machine (SMB 3.0).
I setup my Vnet in Azure, my Vnet gateway (P2S VPN) and shared file storage account.
The usual way to mount the drive is to use the NET USE commnand such as :
net use [drive letter] \\xxx.file.core.windows.net\fileshare /u:user [Password key]
If I run the NET USE command on a VM it mounts the drive instantly without a problem.
However, running the command from the on-premises Windows 10 pro machine I get the System error 53 has occurred error message.
I know that this error is often due to the fact that the ISP blocks port 445. However, my understanding is that this should not be a problem if I setup and use the P2S VPN. Doesn't the VPN bypass the ISP restrictions ?
I have tested the VPN and connectivity is confirmed.
I've also turned off all firewalls (PC and router) while trying to do this.
When the VPN is connected I try to ping the public IP address of the Vnet but this times out. I have read that Azure does block these ICMP pings.
I have also tried a tracert to my xxx.file.core.windows.net and it does timeout after 5 hops.
Am I trying to do something that cannot be done ?
In Azure, we can't use P2S VPN mount file share to your local PC. Because file share service work on the Internet, and we can't force the file share network traffic through P2S/S2S vpn.
As a workaround, we can deploy a RRAS VPN on Azure VM, and use local PC to connect the RRAS server, after connected, the local PC will get an IP from Azure datacenter, so we can mount file share on you local PC.
Here a blog about how to deploy RRAS on azure VM, please refer to it.
I have Oracle APEX 5.X installed over Oracle Express DB on windows 10 on a virtual machine.
I turned off all firewalls on the guest windows 10 VM and added all outbound and inbound rules to allow connecting to Oracle APEX port 8008.
I ran execute dbms_xdb.setListenerLocalAccess(l_access => FALSE); to allow accessing the APEX server over network instead of just localhost.
Now, What I'm able to do:
I can ping the guest machine IP address (192.168.100.2) from other
PCs on the network
I can open Oracle APEX inside the guest machine
192.168.100.2:8080/apex
What I can't do:
I can't open 192.168.100.2:8080/apex from any other PC in the same
network. I get an error: This site can’t be reached
192.168.100.2 refused to connect.
I searched for 5 hours now without any help.
Issue solved after connecting the laptop with the VM to a wired LAN connection instead of wireless.
I am running as my Host OS - Win 7 x64 and running an instance of Virtual PC XP. I am running the Cisco ISPec VPN Client on the Guest XP VPC OS and can successfully connect to my company's corporate network.
I cannot run the Cisco IPSec client sw on the Host, because it is 64-bit, Cisco doesn't support 64-bit on its IPSec client products and I don't have alot of choices at the moment in terms of moving to Cisco's SSL VPN client (AnyConnect).
The XP VPC Guest OS is not using the NAT network adapter, but the physical adapter of the machine.
I can ping the Host from the Guest OS and vice versa when Cisco Client is not running on the XP VPC guest OS.
Couple of problems:
When the Cisco client is running and connected the guest OS cannot see the Host any longer.
I would like to be able to access the VPN from the Host when the XP VPC guest is connected to VPN.
For #2, I have tried at least one technique, described: xenomorph.net/use-cisco-vpn-under-vista-x64/
This technique turns on ICS on the Cisco pseudo network adapter.
I could not get this to work. I may have followed the instructions incorrectly, however.
I have also looked at: http://www.pringle.net.nz/blog/PermaLink,guid,12ee0de7-f998-4084-8b06-537b3dbd5d9a.aspx
... which involves using a Loopback adapter and bridging between the host and guest OS. I have not followed this because the instructions are not completely clear.
Lastly, I have seen references on the net regarding a x64 build of OpenVPN, but I am hesitant to go in that direction.
Can anyone steer me in the correct direction regarding what to do?
actually cisco has cisco vpn client for windows 7 64 bit ,you can find it on 4shared.com ,but still cisco does not have client for windows 8