SQL Server 2000 on Win 2003 System

A Windows 2000 Workstation authenticates to the Win 2003 (domain
controller). The user starts Enterprise Manager with two registrations. One
to the local SQL Server 2000 Pro and the other to the Win 2003 SQL Server
2000 Standard. The Windows 2003 security group has public access on the
domain SQL Server and sysadmin server role on the local SQL Server.

The user does an import from pubs on the domain server to pubs_copy on the
local server. If copy files/views option is used, the copy works fine
(except the views are converted to tables - anyway to copy them as view
scripts rather than them being converted to tables?).

Since he wants the views as scripts rather than tables, he uses copy
objects. He deselects copy database users and roles. Upon executing the job
the local copy reports an error that is apparently happening on the domain
SQL Server (Home is the domain server).

Invalid OLEVERB structure
[DQL-DMO] CreateFile error on 'Win2003-Home-MMV.pubs.LOG'

On the other hand, the user when the user does not authenticate to the
domain server, but logs on to the workstation locally, things seem to work.
Of course, he has to use SQL authentication on the domain SQL server to get
access (remote connection). Since the workstation is still on the subnet,
although not logged in, the domain instance is visible without having to
use Client Network Utility.

Can anyone please point me to a fix?

A follow up to my question.

If the user authenticates to a local administrator account, the copy
objects task completes successfully. Hence, the issue must be permissions.
I have looked at the C:\Program Files\Microsoft SQL Server\80\Tools
folder's permissions on the local machine, but am not able to see anything
out of the ordinary. I believe this is the folder to which the system is
trying to write the file.

Does the install of the local SQL Server 2000 instance assume that the user