Hey Charlie
For clarification, yes, I am having issues with the 404. Though old, antiquated and we have much better practices now, the old site was designed in the manner that the user could request pages that don't exist, ie domain.com/this/that, and this would result in a 404 that IIS was setup to route to an index.cfm file. At that time, CF would look at the request, parse the requested URL from the 404 key in the URL struct, and build the page as requested. I am still getting the situation where on 1 load the whole page comes up fine, reloading the same page may then result in a connection reset or part of the page loading.
I'm not sure I understand your message "What what the recording involve to get around this?" If you can clarify, I'll answer in hopes of troubleshooting this.
I sincerely appreciate your offer to help troubleshoot this. And even in helping to troubleshoot, I could not value a man's time at nothing; it wouldn't feel right. But our budget has been scrimped and scraped down to nothing until the new fiscal year (October), so I cannot authorize any expense to troubleshoot this. (Again, thank you for the offer; very appreciated)