Tag Info

New answers tagged

0

What state is the machine currently at physically? Can you view the display? If it has already stopped the user profile service and logged the account off you either need to wait or force the machine to power off. If it has not you can issue a shutdown -a this will abort the shutdown and you can try again, before doing this check the eventlogs for any ...


-1

Ah, same thing here. I solved by disabling public access to RDP, allowing only private network connections to the server. Which is, by the way, recommended as soon as you get access to your brand new server.


2

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 ...


4

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 ...


0

Try an IP scanner utility like Angry IP Scanner and see if it can interrogate the server for its host name. I know in Angry there is a column for host name and I often (but not always) see it populate.


4

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


2

You had to use/configure Windows Firewall, here. Simply modify the incoming RDP rules to allow connection only from the desired interface.


1

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 ...


0

In addition to SNAT, a MASQUERADE should also do and will make it a little easier. MASQUERADE is SNAT except instead of specifying an IP address you are specifying an interface; this means that you won't need to add POSTROUTING rules if for example you add more port forwards. iptables -t nat -A POSTROUTING -o $out_interface -j MASQUERADE In theory there ...


2

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


1

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.


5

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 ...


0

I have the same, the Terminal Server 90 days Evaluations License was expired, you need to purchase proper TS CALs License


0

Often Im seeing below message, while trying to login to server 2003 .. Then as its already suggested, by roaima , What i do is to use "Attach to console" in the Advanced tab Above option should be equal to below windows command mstsc -v:servername /F -console Attach to console" in the Advanced tab achieves much more similar to this switch /admin ...


0

Based on the above answers, you can create a shortcut to the following location (right click on Desktop>New>Shortcut) explorer shell:::{2559a1f2-21d7-11d4-bdaf-00c04f60b9f0} It should also work if launched from command line (if you want to script it). Add a nice icon from %SYSTEMROOT%\System32\imageres.dll, and you're good to go. Thanks guys!



Top 50 recent answers are included