Enterprise Replication on NT 4.0

I am trying to set up Enterprise Replication on two Win NT 4.0 servers using IDS 2000. I am having difficulty getting the target server to synchronize with the primary. Specifically, I can't seem to get the target "host or user" known to the primary (-956). Sqlhosts registry structure is set up according to instructions and sample from Madison Pruet. Hosts.equiv file is created and resides in \\winnt\\system32\\drivers\\etc, along with correct hosts and services files. DbPing utility allows logon to both servers in both directions without specifying user name or password, so default user <informix> appears to be set up correctly. Can ER be set up to cross NT Domains? I have had it working correctly within the same domain, but can't seem to get it working between two domains. This is a test setup, actual production setup will involve servers on opposite sides of the US so it seems that working across domains will be critical. Any help will be greatly appreciated. -- R. Mitchell

I'm not in the position to be able to help currently. Do you have a case open with tech support? When you get one open, you may need to ask for NT help instead of ER help. I'm going to bet that this is a permissions issue and that you will need to set up your etc & host.equiv files a bit differently. News wrote: > I am trying to set up Enterprise Replication on two Win NT 4.0 servers using > IDS 2000. I am having difficulty getting the target server to synchronize > with the primary. Specifically, I can't seem to get the target "host or > user" known to the primary (-956). Sqlhosts registry structure is set up > according to instructions and sample from Madison Pruet. Hosts.equiv file is > created and resides in \\winnt\\system32\\drivers\\etc, along with correct hosts > and services files. DbPing utility allows logon to both servers in both > directions without specifying user name or password, so default user > <informix> appears to be set up correctly. > > Can ER be set up to cross NT Domains? I have had it working correctly within > the same domain, but can't seem to get it working between two domains. This > is a test setup, actual production setup will involve servers on opposite > sides of the US so it seems that working across domains will be critical. > Any help will be greatly appreciated. > > -- > R. Mitchell -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================