Thursday, February 23, 2017

hp laserjet and Initializing...

The only thing that really works is this solution:

1. Turn off the fax/printer and turn it on again.
2. Wait till the screen shows the Ready display.
3. Press the Menu (wrench icon) button.
4. Press the Left (Left arrow) button and the OK button simultaneously
5. You should see the 2ndary Service. Press OK to select.
6. Press right arrow until you find File Sys Format. Select that.
7. Wait until the system finishes the formatting. After that, the fax/printer should be fine and ready to receive new faxes again.

How To Factory Reset HP Laserjet M1212nf MFP
Problem: Unable to install HP Laserjet M1212nf MFP because the IP address on the printer was not in the same subnet as the devices within the network.

As a result it was not possible to access the printer using the web interface and ping requests also failed.

Solution: To make the printer detect an IP address within the network I had to reset the printer. It is a simple process:

1. Turn off the printer and disconnect the ethernet/network cable that connects the printer to your network device (router).
2. Locate the red X button and the right arrow button on the printer's control panel.
3. Turn on the printer and at the same simultaneously hold down on the red X button and the right arrow button.
4. In a moment you should see a 'Permanent Storage Init' message on the printer's display screen.
5. Answer the prompts for 'language preference', 'location', etc.
6. After that you see 'Initializing...' message then 'Ready/OK'.
7. Leave it like that and reconnect the ethernet/network cable.

After a few seconds your printer should have a new accessible IP address within the range of addresses for your network.
  1. Turning off the printer
  2. Pressing and holding the “Start Copy” and the “Cancel” button. (Easy, both are below each other.)
  3. Turning on the printer

Wednesday, November 26, 2014


Award and Phoenix BIOS:

1 short beep: Normal
2 short beeps: CMOS error
1 long and 1 short beep: DRAM error
1 long and 2 short beeps: Video card error
1 long and 3 short beeps: Keyboard error
1 long and 9 short beeps: ROM error
Long continuous beeps: DRAM not installed correctly
Short continuous beeps: Bad power supply


1 short beep: DRAM flash error
2 short beeps: DRAM ECC check error
3 short beeps: DRAM detect error
5 short beeps: CPU error
6 short beeps: Keyboard error
8 short beeps: Video card error
9 short beeps: ROM error
1 long and 3 short beeps: Bad DRAM
1 long and 8 short beeps: Video card error

Phoenix BIOS:

1-1-3 - CMOS read/write failure
1-1-4 - ROM BIOS checksum error
1-2-1 - Programmable interval timer failure
1-2-2 - DMA initialisation failure
1-2-3 - DMA page register read/write failure
1-3-1 - RAM refresh verification failure
1-3-3 - First 64k RAM chip or data line failure
1-3-4 - First 64k RAM odd/even logic failure
1-4-1 - Address line failure first 64k RAM
1-4-2 - Parity failure first 64k RAM
2-_-_ - Faulty Memory
3-1-_ - Faulty Motherboard
3-2-4 - Keyboard controller Test failure
3-3-4 - Screen initialisation failure
3-4-1 - Screen retrace test failure
3-4-2 - Search for video ROM in progress
4-2-1 - Timer tick interrupt in progress or failure
4-2-2 - Shutdown test in progress or failure
4-2-3 - Gate A20 failure
4-2-4 - Unexpected interrupt in protected mode
4-3-1 - RAM test in progress or failure>ffffh
4-3-2 - Faulty Motherboard
4-3-3 - Interval timer channel 2 test or failure
4-3-4 - Time of Day clock test failure
4-4-1 - Serial port test or failure
4-4-2 - Parallel port test or failure
4-4-3 - Math coprocessor test or failure
Low 1-1-2 - System Board select failure
Low 1-1-3 - Extended CMOS RAM failure

HP Multimedia PCs:

Continuous tone - Power supply defective
Many short beeps - Defective motherboard
1 Long - RAM refresh
1 Long, 1 Short - Defective motherboard or RAM-Basic
1 Long, 2 Short - Video Card error
1 Long, 3 Short - Error on EGA card
2 Long, 1 Short - Synchronization of monitor adapter
2 Short - Parity error (incorrect memory checksum)
3 Short - Errors in the first 64K of RAM
4 Short - Timer or counter defective
5 Short - Processor failure or Video RAM
6 Short - Error in keyboard Processor
7 Short - Virtual processor mode det (AT)
8 Short - Incorrect writing to Video RAM
9 Short - Wrong ROM BIOS checksum

