Hot answers tagged rdp
There are settings in the Server 2008/2012 policies that aren't accessible on your 2003 server I believe, such as "Do not connect to any Windows Update Internet locations" under the Computer settings you show above. I believe the settings you are looking for in a 2003 environment are: Disable access to Windows Update The correct policy for v6 ...
I would connect to the remote machine via wmi and use win32_computer system.name. EG (gwmi win32_computersystem -computer 192.168.1.1).name
If your client is Windows 7 or newer, you can get this info by WMI as JimB mentions with a one-liner Powershell: Get-WmiObject win32_computersystem -ComputerName 192.168.161.5 | Select-Object Name should work with clients that are Windows Server 2003 or newer. If you want it as a string instead of an object, Get-WmiObject win32_computersystem ...
If you prefer something more GUIsh, there's an excellent utility named NetScan (and, IMHO, with better features than other similar utilities). The great advantage of this utility is that it can add columns with WMI queries results. It comes with some pre-built WMI queries, but you can add as many as you like. The query you need is a simple one - SELECT ...
As it seems that all machines are on the same subnet, the Windows computer will try to answer directly to the client without passing through the NAT box (layer 2). You should SNAT reply packets also, adding : iptables -t nat -A POSTROUTING -s 10.10.10.7 -p tcp --sport 3389 -j SNAT --to 10.10.10.5
You had to use/configure Windows Firewall, here. Simply modify the incoming RDP rules to allow connection only from the desired interface.
Most likely you have some open file handles to the server in question, even if they aren't actually connected. The existing handles may have not had access (or are using invalid credentials) when they were set up. Rebooting the client PC is the ultimate solution to resolving the issue, however you could use tools like Process Monitor to search for open file ...
Go to Administrative Tools / Server Manager / Roles / Add Roles. Add the Remote Desktop Services role. In the Role Services submenu add Remote Desktop Session Host. In the Client Experience submenu select "Audio and video playback" and "Audio recording redirection". After installing this a Remote Audio device appears in the Recording tab.
You don't go into detail on how you're logging in but if you're copying, and pasting the password using the mouse login often fails. Your answer describes a work-around but there is a hot-fix available for Windows 7 here: https://support.microsoft.com/en-us/kb/2547752
Only top voted, non community-wiki answers of a minimum length are eligible