Remote Desktop can’t find the Computer through RDWeb and Gateway


Have you tried to use the “Connect to a remote PC” page of RDWeb and end up getting an error that “Remote Desktop can’t find the computer” ?


Chances are you are able to use the RemoteApp and Desktops tab just fine, but for some reason you cannot connect to any computer you type into that blasted “Connect to” field!

Just a guess here, but I would assume you have a Remote Desktop Gateway deployed and you are accessing RDWeb from outside the corporate network.  Am I right?  OK, one more guess, if you manually configure the gateway on the Remote Desktop Client (mstsc.exe) you are able to connect just fine…right?


So what’s going on here?  The gateway service is obviously working, which means there is probably something wrong with the RDWeb page.  To fix it, you need to open up the IIS console from your RD Web Access server.


Then navigate your way to Sites Default Web Site RDWeb Pages and double click the Application Settings icon.


Here you will see an empty Value for DefaultTSGateway.  Just double click that and enter in the external DNS name of your RD Gateway address.


Now you need only to refresh the RDWeb page and try connecting again, but this time it should work.

Remotely enable remote desktop

If for any reason you neglected to perform this procedure prior to shipping the server, you can enable Remote Desktop remotely by using the registry.

Administrative credentials

To complete this procedure, you must be a member of the local Administrators group.

To enable Remote Desktop remotely by using the registry

  1. On any computer that is running a version of Windows Server 2003 or Windows XP Professional, click Start, click Run, type regedit, and then click OK.
  2. On the File menu, click Connect Network Registry.
  3. In the Select Computer dialog box, type the computer name and then click Check Names.
  4. In the Enter Network Password dialog box, provide Domain Admins credentials for the domain of the server, and then click OK.
  5. After the computer name resolves, click OK.
  6. In the computer node that appears in the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
  7. In the console tree, click Terminal Server and then, in the details pane, double-click fDenyTSConnections.
  8. In the Edit DWORD Value box, in Value data, type 0, and then click OK.
  9. To implement the change, reboot the server remotely, as follows:

    Open a command prompt, type the following, and then press Enter:

    shutdown -m \\DomainControllerName -r

Taken from Microsoft TechNet

RDP/Terminal Services Printer Driver Mapping

Client’s who RDP’ing in to their desktop unable to print to their local printer?  Have you got “TerminalServ” errors in the “Event Log” relating to missing drivers?

This is cause by the names of the drivers not matching up, i.e. on the click you have a driver for “Samsung ML-2250 Series” whereas the server has the driver for a “Samsung ML-2250 Series PCL 6”.  Only a slight difference but this causes them not to match up and as a consequence stops printing over the RDP session.

You’ll need to edit the registry and create two new values and create a ‘mapping’ file:

Key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd

Value: “PrinterMappingINFName”

Type: REG_SZ

Data: Name and path to mapping file, e.g. “c:\windows\system32\TSprinters.inf”

Key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd

Type: REG_SZ

Value: PrinterMappingINFSection

Data: Name of the section in the .INF file that contains the actual mappings, e.g. for example “Printers”

Create a file in “c:\windows\system32\” called “TSprinters.inf”, basically it must match your newley created registry key.  The content should start like so:


;This file contains Mappings for Client driver to Server driver printer connections


;”Client Printer Driver Name” = ” Server Printer Drive Name”

“Hewlett Packard LaserJet 5P” = “HP LaserJet 5P”

Now restart the “Print Spooler” on the RDP/Terminal Services Server, log off and back on and print!

Thank to Brian Madden for this extract from “The Ulimate Guide to Terminal Server Printing, Design and Configuration.”

“Terminal Services temporary client license will expire in…”

Having used the different versions of Windows Server 2003 for a long time I tend to use Standard Edition to utilise Terminal Services for remote workers.

In some instances before the implementation is full complete and the required TS CALS purchased a user will be required to log in after the 120 days temporary license has expired.  A temporary work around to resolve this remotely is as follows:

  1. Login remotely via VPN.
  2. Using “Computer Management” click “Action” > “Connect to another computer…” and type in the IP address of the server and click OK.
  3. Expand “Services and Applications” and then click “Services”.
  4. Scroll down to “Terminal Server Licensing”, right click and “Stop”.
  5. Using Explorer browse to “\\<ip address>\c$\WINDOWS\system32\LServer” delete all the files ending “.edb”
  6. Go back to “Computer Management” and “Start” the “Terminal Server Licensing” service.

The client can now logon with out the expiry message.

Please note: To carry out the steps above you are required to have administrator access rights to the server.