Custom 404 Errors - Persisting original page's query string

Hey all,
On my local setup of IIS, I have a single application's Custom Errors set so 404's go to an aspx page. When the 404 kicks in, the URL in the browser stays the same as the non-existant URL, and the 404 page shows. I am able to get the query string of the non-existant requested URL, and use it to find related pages.
Now, when I bring this live, I have the entire website's Custom Error 404 set. When the 404 kicks in, it redirects to the 404 page with query string "404;http://blahblah.com/page.ext", cutting off the original URL's query string. This kills my ability to offer related pages based on the query string.
Does anyone know how I can fix this? Works perfect locally, doesn't work remotely. Thanks in advance!

Are you and your host using same version of IIS?

Good question. My local version is 5.1, the remote IIS app is setup slightly different (no About menu item) - the help file says 5.0.

Have you asked your host about this?

We host or own. I would think that if the query string were attached, it would either hide the new URL (301 redirect, I think?) or convert the original URL to be URLEncoded so the "?" wouldn't appear twice. Also, HTTP_REFERER does not give the original URL. This is driving us crazy, please help!

Still unable to find a solution to this... I read about a user on another forum with the same problem, and they concluded that it was not possible, but I fail to believe that!

Sorry I can't offer any help. Perhaps some site like iisfaq.com can help, or some site from this google search

http://www.google.com/search?q=iis+...:en-US:official

Thanks Doug, from going to iisfaq.com I found out that this "problem" is more of a "feature" that has to be specified per file extension. The main file extension I was using as ASP, and that apparently has it's own 404 handling, so turning it on in IIS for .ASP files solved the problem. Thanks!

Hey, I'm glad you got it sorted out!