MACOSX Time Machine to NAS connect error


Hello World.

Mountain Lion is out – yay (or roar?)! I’ve decided at the same time to setup a Time Machine to backup over wireless to my Zyxel NSA310…

What a painful process. To start with I wanted to backup to the USB drive connected to the NAS – wouldn’t want to have it. The firmware for some reason only enables you to enable Time Machine for shares that are on your internal drive… So I gave it a few days thought and decided to move everything from the internal drive to the USB, and use the internal drive for Time Machine. Ok… You thought it was the end of my problems? – NO.

When I selected the NAS share in Time Machine preferences it asked me to input the credentials for the NAS, – which I did and pressed connect. As I did so, I was presented with an error titled the operation could not be completed osstatus error 2Great!

I’ve started googling, and did get a few solutions to try out – but none worked. I’ve tried setting up different users, setting up different sharing/permissions – nothing worked.

What I ended up doing is re-enabling the admin folder which was created automatically with the NAS’s setup (it was disabled as I didn’t use it) – and Time Machine connected with no error to that folder once I selected it as a share. I then tried to point back to the “TimeMachine” folder for TM access – error again. It sort of seems you can only get access by using the pre-built folders on the NAS.

It turns out the problem is not Zyxel NSA310 related, as people on forums experience the same problem with different devices.

If you encounter the problem, I hope this helps you!

Advertisements

OSX Flashback Trojan Fix


Hello All.

This is absolutely not the best reason to write  blog. This is one of the worst ones. At least for a person like me, an active member of the MAC community. It is sad, but we have to be realistic. This day was expected to come when something major hits the MAC. Apple have been busy making these amazing computers, and now as they become more and more popular there’s more people aiming to attack us using them.

The attackers used a vulnerability in Java to insert malware onto the machines. In case with Apple, who have their own custom version of Java, they sadly are usually quite late with updating it. So in this scenario, even if you were up-to-date with your software you could get the malware onto your machine, just by visiting a compromised web site which contained malware (a lot of major web sites affected by this), it would use the Java vulnerability to install itself onto your machine without you even noticing. No user interaction required whatsoever.

Going back a number of months it was acting a fake-flash installer that you would download, and by installing which you would get malware onto your machine, so you would have to actually accept the installation of the so-called “flash” which would prompt for installation after you visiting a web site for example.

The attackers are forming a botnet (What is a botnet?) of Mac users to be available for spamming/monitoring/data theft, you name it.

Now how do we go about understanding if you have it, removing it and making sure we protect ourselves. First of all, everybody and always has to make sure their software is up-to-date. No excuses. I see no reason people not updating their software, if their computer can run it. There is really no reason. And make sure that you are using an Apple Supported OS – so you have to be on Snow Leopard or Lion. Anything under – you’re not safe.

Quite a few nice people on the internet have came up with a few ways of looking up if you have the trojan, and how you can remove it.

One of my most respected podcasters Bart Busschots has combined instructions to check if you’re infected from F-Secure and Tidbits. You can find the instructions on his blog at http://www.bartb.ie – the direct link to the article is here

But all it takes is to download a script, run it. And it will identify if you’re infected. If you’re not – happy days. If you are… You have to follow the instructions on the F-Secure web site. And at the time of me posting this, Kaspersky have came up with a removal tool – the direct link to download is here.

Ok people. This is a sad news, but I keep you updated. Stay on the ball, safe, and careful!

How to resolve Remote Buddy Express Plex Volume Issue


Hello everyone. I have found  a workaround for a major issue there is between Plex and Remote Buddy Express.

I’m sure I’m not the only one who came across the problem. This is when using Remote Buddy Express to control Plex, and hey, your volume doesn’t work. It just sits at -0db. It has worked for me in the past, but it seems that after I’ve reinstalled Lion and put the apps back on it doesn’t. Whether it’s a new version or similar – I have got no clue.

I’ve digged into the forums, came across a few solutions, which didn’t really address the issue, however when combining the information from different forums I came up with a solution. There is two ways you can do it, depending if you want the system volume to change when using plex, or plex volume to change.

But essentially I’ve mapped the keys to act as volume change when holding the up / down (plus / minus) keys, rather than just pressing them. As pressing them in a normal way doesn’t seem to be handled correctly on either side of the apps.

Go into remote buddy express preferences.

Go to the Mapping screen, select Plex on the left hand side, and adjust the settings that way:

By the way we’re only editing the top section – for the apple remote. My settings on the Virtual Receiver page are altered as I was trying suggestions from other places that didn’t seem to help me.

I hope that helps. Any questions – feel free to ask in the comments!

27″ iMac Wireless Interference


So as some of you may know, I work for TalkTalk Group, in the residential technical support, 1st line. We get quite a few interesting issues, some of them are funny (I might post a few of those later), some of them are quite hard to resolve, and some point out to some potential hardware issues. I have never came across anything like that before anywhere on the Internet, being a mac geek and a huge podcast fan, so I decided to write about that on my own blog.

So the story is that I had a customer who has called in with an intermittent wireless connection issue. He has one of TalkTalks Huawei HG520b routers which is situated on the ground floor of his house. According to my systems in work his router was connected at a maximum sync speed of 20.1Mb.

He has got a 27″ iMac on his 1st floor upstairs at a distance of around 15-20 meters away from the router. The iMac had trouble connecting to the wifi and was only getting 1 out of 5 signal bars. We have moved the router upstairs, connected an Ethernet cable, and changed the wireless channel so he could connect wirelessly and get 5 bars on the same distance.

Now when running a speed test, he could only achieve around 6Mbps. To which my answer was WTF?

Now here’s the most interesting thing and why I have decided to blog about this. I told the customer I had an iMac before, it was a previous generation though, and I had a couple of issues with wifi on it, a the whole back on the new machines is aluminium apart from the apple logo, which is in black plastic, where the actual wifi chip is located, it can cause huge interference.

The customer then said, what if I turn the machine the other way round, so it’s back would face the direction to the router. It may sound ridiculous. But we’ve done that. Guess what was the speed result? 14.5 Mb! He turned it back and it was 6 again. So realistically, that huge aluminium back can cause huge problems. Now the main thing that worried me is that it would mean that the local are speeds were limited to 6Mb! While the router is a standard 54g. Clearly the Internet connection is faster than the guys local area network can handle.

I have advised the customer to have a word with apple regarding that issue, because it really seems like a problematic unit. Hope some of you guys found that interesting, thanks for now!

Cheers,

Aleksandr.