It wouldn't suprise me. I've had similar findings with other aspects of
DTS. For example, we had differing versions of MDAC on the server and
my development PC. It was enough of a difference to stop our package
working (connection string differences). From what I understand, DTS
uses the local user's settings if you run it manually as it knows you
have run the package, but when you run it as a scheduled job, the
server is the one that calls the job (not a user) and it therefore uses
the settings, files and permissions of the server as it can't determine
which user's settings it 'should' be using, this makes sense for it to
run as the server. It is consistent though. UNC paths should work fine
if you can use these or re-look at the specifics of what you want to
achieve. There may be some helpful stuff on
www.sqldts.com
HTH
Ryan