Tag Info

Hot answers tagged


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


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


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.


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


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


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.


Uh, well, the default time zone on a Windows OS is Redmond, Washington time. :P But that's irrelevant, since as HopelessN00b points out, timezone differences don't equal clock skew. But I'm going to bet time differences aren't your problem anyway. The error message mentions that the server gave you an invalid certificate. In order for that to happen, that ...


LoM is a commonly used technique to access nodes which is unaccesible in logical terms. The name of the techniqu differs from manufacters, dell call their version 'iDRAC'. HP call theirs 'iLo' In the earlier days there was specific PCI cards for this, called MEGARAC. There is also KVM over IP to help. Best of luck!


Like said above iDRAC, iLO are best way to access remote systems if RDP fails to start. If the system is a virtual machine you could use virtual infrastructure to remotely manage and in most case view the console. I'd invest in something such as a LANTRONIX 'Spider" also which could be hooked up to the VGA and USB ports of the remote system to allow for our ...


Yes, you can set up a second server in an SBS 2008 domain and run terminal services on that. This is the preferred solution. In fact, SBS 2008 Premium comes with the second server's license already (you might want to check and see if they already have that second license).


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

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