I just launched a new windows server 2016 virtual machine from EC2 Management Console.
I tried to connect RDP from my desktop (MAC OS) it is not connecting, and even the machine is not pingable from public IP and public domain name.
please the machine is up and running and the from the security group i enable the inbound rules for port 3389
You would need the Microsoft Remote Desktop, the default RDP app will not work and for the ping, you need to enable ICMP protocol in the Security group and then open the windows firewall. Here is a detailed answer
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 want to have a SSH connection from my local windows machine or VM on my computer to Azure windows server VM. I tried Cygwin and Putty but both of them gave timeout connection. I used public ip address and opened port 22 on Azure VM.
I will appreciate if some one can give me any hints or links.
There are multiple firewalls that can be the reason here. Fist you must have a rule on the server to allow incoming SSH requests (port 22). Then you need to configure the NSG(Network security group) to allow incoming on port 22. If it still doesn't work, you need to verify that you are allowed to do an outgoing SSH request from your computer.
Thanks for suggestions, I found the problem which was the host machine IP address(ipconfig) (where is a local VM inside domain) was different from the IP address that communicate outside the domain to internet. I was set in NSG of Azure VM to only accept this IP and because of that it gave time-out error. After changing the IP it works.
My local machine is using MacOSX/linux and am able to connect to a Windows Remote Desktop machine (using Windows Remote Desktop/Remote Desktop Connection).
The Windows Remote Desktop machine is able to connect to certain servers that I cannot connect to locally on my MAC. For example, connection to database servers, specific web servers, etc.
How can I setup some kind of tunnel so that I can access the servers locally on my mac?
You can configure port forwarding on the Windows machine
netsh interface portproxy add v4tov4 listenport=3390 listenaddress=192.168.1.111 connectport=3389 connectaddress=192.168.0.33
where 192.168.1.111 is IP of your Windows machine and 192.168.0.33 is destination server. From your Mac you will connect to Windows machine specifying port in RDP connection 192.168.1.111:3390 and you will be connected to the remote server. You have to provide credentials from the server, not your local Win machine. This configuration survive restarting Windows machine.
Just install Igiko on your windows machine and then open it in web browser on your MacOSX. Igiko is acting like web-based RDP gateway, using it you will be able to open RDP console to any Windows machine in your network.
While configuring one of the subnet IP address (for virtual machine in windows azure), deleted Microsoft Virtual Machine Network Bus adapter and now cannot access the Virtual machine via RDP. Before this I was able to RDP into the virtual machine.
Is there an alternate access to the virtual machine?
Yes you can always try to use your public IP Adresses of your VM and you can establish a SSH connection with command line. In order to connect in SSH you should take these steps on below.
Open your terminal
type: ssh yourusername#youripadress ex: ssh john#192.168.2.3
You will be asked for your password
After this you will be able to connect. If not you should authorize the port 22 SSH in your vm machine configuration.
Second solutions:
-Is to use an Azure Bastion.