>Just waned 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?
>
>
>>>I have been pouring over the MSDN on this problem and am comming up without any answers. I have a COM object on a NT4.0 Workstation in Domain X. I can call oMyObj=CreateObjectx(lcComID,lcIP_Address) from my workstation. Then I can call a Function in that remote object. and it works. I have another programmer on ISDN that is an Admin on that COM NT4.0 Workstation. He gets "RPC server unavailable" He can Ping the Machine with the COM object by name.
>>
>>You may not have the necessary trusts established between the domains, or mnay have some ports blocked by a gateway/firewall between the two. Admin prvileges on one domain do not necessarily grant any privileges on another domain; you need to establish the trust relationships.
>>
>>>I have had this same problem when I am logged in at home on a 56K line. We have never had a problem going across Domains to access COM before. Is there something about a slower connection that causes problems and if so does anybody know how to fix it? Thanks in advance.
>>
>>Again, the port may be restricted if you RAS in by modem. You need to check the RAS configuration in the Remote Access Admin tool (Start/Program/Admin Tools (Common) to get there.) You may need to adjust the RPC service. If you're using Win9x at home, you must set up an entry in LMHOSTS or a WINS service to translate an IP address to a NetBIOS name - Win9x requires a NetBIOS name for the server rather than an IP address for the server. If you aren't familiar with the basic issues, Rick Strahl's book "Internet Application Development with Visual FoxPro 6.0" is a good start point.
>>
>>I'd get the domain admin(s) in to make sure that the necessary network services are in place.
