Remember: Please write in the comments area whether or not you had success with this solution, and share other ideas.

Issue: When clicking on “Older Posts” which brings you to the URL “page 2” (page2), you get a 404 error page.

Problem: Apache mod_rewrite is disabled –or– “AllowOverride” is set to “none” in your Apache configuration file for the virtual server.

Solution: In my case, the problem was with AllowOverride being set to none.

Simply look though your Apache configuration file, and change “none” to “all” for AllowOverride.

Here is an example of what this should look like:
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride all
</Directory>
<Directory /var/www/>
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Order allow,deny
allow from all
</Directory>

WARNING: You should only change AllowOverride to all for the web directory. (Exclude all other items, such as CGI or usr/share/doc). Leave these alone!

Solution 2: This second option works, but does not fix the underlying problem.
Go to your Permalinks settings page in WordPress. Under “Custom Structure”, add /index.php before the line.
Eg:
/%year%/%monthnum%/%day%/%postname%/
should look like this:
/index.php/%year%/%monthnum%/%day%/%postname%/

All links will go through index.php. If you change these links back to not having index.php, they will still redirect properly.

Solution 3: Go without custom permalinks structures.
The disadvantage is that Google doesn’t like these, since the actual link tells Google nothing about the page. For higher ranks in searches, you should avoid this.
Simply go to the Permalinks settings page in WordPress, click “Default” and save changes.

A general reminder: It’s usually a bad idea to constantly switch permalinks. It places you farther behind in Google because your links are always becoming broken. Choose a structure, and stick with it!

One of the worst things you can do for a network is give every computer random names. I work for a school district, and we use the following name scheme:
<School>-<Room Number><Student or Teacher><Number>
So, for an elementary school student computer in room 106, the first computer going from the left side of the room when you walk in all-around back to the door would be called:
ELEM-106-s01
(the “S” is for student, “T” for teacher, “nb” for notebook)

The advantages:

Looking through Ghost, Active Directory, or Desktop Authority, we can know instantly where a computer is.
It’s alphabetical, so any computer is easy to find.
It’s easy to remember.
I can instantly know what side of the building it is on based on whether it is elem (elementary) or hs (high-school).

“What about Descriptions”
Though it is true that you can set up descriptions instead of giving proper names, a program such as Ghost will not display these in any sort of order based on location.

Other Naming Schemes:
Many buildings do not have room numbers. You should look at naming computers after their floor and department.
For mobile computers, you might even consider using the primary users name (eg: nb-jesse-zylstra) if the computer moves around a lot.

“Windows could not log you in. The trust relationship between this computer and the primary domain failed.”

If you have ever seen this error, and said to yourself:”*@*$&@@ !! How the !*$&@^@ did this happen?” then I am totally with you.

What this means:
Really, I have no idea. Nor why it happens, or why XP never had this issue but Vista and 7 do. Essentially, it’s a security thing when either the client or the server has reasons not to trust the other.

How to fix it:

1. Unplug the computer from the network, and log in using cached credentials.
2. Drop the computer from the domain by changing the domain name to a workgroup.
3. Reboot the computer.
4. Log in using the built-in administrator account (you should make sure you know this before dropping it from the domain! Otherwise, you will need to create this user by alternative means).
5. Join the computer back to the domain,
6. Reboot.

If this fails, you can try another method located here:
http://community.tigranetworks.co.uk/blogs/tim_long/archive/2009/05/16/windows-7-rc-failed-trust-relationship.aspx

“Account Already Exists” error on Windows 2000, XP, and Windows 7/Vista indicates that Active Directory already has the computer listed. You can not have two computers of the same name, even if one is offline. (If the other is online, you will see: “Duplicate Name on Network”. More about this further down)

How you fix it:
Log in to your Active Directory computer, and go to “Active Directory Users and Computers”. Find the computer name you wish to use and delete it.
Return to the computer, and set the computer name as you normally would. (Sometimes, Active Directory changes can take a short period of time before actually taking place. Also, if you have multiple Active Directory computers, you may run across the issue of having to wait for them to synchronize the change).

How to avoid it:
Before changing the name of any computer, you should drop the computer from the domain. The best way to do this is to switch the computer from being on the domain to being on a workgroup. The computer says: “I’m leaving” to the Active Directory server, and Active Directory drops the computer from it’s database.

Duplicate Name on Network:
You must find the other computer name and change it before you can use the name without receiving this error. You should still be able to log in and use the computer with this error, but it is very bad network practice to do so.

If you are failing to get computers to show up in Ghost, and you tried the standard troubleshooting that Symantec recommends (turn firewall and AV scanner off, disabled simple file sharing, etc), here are a few things you may want to try:

First off, if you renamed the computer, Ghost doesn’t magically know about this. A point I should make is that Ghost’s directory of computers connected and Active Directory’s computers listed are completely separate. It may take a while for Ghost to actually get the name. What you can do is run a refresh of configuration and inventory on the old computer name. If you forgot the old name, you may just have to do a refresh on the entire network and wait a few hours.

Second, though the “client heartbeat” or whatever they call it now is usually 20 seconds, it’s not as if the client is giving data back instantly. It’s just saying: “I’m here”. Give it ten minutes, or so.

Third, tried these steps and got nothing? Did you exit Ghost Client and open it again? I’ve had instances where new computers just won’t show up until I do this.

Fourth, hit the Ghost server with an electro-magnet. This will disturb the contents of the hard drive, resulting in quick corruption, forcing you to start the whole thing over again.

Last, “In rare cases”, as Symentec says, it can take up to 24 hours for a computer to appear in the Ghost Console. I’ve had this happen, but you might as well try everything else first. And, if this fails (last last, I should call it!) reboot the Ghost server.

The very last of the last: If you are having trouble getting any computer at all to appear in the Ghost Console, first check to make sure you have enough licenses to connect all of your clients. Second, call Symantec. This is an expensive program with many minimum-wage tech support people desperate to talk to you. Third, consider uninstalling Ghost and reinstalling it. (First, reinstall the client, if that fails, reinstall Ghost altogether).