I am completely new to this challenge. The scenario is :
I have create two virtual machines on Microsoft Azure. First VM is Windows Server 2012 R2 and second VM is Windows 8.1
I have configured a domain controller on Windows Server. I want to connect to server from windows 8.1
I have attempted following:
In the browser of windows 8.1 - http://dc/connect
but it shows error as:
`This page can’t be displayed
•Make sure the web address http://dc is correct.
•Look for the page with your search engine.
•Refresh the page in a few minutes.`
Also I tried changing domain of windows 8.1 machine. but it is not allowing me
There's nothing preventing you from connecting to a Windows Server machine from Windows 8.1 in Azure. What probably you did wrong is the network configuration. Both VMs must be in the same virtual network. When you create a new VM, you have to choose "From Gallery" to be able to select the VNet you will deploy it to. Once both machines are in the same VNet you will be able to ping the private address, join domain, access network file shares, etc.
Deploy using "Quick Create" only if you want to quick test something solo. At this point, if you really didn't setup the network configuration properly you will have to redeploy. Just delete the Windows 8 VM (without deleting the VHD) and after a while the machine disk should appear on the vm creation wizard under "My disks". Just recreate the VM using the original settings and making sure the VNet for both VMs are the same.
Virtual Network Overview
https://msdn.microsoft.com/en-us/library/azure/jj156007.aspx
Do remote desktop connection ,in your search tab type remote desktop connection and set your domain and user name. than connect it.
Related
I have an App Service in my Azure resource group. My ASP NET application is hosted on the windows environment inside that app service. I am wondering if it is possible to connect to this desktop windows server using Remote Desktop or something like this. There is a KUDU feature on the Azure but the only one thing that I can do with this is to show server's CMD. That is not enough, because I need to access to the windows desktop GUI like on typical PC. Do you know any tool that would allow me to do this?
App Service runs your applications in a sandbox and it's simply not possible to remote desktop to the underlying VM. There's no Windows GUI that you can access.
The Virtual Machines service allow full control of the VM and you can access the Windows GUI using remote desktop.
I've got 2 machines:
A corporate desktop machine which is running Windows 7 SP1 which resides on the corporate domain and which I log into using a corporate domain account.
A personal laptop that I use when working from home via the Cisco VPN client but presently sits on my desk connected to the corporate WiFi (though I had it connected to the wire and on the same subnet as my desktop machine today also). This machine is not on the corporate domain; I log into this machine with a Microsoft Account.
I need to run Visual Studio 2013 Release Management Client from both machines. The machine on my desktop works fine when entering either the IP address or the URL into the Release Management Server URL entry field and everything hooks up and all is glorious.
On my Windows 10 laptop however, it's a different story. Every attempt to connect is met with the error:
The server specified could not be reached. Please ensure the
information that is entered is valid (please contact your Release
Management administrator for assistance). <-- I'm the admin
I can ping the machine both with IP address and with hostname, ruling out DNS issues. Both client machines are on the same subnet. Both machines are using the same outbound port.
Checking the event log I see a bunch of Message: The remote server returned an error: (401) Unauthorized.
Checking with Fiddler, on my desktop machine, I can walk through the handshake of each of the stages of startup and all is good. But in Fiddler on my laptop I see 3 401 Unauthorized errors before Release Management Client bombs and returns the rather uninformative message I posted above.
I've attempted to create a shadow account on my laptop and do the Shift-Right Click-Run As Different User dance, but I must be missing something because I can't get this to run.
I've talked to the network administrator who suggests that I should be able to access all of the same resources from both machines and that it must be a Release Management issue.
Is this an incompatibility between VS2013 Release Management & Windows 10 or something else? Has anyone else had this issue and overcome it? I have access to be able to administer the Release Management environment if there's changes that need to be made there and I'm a local administrator on both machines. I'm not however a domain administrator if changes need to be made there.
I would bet you simply have a security issue as the workstation is not domain-joined and the WPF client is using Integrated Authentication.
Often creating a local "shadow" user with same username and password, and running the client app under that account (run as) works.
Another option is to join the workstation to the domain or use a domain-joined VM.
After fully investigating the situation, it appears to have been a combination of factors. I am posting a response because this appears to be a relatively common problem:
The workstation was sending an unexpected credential to the server. To get around this, you have to configure the user account on the server without a domain in the username and create a shadow account on your local machine. When running the client application, you must either log into this shadow account on the local machine or you must SHIFT+RIGHT CLICK and choose "Run as" entering your local shadow credentials. This will then pass the shadow account to the server which will now authenticate without referencing the domain. OR
Create a user account on the server that matches the credentials on your local machine including MACHINENAME\LocalUsername
There appeared to be a network issue when attempting to connect to the Release Management Server from the non-domain machine when connected inside the network. When connecting via the VPN from home, this situation was resolved, but only after we'd ensured the account and local machine accounts were correctly configured. The domain connected machine always connected properly.
I'm pretty new to Hyper-V so go easy on me if this is an obvious question. I would like to access my host machine's IIS through a Hyper-V VM so that I can view webpages I'm creating in Visual Studio within my VM. I have enabled the network switch to share internet connection however I'm unsure as to how I can allow IIS through to my VM. Is this simply a firewall/port issue or is there a more advanced solution needed?
Since you already have a switch attached to the VM, I don't see anything that is required to be done on the VM, but I would ping the host from VM and make sure that works.
If you are running the website just out of Visual Studio, which would inturn be running IIS Express and not the IIS on the host, you should follow the instructions here to configure IIS express and host to accept requests from non local addresses: http://johan.driessen.se/posts/Accessing-an-IIS-Express-site-from-a-remote-computer.
I'm trying to setup Azure Connect so my worker role in the cloud can access my SQL Server database on my private premises.
I've followed the articles here, here and here, but they all seem outdated.
Furthermore, i'm using Visual Studio 2012, and there is no "Virtual Network" tab on the project properties, on anything related to "Azure Connect".
I'm assuming it's been rebranded as the "Virtual Network" tab in the management portal?
Can anyone help?
Azure Connect is getting retired on July 3, 2013. You should make the transition to Windows Azure Virtual Network before then.
You should now use the Point-to-Site VPN feature that was announced last week (April 26): https://azure.microsoft.com/documentation/articles/vpn-gateway-point-to-site-create/
With the Point-to-Site VPN feature of Virtual Network, you can easily set up secure VPN connections between individual computers running Windows and a virtual network in Windows Azure. The feature relies on the built-in VPN client functionality of the Windows operating system (supported versions are Windows 7, Windows 8, Windows Server 2008 R2, and Windows Server 2012), so there’s no need to install an agent software, as there was with Windows Azure Connect. Furthermore, with the Point-to-Site VPN feature, you get the full functionality of the Windows Azure Virtual Network service.
I published the cloud service from VS2010 with Remote Desktop enabled. I downloaded the remote desktop connection for that instance. I just logged in to cloud server using Remote Desktop. Now i published same application from another computer. When i want to connect Remote Desktop from new machine its unable to connect to server. Even i tried from previous machine i am getting the same thing.
Application has 1 role & 1 instance. help me with this thing.
You must allow the RDP while publishing it to the cloud...Check the publish settings once...