Yep...I didn't even think of that. 

Yep you where right.  Somebody entered the wrong information via our "Partner" quailty software.  

Setting the owner to SA solved the problem.  Thanks for all of the help with this.

Could the MSSQLSERVER service running as LocalSystem and the SQLSERVERAGENT running as domain\administrator be causing this problem?

Rheejay:

I wasn't to sure about he UNC or mapping, but I thought this worked before we move rebuilt the backup target...but I am not for sure on this.

What do you...

Here is what the SQL log is saying...

2004-04-12 12:02:25 - ! [298] SQLServer Error: 8198, Could not obtain information about Windows NT group/user 'DOMAIN\Administrator'. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

I am using the domain administrator account for the SQL agent startup as indicated on services...

I have also verified that the administrator account has the owner role given to it...

I change the authenication in the design of the package from windows to sql using the SA account.  Under Enterprise Manager the DTS package still lists Owner as domain\administrator...

Is there...

Permissions are fine...  I just don't understand how under one SQL server I can access the Link server and through a different server  I can't.

How does that help setup the ODBC-DSN information on the client machines?

Since we are currently using Access 2000 for the front end (to the Access Databases) we have decided to contintue to use Access as the front end to SQL. ...