In addition to the stuff mentioned by Wayne you need to remember that NT credentials are only good for at most one 'hop'. If an object is created on your behalf on another machine then that object can access resources on that machine which would be accessible to you but nothing else - not even your own stuff on your own machine from where you initiated the request. The effect is easy to observe if you run the remote command shell that comes with the NT resource kits and try to access network resources.

If the object needs to access resources on the network then it needs to be run as a 'principal', i.e. under some sort of account on the machine where it resides and in some 'real' (non-network) logon session. Then the network access of that object will be governed by whatever rights the account has.