I need to run a sproc on SS2k server B as part of a scheduled job that runs
on SS2k
server B. The sproc and job were created by and owned by our designated
Service account, which is in the Admins group on both servers. Both W2k3
servers are running SS2k sp3a. Server B is not a linked server, nor do I
wish it become one.

I created a test job with only the sproc call and the job still fails with
this error:
"Executed as user: [domain\ServiceAccount]. Remote access not allowed for
Windows NT user activated by SETUSER. [SQLSTATE 42000] (Error 7410). The
step failed."

Running the same step in QA on Server A also causes an error:
"Server: Msg 18483, Level 14, State 1, Line 1
Could not connect to server 'SERVER1' because 'ServiceAccount' is not
defined as a remote login at the server."

I've looked at KB 811031 and other sites that describe the same problem, but
don't describe a solution (that applies here).

This would appear to be a security issue.
I've confirmed that ServiceAccount has the "Allow logon to terminal
server"box checked on the account properties dialog.

What am I missing?

Thanks.
dj