IBM IntelliStation and IBM PC:

Beep error code
1-1-3 CMOS read/write error
1. Run Setup
2. System Board
1-1-4 ROM BIOS check error
1. System Board
1-2-X DMA error
1. System Board
1. Memory Module
2. System Board
1. Keyboard
2. System Board
1-4-X Error detected in first 64 KB of RAM.
1. Memory Module
2. System Board
1. Run Setup
2. System Board
2-1-X First 64 KB of RAM failed.
1. Memory Module
2. System Board
1. Video Adapter (if installed)
2. System Board
2-2-X First 64 KB of RAM failed.
1. Memory Module
2. System Board
1. Memory Module
2. System Board
1. Run Setup
2. Memory Module
3. System Board
3-1-X DMA register failed.
1. System Board
3-2-4 Keyboard controller failed.
1. System Board
2. Keyboard
3-3-4 Screen initialization failed.
1. Video Adapter (if installed)
2. System Board
3. Display

3-4-1 Screen retrace lest detected an error.
1. Video Adapter (if installed)
2. System Board
3. Display
3-4-2 POST is searching for video ROM.
1. Video Adapter (if installed)
2. System Board
1. Video Adapter (if installed)
2. System Board
All other beep code sequences.
1. System Board
One long and one short beep during POST. Base 640 KB memory error or shadow RAM error.
1. Memory Module
2. System Board
One long beep and two or three short beeps during POST.(Video error)
1. Video Adapter (if installed)
2. System Board
Three short beeps during POST.
1. See "System board memory" on page 62.
2. System Board
Continuous beep.
1. System Board
Repeating short beeps.
1. Keyboard stuck key?
2. Keyboard Cable
3. System Board

1 short beep
Normal POST completion
1 long 1 short
Refresh failure
1 long 2 short
Video configuration failed or parity error
1 long 3 short
Base 64 KB memory failure
1 long 4 short
Timer not operational
1 long 5 short
Processor error
1 long 6 short
8042 Gate A20 failure
1 long 7 short
Processor exception interrupt error
1 long 8 short
Display memory R/W error
1 long 9 short
ROM checksum error
1 long 10 short
CMOS shutdown register R/W error
1 long 11 short
Cache memory bad .. Newer Boxes have what we call idiot lights on the back and when you check them against your manual that also will let you know what the problem is.

Tuesday, May 27, 2014

Service,Ej-Adjust,PowerOnly MenĂ¼

So people. I would like to explain here as you without a special remote control via a laptop and audio software how serial WinAmp can open the service menu of the ch. This you need play just the individual AUDIO files on the laptop. and there is no magic, even if it sounds so.

So download this file down:

Unzip on your PC, and then have your 4 audio files:

So, now we need a headphone connector and an old remote control or an IR sensor. You must cut the plug and sensor solder the cable with IR (previously from the old remote control IR sensor from solder). Then it looks like this:

now, take your laptop and this plug with IR sensor inside the headphone jack.

Download now from the Internet the audio player "WinAmp" down (possibly others also go) and installed the program. Is the IR sensor on the TV and starts an audio file (with Service menu that you want to open) on the laptop. But first turn the volume up!

Woalla! The TV reports with password input. "0413" enter password for menu just yet.

Sounds unbelievable, what? but it works

Monday, April 14, 2014

Take a screenshot of a remote computer with psexec and nircmd



psexec, nircmd and Windows


Take a screenshot of a remote computer in your network and save it to selected location. Optionally save 20 screenshots every minute in a loop.


Download psexec from, download nircmd from
psexec.exe \\ -u "domain\administrator" -p "password" -i -c nircmd.exe savescreenshot "c:\shot.png"
shot.png will be saved on target computer

If you are logged on as administrator then you can skip -u and -p options, you can skip only -p then you will be prompt for a password.
psexec.exe \\ -u "domain\administrator"  -i -c nircmd.exe savescreenshot "c:\shot.png"
Save 20 screenshots every minute in a loop:
psexec.exe \\ -u "domain\administrator" -p "password" -i -c nircmd.exe loop 20 60000 savescreenshot "scr~$currdate.MM_dd_yyyy$-~$currtime.HH_mm_ss$.png"

Gain access to remote pc via console (telnet equivalent):
psexec.exe \\ -u "domain\administrator" -p "password" cmd

Thursday, December 5, 2013


debian inetd restart
After configuring /etc/inetd.conf

/etc/init.d/openbsd-inetd restart
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd -o document-format=application/octet-stream

