Hrm. Seems like the previous solution may or may not have worked. I'm still getting reports of connection timeouts, but the majority users aren't saving the details of the errors for me to view. However, the one report that was saved is displaying a 08001 error; I don't know if this is what the others are experiencing or not, but it seems we've shifted to a new error type. Would someone have some suggestions on how to approach this problem?

EDIT: After much digging around, it seems as though the problem's cause was in the ODBC connection we were using to connect to the SQL Server. The server's name was being used as the connection location, which worked fine and let us connect to the server normally most of the time; however, on occasion, the server's name would be associated with our ISP's IP address rather than the server's IP address, for whatever bizarre reason. Changing the connection location to the server's static IP address seems to have elimiated the problem entirely. The support in this thread was much appreciated, though; without it, I probably would've continued to assume all was well with the DSN :hehe: