Yep, we found our problem. It had to do with a registry entry that our server provider decided not to tell anyone about.
Here's their answer!
=====================
Sorry about the wait here. The change was made within our default kick for the Windows 2003 server. It was implemented to disable...