I have a VMSS which is not connected to a load balancer running windows 2016 server edition operating system. How can I RDP into this setup? Is port 3389 open by default?
If you use Azure image to create VMSS, you can create a windows VM work as a jumpbox in that same Vnet.
If you use image which upload from your local, please make sure you have enable RDP first, then you can use another VM to RDP it via internal IP address.
If you image does not enable RDP, please re-prepare your image and enable RDP, then upload to Azure to create a new VMSS.
Another way to do this is to go to your vnet, search for your vm scale set and you should be able to see the IP.
Related
Having created a Windows Azure VM and opened ports 3389 and 22 for inbound RDP and SSH connections, respectively.
I can successfully connect to the vm via RDP from a remote Windows PC.
Testing SSH connection in the Portal succeeds. However trying to connect from a remote Linux VM using SSH fails.
Given that SSH connection test within the portal succeeds, it suggests that (1) it is possible to SSH into a windows VM; and (2) there is no other config require on the server ie installing OpenSSH (or similar) / Copying over key file(s) to some location etc. However, the help steps in the Azure Portal for my Windows VM, for making remote SSH connections suggest that maybe a public key needs to exist on the server and that I need the private key on the LinuxVM I am trying to connect from.
Please could someone help me understand if ssh into windows Azure VM is possible and if so, the requirements / minimum set of steps (on the target Windows VM and the source Linux VM) I need to get to a state that I can successfully SSH.
Other posts re similar question posted have not helped me connect via ssh. I have not found a 'golden source of truth' on Microsoft docs. Maybe I missed it.
Thank you.
A Windows Server doesn’t typically come pre-built and ready to go with SSH access and it requires some setup. You can follow this to set up your Azure VM for SSH access. You can configure SSH on a Windows Azure VM for access, check out How to Set Up OpenSSH on a Windows Server. After deploying the OpenSSH, you can follow the steps about connect via SSH with client in the Azure portal on your Linux client to access that Windows VM via SSH.
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 create a win2012r2 datacenter vm on azure. i'm trying to connect via RDC but rdc cannot connect. i use the rdp file that azure provide, and also tryied to do it by myself manually in rdc (dns:port and also ip:port) but still i can't connect. how to check where the problem is?
Thanks
Are you in a Crop. network? I means did you check the firewall settings on your side? And kindly reminder, the default RDC port is NOT 3389.
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.