Apache v2.0 vs. v2.2+ with SSL

[rtwingfield]

I have a working installation of Apache v2.0 with SSL. I am attempting to configure v2.2.11 (also v2.2.4 with the same results). I have created fresh certificates, keys, etc. and the v2.2.11 server prompts for the pass phrase as with v2.0 and starts as expected. Unsecure pages are served nicely via port 80; however, the SSL port 443 complains that the whatever/something.html cannot be found, even though the error message (404) is served via port 443. I have removed all REQUIRE SSL etc. options from the associated .htaccess file, and if I remove the s from the https construct in the URL address as submitted by the browser, then the pages will be served . . .via port 80.

I've basically taken the configuration from the v2.0 ssl.conf file and incorporated into the ./extra/httpd-ssl.conf of v2.2.11. I've discovered a few nuances such as the <VirtualHost _default_:443> construct in v2.0 had to be changed to <VirtualHost 192.168.1.73:443> which is the IP address within the LAN, i.e., inside a NetGear FVX538 VPN Router.

QUESTION: Has anyone dealt with this or a similar problem? . . .got to be something simple, perhaps a default document path in the httpd-ssl.conf file. BTW, I haven't ruled out a firewall problem withing the NetGear router.