The subject behavior occurs because Internet Explorer Enhanced Security Configuration is enable by default on Windows Server 2003.

To resolve this issue, see How do I disable the Internet Explorer Enhanced Security Configuration component in Windows Server 2003?