Figjam's Travails

CTRL+ALT+END : Open the Microsoft Windows Security dialog box (CTRL+ALT+DEL) ALT+PAGE UP : Switch between programs from left to right (CTRL+PAGE UP) ALT+PAGE DOWN : Switch between programs from right to left (CTRL+PAGE DOWN) ALT+INSERT : Cycle through the programs in most recently used order (ALT+TAB) ALT+HOME : Display the Start menu (CTRL+ESC) CTRL+ALT+BREAK : Switch the client computer between a window and a full screen ALT+DELETE : Display the Windows menu CTRL+ALT+Minus sign : Place a snapshot of the entire client window area on the Terminal server clipboard and provide the same functionality as pressing ALT+PRINT SCREEN on a local computer (ALT+PRT SC) CTRL+ALT+Plus sign : Place a snapshot of the active window in the client on the Terminal server clipboard and provide the same functionality as pressing PRINT SCREEN on a local computer (PRT SC)

Say you want to add 192.168.1.2 through to 192.168.1.14 with a /28 netmask (255.255.255.240). for /L %a in (2,1,14) do netsh in ip add address "Local Area Connection" 192.168.1.%a 255.255.255.240 Which is: for /L (tell for that it's a range of numbers) %a in (placeholder variable) (start, step, end) (self explanatory) do (command goes here) This page FOR /L has more detail and is part of this very useful site ss64.com

To cut a long story short, the first thing to do is try and create an RDP connection locally, to rule out external firewalling and routing. The problem was that even though "Terminal Services" was up and running, "Don't allow connections to this computer" was selected under "System Properties" -> "Remote". Selecting "Allow connections from computers running any version of Remote Desktop (less secure)" resolved the problem. Not exactly intuitive...