Actually we do not have a trust. We are currrently doing it the hard way. As long as a users Username and PW is in the local NT Workstations Users list they can access the COM Object on it. We have gone across domains like this for about a year and have not had any problem. As a matter of fact we probably hit it every few seconds. Anyhow everything is set up fine (NT Stuff ... I am the Domain Admin) the only difference is the ISDN line access. Please note he is accessing via ISDN to Corperate HQ to us through a T1. He is trying to activate it through IP_address instead of PC name and still no luck. More info... no Win95 here all NT 4.0 Workstation.



>>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.