>>>Just wanted to share the wealth: If this User Access a DCOM Object that does NOT use Recordsets it works Fine. If RecordSets are used he gets "RPC Server is Not Found" To Fix this I had him go to the Control/panel/Network/Protocols/TCp IP/Properties/DNS Tab/ Add out Corp Domain name and add the Ip address to the DNS Server. Life was good at this point.
>>>
>>
>>Curiouser and curiouser. You mean to say that the database server's ID was not being resolved through DNS? What context was the RPC running in?
>
>Since he is a remote user he uses a host file. Everyone else in all domains resolves through Domain Wins Servers or DNS depending on the network setup
>

Fine, but why not log into the domain and use the domain services for resolution? I assume he RASes into the machine, logs in as a local user and then runs the RPC across the RAS connection. If he RASes in and logs into the domain, he should have access to domain resources within the limits of the remote access permissions and the domain account, an ideal situation if the RPC server is moved off the box he makes his connection to, or if he comes in via some other route. Is there a reason to isolate the user to the local system? You can still limit access to other resources by account or group membership. By being a domain member, you would be able to use standard control mechanisms.