WordPress MU

I am having some small problem with page redirects. When clicking a link that points to a page such as http://user.blogserver.mydomain.tld/about/ I get a 404 message. Any of my users can log in and be taken to their management page. The blogs themselves are viewable. However links such as "about", "archives", and "categories" do not work on any users webpage.

The server log reports the following

[Thu May 03 15:08:45 2007] [error] [client 192.168.0.22] File does not exist: /var/www/about, referer: http://user.blogserver.mydomain.tld/

Even though the redirects to the subdomains are working, redirects to pages on those subdomains are not. Here is my htaccess file:

RewriteEngine On
RewriteBase /

AddType x-mapp-php5 .php
#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

Thank you for the help!

Where is the software installed within that URL?

You have turned on wildcards with DNS and Apache, right?

WPMU is in /var/www

I have wildcard dns turned on both locally on the Debian box and a delegation in the Active Directory. So whenever a user in my domain logs into the WPMu server they can see their management page at http://user.blogserver.mydomain.tld/wp-admin and they can see their blog page at http://user.blogserver.mydomain.tld however clicking on the "about" link which should take them to http://user.blogserver.mydomain.tld/about/ takes them to the 404 with the above error message. I'm stymied. I'm fairly certain that mod_rewrite is working since the user.blogserver.mydomain.tld is getting the right redirect. The pages in subdirectories at those domains don't get the proper redirection. http://user.blogserver.mydomain.tld/about/ should take me to a WPMu generated webpage as well, but instead its looking for /var/www/about.

And you've set permalinks in the back end to something other than the default?

I put the dot in "date and name based" and tell it to save, however it always resets itself to Custom Structure: /blog [/%year%/%monthnum%/%day%/%postname%/]

WPMU is in /var/www

For reference, that's a file directory, not a URL.

What URL does /var/www match up with? Does it match up with http://blogserver.mydomain.tld?

Yes http://blogserver.mydomain.tld does indeed point at /var/www .

Clicking on the link to
http://myuser.blogerver.mydomain.tld/2007/05/02/it-works-whee/ also gives a 404 even though the post is visible from http://myuser.blogerver.mydomain.tld/

:-/

I've been whacking on this problem still and noticed that the 404 errors I am getting sounded exactly like what was being talked about in this thread http://mu.wordpress.org/forums/topic.php?id=3880&replies=8
I followed lunabytes advice and added the AllowOverride FileInfo Options to the correct spot in the default site file. I restarted apache and then opened the webpage again to discover that it breaks php when I add either of those two options. instead of the server processing the script my browser asks me where to save the index.php file. I think I may go apply a wall directly to forhead for a bit...

Silly problem. Silly Solution. Thanks for the suggestions both here and in previous posts which have been a FANTASTIC resource. Especially those by Drmike and Lunabyte. The solution was to add FileInfo <i>Indexes</i> Options to the default site. Restart apache. Tadaa. Again, thank you!

Indexes? That's strange. I don't remember that coming up before.

LOL! Now you have me wondering if all the stuff I was doing was only so much Chicken Waving and the problem is something that fixed itself... Oh well, if the chicken works...

I have exactly the same problem on only ONE of my wpmu blogs. All the others work fine but, recently, one of them has started to throw up 404 errors on the post links from the blog entry page

This is on a hosted server and I'm not certain how to implement the fix you've mentioned above: FileInfo <i>Indexes</i>

It's very bizarre because it only affects one of four blogs. The others are just fine.

Any ideas?