Tag Info

Hot answers tagged

19

The first thing I do when RDP is not talking is this in Powershell: PS> $service = get-service -computername MyServer -displayname "Remote Desktop Services" PS> $service.stop PS> $service.start The majority of the time this revives RDP and I can get back in. If this doesn't do the trick then I have to rely on iLO or one of the other console ...


10

See this question here for your command line options. Basically, you've got WinRS/WinRM, PowerShell Remoting and PSexec and the other SysInternals Suite utilities. You can also install SSH, or even telnet on a Windows server, and connect to that, once it's installed. Additionally, your tools in the Administrative Tools folder will let you connect to ...


7

It doesn't require reinstallation, it requires the installation of a the remote desktop services role and the purchase of licenses to enable additional RDP connections. Why do you need so many RDP connections, is this just to manage Microsoft services on the server? Management tools can be installed on client computers to manage many of Microsoft's products ...


6

I'm assuming that you want to RDP to it so that you can change it's ip address? If yes, then you can try this: Temporarily assign your workstation an ip address in the same 172.18.2.x range, then RDP to the machine, then change the ip address to match your new ip address range, then change your workstation ip address back to what it was.


5

The RDP client is interpreting the ".\" locally and filling-in the name of the local computer rather than passing the ".\" literally to the remote computer. (I believe this changed around the time that the RDP security layer was abandoned in favor of SSL, but I can't give you a specific RDP client version number...)


5

