Monday, November 30, 2009

Video setting up Openfiler to be a iSCSI SAN

My first attempt at posting to YouTube. I created a video showing all the steps in setting up OpenFiler as iSCSI SAN. No audio, just a run through of how it is done. It looks better if you watch it in a separate screen so the detail comes in better.

Just go to this link.


Thursday, November 12, 2009

Combofix and the Recovery Console

I have used and read about the Combofix utility and the Microsoft Recovery console. If you use Combofix, it will install the Microsoft Recovery Console. But after that some are having problems removing the recovery console. I usually leave it installed, but certainly it is best to be able to put a machine back in the same state it was in especially if you are working on it for someone else. So I decided to see how I could use Combofix and get rid of the recovery console.

The first test was actually to install the console myself before running Combofix. You do this from the CD that has your installation files for Windows XP. One note here is that you need the right version for the one installed. That is, if you have Windows XP with SP3 installed, you are better doing it with a Slipstreamed XP CD (To slipstream, you can also look at downloading Nlite which makes the job a lot easier). The command to do this is: driveletter_of_CD:\i386\winnt32.exe /cmdcons.

Once you have done this, then you can install Combofix and run it. It will not install the Recovery Console because it is already there.

Once you are done, you can follow Microsoft's instructions for removing the recovery console. It will work just fine.

Now if you have the console because it was installed by Combofix, then this is where some have encountered the problem. I have read numerous post about this. If I have the chance (this will be my second test), I will try to remove the console after installing it with Combofix. If you can install the console yourself before using Combofix, then I suggest you do it that way. Of course you are running Combofix because you have a virus, so that might not be possible then. Since the times I have had to use it was in such a case, I just let Combofix install the recovery console because the computer already was in such a sad state.


Enabling SSH on Ubuntu

Ok, not sure why I want to blog this, but guess I ran into it today trying to P2V a Linux machine running Ubuntu. You need ssh enabled for Linux - since I normally do Windows, I had to quickly figure it out -- Here is basically my Terminal session and testing to see if worked:

1. First get the openssh-server software:

machine_name@ubuntu:~$ sudo apt-get install openssh-server
[sudo] password for machine-name:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
rssh molly-guard openssh-blacklist openssh-blacklist-extra
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 286kB of archives.
After this operation, 766kB of additional disk space will be used.
Get:1 karmic/main openssh-server 1:5.1p1-6ubuntu2 [286kB]
Fetched 286kB in 2s (104kB/s)
Preconfiguring packages ...
Selecting previously deselected package openssh-server.
(Reading database ... 132547 files and directories currently installed.)
Unpacking openssh-server (from .../openssh-server_1%3a5.1p1-6ubuntu2_i386.deb) ...
Processing triggers for sreadahead ...
sreadahead will be reprofiled on next reboot
Processing triggers for ufw ...
Processing triggers for man-db ...
Setting up openssh-server (1:5.1p1-6ubuntu2) ...
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
* Restarting OpenBSD Secure Shell server sshd [ OK ]

2. Next Test to see if it is running:

machine_name@ubuntu:~$ ps -aef | grep sshd

root 3663 1 0 15:38 ? 00:00:00 /usr/sbin/sshd
user_me 3679 3488 0 15:39 pts/0 00:00:00 grep sshd

3. Next ssh to it right there from your own machine:

machine_name@ubuntu:~$ ssh localhost
The authenticity of host 'localhost (' can't be established.
RSA key fingerprint is f0:7f:e7:82:6c:61:d0:61:85:66:31:10:1f:72:b1:7e.

4. Type yes
Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
machine_name@localhost's password:
Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686

To access official Ubuntu documentation, please visit:

0 packages can be updated.
0 updates are security updates.

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

5. At this time your on and working, typing exit, brings you back to the terminal. You can test remotely with putty.


Wednesday, November 11, 2009

Why does Microsoft name their OS so lame?

MAC has Snow Leopard, Ubuntu Karmic Koala, but Microsoft, Windows 7!!! Before that Vista, before that Windows XP, before that 2000, NT, 98, 95, Win3.1 ... no pattern, but inconsistent boring names. They should at least be named after planets, or better yet solar systems. If not, then I would like to name them after fish. How about "Barracuda", or "Hammer Head"?

Just a thought, What do you thing would be good names for Windows OS(s)?


Sunday, November 8, 2009

Could not delete or Edit Host file because of Virus

Recently, and yes this is definitely when Tech Bytes, I was cleaning a computer that was riddled with viruses. Ran all the tools - Conficker, Malwarebytes, Adware, Hijack This, etc., and removed pretty much over 244 infections of one type or another. One virus, and I have seen this before, decided to hi-jack the browser, and the host file. The hosts file was full of entries redirecting the browser to all sorts of crazy sites, of which then would continue to infect the machine. Booting to Safe Mode did not help. Still could not delete the hosts files. You could not change the attribute which was set to "read only", and it had also created a backup for itself in the hosts.sam, and a folder called !Killbox in the root with another host file in it.

What I did:

1. Took the drive out, and added it as a USB drive to my Windows 7 laptop.
2. Took Ownership of the file.
3. Removed the Authenticated Users from the rights of which they were set to read only.
4. Added everyone group and gave full rights.
5. Deleted hosts file, backup host file, and the folder !Killbox.
6. Ran Nod32 on it from my laptop.
7. Recreated the host file.
8. Put back into machine, booted, and rescanned again with Spybot, Malwarebytes, and installed Avast.
9. Ran Avast at boot scan after installing it. You have to reboot, then it scans before getting to Windows.


Tuesday, November 3, 2009

Windows 7 some problems noted

My experience with Window 7 so far has been over all positive, but this is not saying that I will not experience something drastic, and that others are not experiencing problems:

1. I have seen reports from friends saying that now that they have gone to Windows 7, Internet Explorer 8 is soooooo slow.
2. Printer driver issues still exist, and HP, on a particular model will not have new driver available until January!!!!
3. Endless reboots on upgrades.
4. Key problems.
5. Download problems.

Also saw this post: Windows 7 Problems Article in PC World