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

Had a website that had been copied from one Plesk server to another but no one knew the usernames and passwords for the protected directories. Plesk with it's passwords in plain text in the database to the rescue! SELECT domains.name , protected_dirs.path, pd_users.login, accounts.password FROM domains RIGHT JOIN protected_dirs ON domains.id = protected_dirs.dom_id LEFT JOIN pd_users ON protected_dirs.id = pd_users.pd_id LEFT JOIN accounts ON pd_users.account_id = accounts.id ;

This should work on any linux distribution using the net-snmp packages. Install net-snmp and the net-snmp-utils packages. Edit "/etc/snmp/snmpd.conf" and find the following lines: # First, map the community name "public" into a "security name" # sec.name source community and add a line for each host you will be polling from. i.e. com2sec notConfigUser 127.0.0.1 <a really, really secure community> com2sec notConfigUser <some other host> <a really, really secure community> If you only changed the "source" and "community" columns the following lines should not need to be modified. # Second, map the security name into a group name: # groupName securityModel securityName group notConfigGroup v1 notConfigUser group notConfigGroup v2c notConfigUser Add a view named "all" in the following section. #### # Third, create a view for us to

Did my first Ubuntu installation today. I wasn't really paying attention and skipped through the installation (it's very debianesque and I've done that a million times). I tried to get smart and skip creating a normal user account only to finish the installation process and realise it doesn't ask you for a root account password. Doh! Turns out that it's a "security" feature to encourage you to use sudo.