Posts filed under 'Computers'
Godaddy.com are great for domains but their domain pushing process can seem overly complicated unless you’ve been through it several times.
(Lately, there appears to have been a glitch whereby if someone pushes a domain to your account, the domain doesn’t appear in the appropriate section (Pending domain changes) and it looks as if it didn’t come through.
Fear not! It’s there! You just have to go through the process.)
Pushing a domain from one Godaddy account to another.
Here’s how to push a domain from your Godaddy account to someone else’s Godaddy account.
Firstly, log into your Godaddy account.
Then choose,
Domains > Manage domains to take you to the domain manager.
Tick the checkbox next to the domain you wish to push to another account. Follow this by clicking ‘Account Change’ (arrowed)

Now you need to fill in the Registrant details to that of the person to whom you want to push the domain name.

Be certain to use the proper email address as this is where the “Change of Registrant” email will be sent.
Click on “Ok”.
That’s it! The process to push the domain to another account has begun. From your end, nothing further need be done.
How to receive a domain pushed to your Godaddy account
Assuming you have received the “Change of Registrant Pending” email from Godaddy you should follow these steps.
Log into your Godaddy account.
Click on “Pending Account Changes”

This will take you to the “Pending Account Changes” page.
Click on “Accept Account Change” (top right, arrowed)

Then enter the Transaction ID and Security code. Click “Continue”

That’s all there is to it!
Simply click through the checkout process (don’t worry, it’s free - i.e. Total: $0.00) and you are done.
You should then receive a confirmation email from Godaddy.com to confirm that the domain name has been transferred to your account.
This process will work even if no domain is showing in the “Pending Account Changes” box so long as you have received the “Change of Registrant Pending” email containing the Transaction ID and Security Code.
July 2nd, 2007
Some time ago when installing a home wireless network I made the mistake of leaving it unsecured. Trying to get three computers to talk to the network with impatient children snapping at my heels the entire time was, at the time, something of a challenge and I was too lazy to research the subject. Then I received a ‘heavy user’ warning from my ISP.
I knew it wasn’t my own home network that was burning up the bandwidth so it had to be someone nearby tapping in and helping themselves. My mistake, I shouldn’t have left an open network.
Biting the bullet, I researched (read a page) on how to secure a network and implemented the WEP (
Wireless Equivalent Protection) security protocol - a 26 Hexadecimal (Hex) character (0-9 and A-F) encyption method.
Encryption - is it difficult?
Encryption sounds much more complicated than it actually is - much like getting two Bluetooth enabled mobile phones to pair up and share information, a key known only to the two devices is entered into both the computer(s) and the wireless (WiFi) modem - if they match, bingo, you can access the Internet.
WEP wasn’t safe but who would bother me?
Since I was already ‘on the case’ I dug into the whole Wireless encryption subject and was frankly shocked at what I discovered - WEP just wasn’t safe. Still, I was just some anonymous person - who would go to the trouble of trying to crack my WEP key, right?
It didn’t take long for me to find out! Just two days after encrypting my wireless network using WEP I received a strange phone call. The anonymous person on the other end asked me if my ISP was Tiscali. I replied in the affirmative thinking it was my ISP calling and waited on a response. None was forthcoming but in the background I could hear someone furiously tapping on a keyboard. It took me only a few seconds to realise what was happening, at which point I hung up and immediately got to work upgrading the WEP encryption to WPA (Wi-Fi Protected Access).
So what was going on that caused me to slam down the telephone and immediately switch my Wi Fi encryption to the more secure WPA?
The purpose of the phone call and the furious tapping on the keyboard I could hear in the background was what’s called a packet flood and capture. Remember I said I’d dug into Wireless security a bit deeper than simply finding out about WEP? Well, I came across an interesting story about how the FBI could crack a WEP key - any WEP key - in under three minutes using freely available software (current advances can crack a WEP key in 20 seconds).
The steps are straightforward enough if you have a packet sniffer - computer software or computer hardware that can intercept and log traffic passing over a digital network or part of a network. As data streams travel back and forth over the network, the sniffer captures each packet and eventually decodes and analyzes its content. Used in conjunction with other software your WEP key gets spat out allows free and full access to your internet connection and quite possibly all of the data on your computer.
BT (British Telecom), one of the UK’s largest broadband providers, ships out what it calls the “BT Home Hub” and unbelievably, it cannot support WPA, only WEP. Kudos to BT.com for trying to introduce mandatory security to their broadband modems but shame on them for restricting it to WEP only.
May 1st, 2007
Next Posts
Previous Posts