Friday, October 25, 2013

Winbind, samba, proftpd

It is configured in the following way.

Winbind, samba, proftpd.
It uses kerberos and security = ADS

Now. Users can login via proftpd and their home directory is created by
There group is set to "Domain Users"

When logging in via a Linux command line ftp client, all seems to
function as expected, but when using a browser, this is where things go
wrong. First thing I notice is when compared to a "normal" (see
attachment "good.png") ftp  browser connection the folders/files are
listed out with a date. See the attachment "good.png" and look at the
difference between the file "hosts" in when compared to "nogood.png".
You will see the bad(un usable) files are listed with dates and the host
file in "good.png" lists without dates.

When I select the hosts file when it is in the "Domain Users" group, I
get this message from my browser.

    An error occurred while loading
ftp://simonj@ 04:43 hosts:
    The file or folder /home/STAFF/simonj/29 04:43 hosts does not exist.

See what it's doing? It thinks the date is a part of the name "hosts"

The "host" file is fixed when I change the group from "Domain Users" to
a normal unix group like "users".
But when I switch "DirFakeGroup on ~" on, the problem resurfaces, even
with the unix group "users" set.

I'm using proftpd-1.2.9-7mdk and I was using an earlier version that
comes with mandrake but I wanted to see if it was a version specific bug.

Any ideas, Can you suggest anything that I can try. Below are some of
the config files.

        workgroup = STAFF
        server string = Samba Server %v
        security = ADS
        realm = STAFF
        encrypt passwords = Yes
        #;server = dangnamit2.staff
        password server = *
        log file = /var/log/samba/log.%m
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        #;character set = ISO8859-15
        os level = 18
        local master = No
        dns proxy = No
        winbind enum users = Yes
        winbind enum groups = Yes
        winbind uid = 10000-20000
        winbind gid = 10000-20000
        winbind separator = +
        #template homedir = /home/%U
        template homedir = /home/%D/%U
        template shell = /bin/bash
        winbind use default domain = yes
        template primary group = "Domain Users"
        printing = cups
        unix charset = LOCALE

   comment = Home Directories
        browseable = yes
        writeable = yes
        preserve case = yes
        short preserve case = yes

pam.d/ftp file
auth       required item=user sense=deny
file=/etc/ftpusers onerr=succeed
auth       sufficient
auth       required service=system-auth
auth       required
account    sufficient
account    required service=system-auth
session    required service=system-auth

##auth       required item=user sense=deny
file=/etc/ftpusers onerr=succeed
##auth       required shadow nullok

# If this is enabled, anonymous logins will fail because the 'ftp' user does
# not have a "valid" shell, as listed in /etc/shells.
# If you enable this, it is recommended that you do *not* give the 'ftp'
# user a real shell. Instead, give the 'ftp' user /bin/false for a shell and
# add /bin/false to /etc/shells.
#auth       required

##account    required
##session    required


ServerName                      "ProFTPD Default Installation"
ServerType                      standalone
DefaultServer                   on
#DirFakeGroup on ~

# Allow FTP resuming.
# Remember to set to off if you have an incoming ftp for upload.
AllowStoreRestart               on

# Port 21 is the standard FTP port.
Port                            21

# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask                           022

# To prevent DoS attacks, set the maximum number of child processes
# to 30.  If you need to allow more than 30 concurrent connections
# at once, simply increase this value.  Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd).
MaxInstances                    30

# Set the user and group under which the server will run.
User                            nobody
Group                           nogroup

# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
#DefaultRoot ~

# Normally, we want files to be overwriteable.
<Directory />
  AllowOverwrite                on

# Needed for NIS.

PersistentPasswd              off

# Default root can be used to put users in a chroot environment.
# As an example if you have a user foo and you want to put foo in /home/foo
# chroot environment you would do this:
# DefaultRoot /home/foo foo

Any help or advice to this proftpd beginner would be welcome. TA

Here's what i've done to make it work:

<Directory /users/sca/*>
        <Limit WRITE>
                DenyUser sca

Integrate Linux with Active Directory using Samba, Winbind, and Kerberos

Integrate Linux with Active Directory using Samba, Winbind, and Kerberos



This is the summary of my experience setting up a Linux machine to become a member of an existing Active Directory domain.
Last year I was new to an organization that has an unhealthy affinity for Dell. Anyway, we needed some more storage space, so my solution was to build a server from parts and use Centos 5.1 and Samba to share files with the Windows domain. I wound up with a 3U file server with a 12 TB Raid 6 array with a hot spare (redundancy is serious business) for just shy of $4,000. Given the cost of a similar solution from Dell, major brownie points for me. But, I digress. Here's the meat and potatoes of getting a linux box to play well with an AD environment.
I hope this helps someone!

Get your linux box configured, with the relevant packages installed.

So, you've got your server/workstation up with your favorite flavor of linux installed, and it's time to join the Windows domain. For this, we'll be needing samba and kerberos. Most distros come with samba installed, but it's best to go ahead and grab the newest version either from your distro's repositories or the samba website itself. Also, make sure you have the krb5 packages installed.

Time synchronization...

AD is very picky about the time matching during authentication, so you'll need to point the ntpd process to a server on your network. A domain controller is a good choice.
On redhat flavored linux (CentOS, RHEL, and maybe SuSE, I'm not sure on that one) you can configure NTP without editing a .conf file like so:
ntpdate HOSTNAME
For debian flavored linux, edit /etc/ntp.conf with your favorite text editor. Real men use vi. You'll see a servers section; just replace what's there with one or more NTP servers on your domain, like so:
server HOSTNAME iburst dynamic
Now, restart the NTP service like so:
service ntp restart
/etc/init.d/ntp restart
/etc/rc.d/init.d/ntp restart
depending on your particular brand of *nix.
Make sure it's working with the following command:
ntpq -p
You'll see some output that should include the NTP server you pointed it to, and some stats.

Edit /etc/hosts

Add this line to /etc/hosts for each domain controller: adserver.yourdomain adserver

Edit /etc/krb5.conf

Edit /etc/krb5.conf to look something like this:
ticket_lifetime = 600
default_realm = YOURDOMAIN
default_tkt_enctypes = des3-hmac-sha1 des-cbc-crc
default_tgs_enctypes = des3-hmac-sha1 des-cbc-crc
kdc = ip of you ads server
default_domain = YOURDOMAIN
.yourdomain = YOURDOMAIN
yourdomain = YOURDOMAIN
profile = /etc/krb5kdc/kdc.conf
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmin.log
default = FILE:/var/log/krb5lib.logog

Test kerberos authentication

Enter the following at the shell to test kerberos authentication:
kinit username@DOMAIN
It will prompt for a password, and if all is well, return you to the prompt.
Use the command klist to verify you received a ticket. If you have a ticket, then you're doing great. If not, double check your /etc/krb5.conf file.

Configure Samba and Winbind to be a domain member.

Almost done. Now we need to edit the /etc/samba/smb.conf file. I'll include the important parameters. Your smb.conf file should look something like this:
workgroup = domainname
password server = hostname of domain controller
wins server = IP of wins server
realm = DOMAIN
security = ads
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/bash
winbind use default domain = false
winbind offline logon = false
winbind separator = + <<very important, as the default \ character does strange things in unix/linux.
allow trusted domains = Yes <<if you have them
Those are the important bits, but you'll find that there are hundreds of valid parameters for the samba config file. Explore them; it's a very powerful program.

Tell linux to allow winbind to handle authentication.

Edit your /etc/nsswitch.conf to look something like this:
passwd: compat winbind
shadow: compat
group: compat winbind

Moment of truth: Join the domain.

Once the /etc/samba/smb.conf file is properly edited, enter the following at the shell:
It gives you the rundown of your samba config file, and will let you know if something is wrong. If all is well, it's time to start the smb and winbind services, like so: (depending on *nix flavor)
service smb restart
service winbind restart
/etc/init.d/smb restart
/etc/init.d/winbind restart
/etc/rc.d/init.d/smb restart
/etc/rc.d/init.d/winbind restart
If they both come back up fine, lets move to joining the domain, like so:
net ads join -U DOMAIN+username%password
Then test the join using:
net ads testjoin
If it reports "Join is OK", the test winbind:
wbinfo -u <lists all of your AD users>
wbinfo -g <lists all of your AD groups>
If it works, your linux box is now integrated into the AD domain.

Lastly, configure the smb and winbind services to start automatically

Every distro has a different way of doing this, so I won't delve into too much detail. Just have a google on it; theres a wealth of information out there.

install proftpd
useradd userftp -p your_password -d /home/FTP-shared -s /bin/BASH <----> bin/false dont work



That should do it. If you run into errors, I may be able to help you. I had a bumpy road getting this up and running, but in the end this is what worked.
Enjoy, and again, I hope this helps someone.