The RDP GDI Acceleration Extensions document is the closest thing I can find to an official reference, and it makes references to 16-bit RGB values being sent across the wire for things like GDI brushes as being 5/6/5 format (5 bits of red, 6 bits of green, 5 bits of blue). 5/6/5 has always been how Windows has handled 16-bit video modes (at least, in my ...


5

Remote Desktop Gateway would probably do what you're looking for. RD Gateway encapsulates the RDP protocol in HTTP or HTTPS. RD Gateway decapsulates the RDP protocol from the HTTP(S) and makes an RDP connection on behalf of the remote client to the appropriate RDP server. This allows a number of RDP servers to be present with the RD Gateway brokering ...


5

VNC on Windows acts like you are physically tapping into the keyboard, video, and mouse of the remote computer. So what you do through VNC basically has the same effect as if you were physically present at the console. Remote Desktop was originally a terminal server protocol. To permit lots of computer to run applications remotely on a server. These days ...


4

You don't just jump in to VDI as your first virtualization product. VDI typically builds on many complementary technologies, such as the hypervisor, the management suite for that hypervisor, VM images and templates, linked-clones, IP pools, etc. If you're completely new to virtualization, I'd recommend installing Hyper-V or VMware ESXi in a test lab, and ...


4

Were you qualifying the username you entered with the local machine name? If not, it's likely Windows was assuming you were attempting to login as the administrator account for the domain instead of the local system. In order to explicitly tell Windows that you want to login with the local administrator account you either need to qualify the username using ...


4

Essentially my question boils down to: does a computer joined to the domain automatically trust certificates issued by a CA on the same domain, or would they still need to be manually installed on each client device? Typically, the root certificate for your internal PKI is distributed via GPO to all clients. This makes it "automatic"


4

I am assuming you need to install the x64 bit driver. On your print server, go to Printer Properties, then click the Sharing tab. Click Additional Drivers.... When you download the x64 bit driver from the manufacturer's web site, you'll want to make sure the driver name matches exactly the same as the x86 driver and you should be good to go from there. ...


4

PowerShell is what you're looking for. TechNet PowerShell Remoting


4

One method would be to use a Remote Desktop Gateway. The Gateway can be fitted with multiple Connection Authorization Policies and Resource Authorization Policies (CAPs and RAPs) to define exactly who is allowed to connect to what. You could, for instance, create an Active Directory security group named "Internal Network Access" and assign that security ...


4

I have had a similar issue a while back. Ended up being that, although I was only putting in login in CoRD's dialog, it was actually sending the down-level login name (domain\login) to the server. Once I added domain\ prefix to login on RDP, it all worked. Hope this helps.


4

To allow more remote users on your MS Windows server you need to install the terminal services role. Microsoft calls those Remote Desktop Services since MS Windows Server 2008. This does not require reinstallation but probably one or more restarts. You need client access licenses and a license manager to use this feature. The following links will give you ...


4

With a Cisco AnyConnect VPN there is an option on the client side to allow this IF the VPN admin is allowing split-tunneling. You can see the option here: As far as on the firewall itself, if you are the VPN/firewall admin (I'm guessing you aren't) then the setting is similar to this here:


3

Your problem is that the templates don't allow for enough customization of the Subject Alternative Name (SAN) when using auto-enrollment. In this case, you need another check box for NetBIOS Name (or DNS Short Name). You basically have two choices. Keep using auto enrollment and deal with having to type the FQDN (which is good practice anyway). Or you ...


3

To answer just your question...sadly no. While you can upgrade a TS client's RDP version, the server version is dependent on the underlying OS installed and isn't upgradeable outside of upgrading the OS itself. Meaning while the RDC (remote desktop client)version's can be upgraded on a machine...the RDS (remote desktop services) is dependent on the OS ...


3

'.\' would not work as that is 'your' computername. But you can use 'localhost' localhost\localadminusername


3

It's not a timezone problem - the system clock is skewed too far. Timezones... don't really affect the computer in this fashion - they use epoch time anyway. (Yes, even Windows uses a system based on epoch time.) Try using the /console switch (call mstsc.exe from a command line) and a local account - otherwise, you'll have to connect physically to the ...


3

Since it hasn't been mentioned: There's always "smart hands". Never underestimate the simplicity of calling someone and saying "can you walk over to the server and tell me what you see? ...OK...do this for me." Unless the server is orbiting the earth, that is likely an option.


3

The licensing and broker roles generally are installed to a server that is not one of the servers providing the Remote Desktop sessions to users. I have often seen these two roles put together on a single box. In a small 3 server farm the broker/license box will probably be idle most of the time. These roles seem to work perfectly fine in a VM, so also ...


3

While you're remoted into another computer, minimize your current RDP session, then right click on the Remote Desktop icon on the taskbar and select Remote Desktop Connection. See my screenshot (it's Server 2012, but it's the same concept exactly). Alternatively you can: Minimize your current RD session and hit Start+R on your keyboard which brings up ...


3

This seems to be what you are looking for: http://support.microsoft.com/kb/2258492 To deny a user or a group logon via RDP, explicitly set the "Deny logon through Remote Desktop Services" privilege. To do this access a group policy editor (either local to the server or from a OU) and set this privilege: Start | Run | Gpedit.msc if editing ...


3

net localgroup "Remote Desktop Users" Ryan /add The above command will add the user account named "Ryan" to the "Remote Desktop Users" group on the local computer.


3

I suspect your corporate laptop VPN has been set up and configured a mode to tunnel ALL traffic down it and not just corporate traffic. In order for you to remote desktop, you will need to have it set up in a split mode. I am unfamiliar with the Cisco VPN but, for example on Sonicwall SRA devices the option is "Tunnel all mode". Many sysadmins setup their ...


2

Did you got that solved? If not try the following: run the IIS Crypto from Nartac on the affected server (or do all the stuff the tool made by hand, thats also possible e.g. via regestry) leave TLS 1.0 enabled change the cipher in the list and disable all CBC cipher (the ones with CBC in it) restart the server. That should do the trick, as currently only ...


2

Remote Desktop Services actually have a pretty rich WMI object library you can take advantage of to query and manipulate the configuration. As of Vista/2008, it's located in the root\cimv2\TerminalServices namespace. Here's a good place to start on browsing what's available: Remote Desktop Services Configuration classes In regards to your specific ...


2

Windows Firewall doesn't necessarily "block" your machine from brute force attacks on TCP port 3389. It just filters via an access control list for those you are permitting to use that port /service. There are many ways the RDP service can be attacked even with a Windows firewall. If your not already using SSL, I recommend you do so as detailed in this howto ...



Only top voted, non community-wiki answers of a minimum length are eligible