Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 10 months ago.
Improve this question
I have spun up a Windows Server Datacenter 2019 image on Azure. When I go to the Activation screen in Settings, it shows that Windows is not activated. How do I activate Windows? Do I need to buy a server license?
I just created a new VM. I log into the server using RDP, and check if the machine is activated. It isn't. The error is:
We can't activate Windows on this device as we can't connect to your
organization's activation server. Make sure you're connected to your
organization's network and try again. If you continue having problems
with activation, contact your organization's support person. Error
code: 0xC004F074. Then I try to hit the Troubleshooting box:
Troubleshooting has completed: We can't activate Windows. Make sure
you're connected to the Internet.
The server doesn't seems to be able to connect to Microsoft's KMS servers. To verify if that is the case run the following from Powershell:
Invoke-Expression "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /skms kms.core.windows.net:1688"
Test-NetConnection kms.core.windows.net -Port 1688
TcpTestSucceeded must be True , if false then your VM can't reach the KMS and therefore not activate it. So test and see if your VM can reach kms.core.windows.net on port 1688.
There is another known issue where setting the Azure hosted VM to any time zone other then UTC +00 will cause the Settings app to show the VM as not being activated, but if you run the activation command via sconfig the VM is activated fine, the GUI will persist that the VM is not activated however.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
The Linux virtual machine on Azure, the problem encountered, can not connect through rdp (Microsoft Remote Desktop). Throws a connection error, respectively. I use MacOs (I tried it with Windows, the same problem).
The question is what could be the problem?
There is no Microsoft RDP for Linux. You have to connect via SSH on 22.
If you have diagnostics enabled on the Linux VM, you can use the serial console. Just click on the VM in the Azure Portal -> Serial Console.
If you really want to connect via RDP, then you can try installing xrdp on your VM, but it really depends what flavor of Linux you have deployed.
sudo apt-get install xrdp
sudo service xrdp start
Don't forget you need access to TCP port 3389.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
My company is integrating with this company to enable us both consume services built on each other's platform to provide joint services extended to external users.
They recently sent me a file containing their VPN configuration with spaces provided to enter ours as well. Now I am not so savvy about VPNs plus our server is hosted in an Azure VM (windows server 2012 R2). I don't know if our hosting arrangement is VPN-ready by default. How am I supposed to go about this?
Any helpful articles or guidance is a welcome boon at this time.
PS.
My knowledge on networking is next to nothing. Just know the basest of things there.
there are two options to create the VPN to your cloud infrastructure:
1) By external services like OpenVPN - in that case, your involvement into what should be done will be to open some endpoints. Tutorials are available.
2) By internal service called Virtual Network. In that case, you should first place your VM to the Virtual Network, and then use tutorial. As the networking is a big topic, i would propose you to read the official tutorial instead of putting that information here.
So, basically, to get your VM ready for the VPN, you should:
1) Create Virtual Network
2) Place the VM into that VN
3) Configure both cloud and local gateways
4) Install the VPN client.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have an Azure VM created using MSDN account.
But cannot remote-desktop into it using mstsc.
- Tried 443 port adding on VM
- Choose mstsc > options > settings > RD Gateway server > (entered VM name)
Any hints on how to remote to it?
I generally download the RDP file from the portal. This has worked pretty reliably for me.
Find the RDP endpoint port (public port) in VM settings, and RDP into that. You won't use the gateway address in the RDP client in a normal scenario, that setting is only used if you have an RD gateway server (which I'm willing to bet you don't have). So all you need is the address (cloud service URL) + port.
Or just download the RDP file, which is way easier.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
As I read, each azure cloud service has a VM behind it (right?). I know, for a VM, I can click 'Connect' button to get the rdp file to remote login. However, for my cloud service (which is running), the 'Connect' button (in Instance panel) is always disabled. How do I turn it on? How do I remote login to this cloud service?
At first you need to enable remote desktop for your cloud service.
This can be done at least in two ways:
During deployment from Visual Studio.
Directly at the portal.
I think good way for you know is a second variant.
Go to your cloud service.
Enter Configure tab and press 'Remote' button at the bottom.
Set all the needed settings there (role, user name, password, certificate, expiration etc.).
After Azure finishes setup - go to 'Instances' tab. Click on the needed and 'Connect' button will be available.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm a programmer dammit, I should be allowed to ask these kinds of IT questions! :)
Anyway the problem is as follows. I'm writing an automatic build script to deploy code to a live windows 2003 server. To get access to the server I enabled the VPN role, and I can connect to it remotely from my dev machine using a username and password I set up on the server from the network connections screen.
I set up a share on that machine and gave full share+security permissions to the account I am using to connect. Once connected, I would have thought I would be able to see the share. In fact I can't even see the computer even though the VPN is connected (if i type '\IPADDRESS\' into the run box nothing comes up).
Am I missing an essential step here?
So you can use Remote Desktop Connection to connect to the server, but CIFS/SMB (shares) is not working?
Is there a Windows firewall setting that needs to be changed (... I don't even know if there was a 2003 update that included Windows firewall)?
Pinging the IP address results in which error message (or, hopefully none if you can RDC)?
Is the remote server and your local dev box on the same IP subnet? If its not routed properly you may be trying to hit a local address.
It looks to me like you can't connect to a network share from inside the same session that you esatblished the VPN connection in. I now manually open the VPN connection, then kick off the build scripts