Blog

Telstra Call Forward codes

These codes are used for land lines or mobiles  that use Telstra as a provider.

Turn on Call Forward: **code*(phone number to forward calls to, including area code)*10#
Turn off call Forward: ##code**10#
Check if forwarding is on: *#code#

Where: “code” is:
21 for “All calls”
61 for “No answer”
62 for “Unreachable”, ie “out of coverage”
67 for “Busy”

Specifically for “no answer”, you can set the duration your phone rings before it diverts using the the following:
**61*(phone number to forward calls to, including area code)**(number of seconds)#

This was compiled from the following Telstra pages (though I will point out that none of the pages mention the “unreachable” diversion – this oversight should be corrected):

https://go.telstra.com.au/helpandsupport/-/turn-call-forward-on
https://go.telstra.com.au/helpandsupport/-/turn-call-forward-off-on-your-mobile
https://go.telstra.com.au/helpandsupport/-/check-if-call-forward-is-turned-on-or-off-on-your-mobile

https://go.telstra.com.au/helpandsupport/-/change-ring-time-before-calls-divert-to-messagebank-on-yo

 

source: https://crowdsupport.telstra.com.au/t5/General-Mobiles/Call-Forwarding-Codes-Mobile-Network/m-p/150164#M2521

 

Posted in: Blog, Technical

Leave a Comment (0) →

Block WordPress Attack with CSF

Edit /etc/csf/regex.custom.pm and add:

Code: Select all


# wordpress
if (($globlogs{CUSTOM4_LOG}{$lgfile}) and ($line =~ /(\S+).*] "POST \/wp-login\.php.*" 200/)) {
return ("Failed WordPress login from",$1,"wordpress","20","80,443","3600");
}

Then update /etc/csf/csf.conf and change CUSTOM4_LOG to scan your web server access logs. (If they aren’t doing so already). Eg. for Plesk: /var/www/vhosts/system/*/logs/access_log

That rule will block brute force attacks to wp-login.php for one hour. If you want to block them permanently just change the 3600 to 1.

Source: https://forum.configserver.com/viewtopic.php?t=8886#p25432

 

Posted in: Blog, Technical

Leave a Comment (0) →

How-to Reset Password on Xerox

If you have forgotten a password on a Xerox Workcentre 5225 you won’t find any documentation on Xerox’s website on how to reset the password. If you ask them they will tell you that a technician (who you have to pay) will need to reset it. There is a way around this however. You can enter what is called “debug” mode and reset the password if you have lost the password to the printer (WARNING: Do not try adjusting anything in debug mode that you do not know how to do as it could have negative effects). In order to enter debug mode you will need to hold down the 0 button on the control panel for approximately 5 seconds, then while still holding this down press the start button. You will then be prompted to enter a passcode. The default is “6789”. Now that you are in debug mode you can change the username/password just like you would if you had already logged in as the admin as follows: [more]

  1. Press the <Machine Status> button on the Control Panel.
  2. Press the [Tools] tab.
  3. On the Tools screen press the [Authentication/Security] Settings.
  4. Press [System Administrator Settings].
  5. Press [System Administrator’s Login ID]
  6. On the System Administrator’s Login ID screen, Select [Keyboard]
  7. Type in <username here> for the Login ID, and select [Save]
  8. On the Retype line, select [Keyboard]
  9. Enter the same Login ID, and select [Save] twice.
  10. If prompted [Do you want to change the System Administrator’s Login ID?] select [Yes]
  11. Press [System Administrator’s Passcode].
  12. On the Passcode screen, Select [Keyboard].
  13. Type in <Passcode here> for the [New Passcode], and select [Save].
  14. In [Retype Passcode], select [Keyboard].
  15. Enter the same passcode, and select [Save] twice.
  16. In the [Do you want to change the System Administrator’s Passcode?] screen, select [Yes].
  17. If prompted choose to reboot the machine after the changes have been made.

Posted in: Blog, Technical

Leave a Comment (1) →

How to replace failed hard drive on NetApp FAS

How to replace failed hard drive on NetApp FAS

What:

NetApp FAS270, FAS2020, FAS2040, FAS2240, FAS2050

Problem:

Hard drive has failed and needs replacement.

Solution:

Disk will have an amber LED on the front of it if it has an issue. You will need a disk of the same capacity as the one you are removing or larger, also make sure disk is the correct type for the shelves that you have.
You can identify failed disks by logging onto the controllers command line via SSH and running the following command:

aggr status -f

-f will identify any of the broken disks.
Output should give you a <disk id> i.e. 0c.00.10

If the LED is not lit in which some cases this can happen, you can illuminate it.

SSH onto the NetApp box and logon (if you haven’t done it already) and switch to advanced mode.

priv set advanced
led_on <disk id identified above>
led_off <disk id identified above>
priv set

Alternatively you can use blink_on & blink_off instead of led_on & led_off.

Remove drive from the shelf and wait for 60 seconds before inserting a new one.

When new drive is in place run the following command to check whether the ID of the disk you have just fitted is owned or not.

disk show -n

If disk auto assign is enabled it’ll be assigned to the head which had the failed disk, if not you will have to do it manually.

disk assign <disk id>

If it won’t accept the command, it might have been auto assigned to the wrong controller/system.  You can clear the assignment from the disk using the following command then try again.

disk assign <disk id> -s unowned -f

The replaced disk will now be assigned as a spare disk to replace the spare which was used when the original failed.
You can check Status of this using following command:

aggr status -s

To check auto disk assign feature use:

options disk auto_assign

The output will either show on or off.

source: http://rawtechnology.blogspot.com.au/2013/02/how-to-replace-failed-hard-drive-on.html

 

Posted in: Blog, Technical

Leave a Comment (1) →

Using CheckSUR and fix Corruption

These are just notes for myself. I will rewrite this article when i get to the bottom of the issue i’m fixing.

Using CheckSUR and update packages to fix corruption

How to extract msu/msp/msi/exe files from the command line

I find these commands quite helpful — maybe you know them already — if not, here you go:

Microsoft Hotfix Installer (.exe)

setup.exe /t:C:<target_dir> /c

Microsoft Update Standalone Package (.msu)

expand -F:* update.msu C:<target_dir>
cd <target_dir>
expand -F:* update.cab C:<target_dir>

Microsoft Patch File (.msp)

msix patch.msp /out C:<target_dir>
msix.zip

Windows Installer Package (.msi)

msiexec /a setup.msi /qb TARGETDIR=C:<target_dir>

 

https://blogs.technet.microsoft.com/roplatforms/2010/05/12/how-to-fix-server-manager-errors-after-installing-updates-hresult0x800f0818-hresult0x800b0100/

 

 

Posted in: Blog

Leave a Comment (0) →

Exchange 2010 The mailbox dumpster size exceeds the target quota

Moving some customers mail boxes around i kept getting a error about dumpster size exceeding the target quota.I couldn’t find much info on it. But this seems to fix it.
1.) Give your account rights to open the mailbox.
2.) Go to control panel > mail > profiles > ask for a profile each time outlook opens
3.) Open Outlook > New profile > input appropriate info for mailbox and users alias > UNCHECK “cached exchange mode” > open the users mailbox once w/ Outlook, then close Outlook.
4.) Open MFCMapi (if Outlook is x64, then use x64 of MFCMapi)
5.) ok > Session > Logon and display store table
6.) Select the profile for the user you added.
7.) Double click “mailbox – user”
8.) Expand “Root Container” > right click on “Recoverable Items” and select > open contents table
9.) Give it a min to enumerate all items
10.) Select any unwanted items and right click “delete message”
11.) You can also expand recoverable items and then highlight purge or deletions and open the contents table for those as well.
12.) Then close windows until you get the original one and logoff.
Be careful with MFCMapi as it can cause serious damage to a mailbox.
Source https://social.technet.microsoft.com/Forums/exchange/en-US/0afd1d0e-7fe1-461f-a6f2-40908554852d/exchange-2010-purge-items-in-recover-deleted-items?forum=exchange2010

Posted in: Blog, Scripts

Leave a Comment (0) →

Windows 10 Bootrec – the requested system device cannot be found

After cloning a SSD for a customer it wouldn’t boot after running the normal

Bootrec /fixmbr
Bootrec /fixboot
Bootrec /scanos
Bootrec /rebuildbcd
But the Bootrec /rebuildbcd wouldn’t work with a error  “The requested system device cannot be found”

after spending time looking in to this issue i found a  forum post that fixed it right up.

Firstly, boot from a UEFI Windows 8/10 recovery disk (CD/DVD/USB) – I found that the automated recovery process didn’t find the correct Windows partition, nor when I managed to add it to BCD settings would it make it reliably bootable e.g. using BCDEDIT I got it to find and launch the Windows partition but it refused to cold boot or would not “keep” the settings after a 2nd reboot or power off.

Go into the Advanced options and run the Command Prompt.

Enter diskpart to use the DiskPart tool to ensure you have all the right partitions and to identify your EFI partition – the key thing here is that your EFI partition is formatted as FAT32:

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> list vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 B  No Media
  Volume 1     C                NTFS   Partition    195 GB  Healthy    Boot
  Volume 2         WINRE        NTFS   Partition    400 MB  Healthy    Hidden
  Volume 3                      FAT32  Partition    260 MB  Healthy    System

Then assign a drive letter to the EFI partition:

DISKPART> sel vol 3

Volume 3 is the selected volume.

DISKPART> assign letter=b:

DiskPart successfully assigned the drive letter or mount point.

Exit DiskPart tool by entering exit and at the command prompt run the following:

cd /d b:\EFI\Microsoft\Boot\

bootrec /fixboot

Delete or rename the BCD file:

ren BCD BCD.bak

Use bcdboot.exe to recreate BCD store:

bcdboot c:\Windows /l en-gb /s b: /f ALL

The /f ALL parameter updates the BIOS settings including UEFI firmware/NVRAM, /l en-gb is to localise for UK/GB locale. The localisation defaults to US English, or use en-US.

Reboot and cross your fingers.

Source http://superuser.com/questions/460762/how-can-i-repair-the-windows-8-efi-bootloader

 

Posted in: Blog, Scripts

Leave a Comment (219) →
Page 5 of 15 «...34567...»