IECC - Problems viewing Unix DB

Hi all, Has any one managed to successfully set up IECC on an NT box to view their Informix Databases on Unix boxes? What we have done this far: 1. Installed IECC on the NT box (Informix = 7.30.TC7) 2. Installed IECC on our Sun Sparc box (Informix = IDS 7.31.UC2A) 3. Started the server agent using startsa on the Sun box 4. Sqlhosts has been set up on the Unix box 5. Hosts.equiv has been set up on the Unix box 6. Setnet32 has been set up on the NT box (such that I can see the databases under Informix Neighborhood in the sqleditor 7. I can see informix databases on other NT Servers, but can not see (or discover) any of our Unix database servers or databases. Any suggestions on what we can do / try ? TIA - Regards, Stephen

One problem we had was that we did not have admin priveleges on the NT clients but the install did not complain it just failed to update the registry and did not install all of the components from the disk so that adding admin and rerunning the install on the install directory was not enough. We had to uninstall and start from scratch. Art S. Kagel Stephen Manga wrote: > > Hi all, > > Has any one managed to successfully set up IECC on an NT box to view their > Informix Databases on Unix boxes? > > What we have done this far: > > 1. Installed IECC on the NT box (Informix = 7.30.TC7) > 2. Installed IECC on our Sun Sparc box (Informix = IDS 7.31.UC2A) > 3. Started the server agent using startsa on the Sun box > 4. Sqlhosts has been set up on the Unix box > 5. Hosts.equiv has been set up on the Unix box > 6. Setnet32 has been set up on the NT box (such that I can see the > databases under Informix Neighborhood in the sqleditor > 7. > > I can see informix databases on other NT Servers, but can not see (or > discover) any of our Unix database servers or databases. > > Any suggestions on what we can do / try ? > > TIA - Regards, > > Stephen

IECC has an anomaly (nice word) that will not allow it to see servers on multiple sub-nets. See following excerpts from the IECC Installation guide: Administering Servers on Remote Networks You can use IECC 3.0 to administer database servers on remote networks. To administer a single server on a remote LAN, set the VisiGenic OSAGENT_ADDR environment variable to the IP address of the server. To administer several servers on a remote LAN, set the VisiGenic OSAGENT_ADDR environment variable to the IP address of one of the servers. (The server that you choose must be running the Server Agent.) This approach lets you view the servers on the remote LAN in IECC; however, you cannot at the same time view the servers on the local LAN. For further details about configuring the VisiGenic Smart Agent, see Appendix A. Excerpt from appendix A. To allow the Smart Agent on one network to contact a Smart Agent on another local network, you must make the IP address of the remote Smart Agent available in a file named agentaddr. The following example shows what the file agentaddr must contain to allow the Smart Agent on Local Network #1 to connect to the Smart Agent on Local Network #2: 101.10.2.6 The path to the agentaddr file is specified by setting the OSAGENT_ADDR_FILE environment variable. After creating the above file, you could place multiple entries in it, but IECC will only access the first subnet listed, in this case 101.10.2 - if you were to also list a server at 101.10.3.99, for example, IECC would never see it. However, if you were to put 101.10.3.99 first, then IECC would see 101.10.3.99 and not 101.10.2.6 Stephen Manga wrote: > Hi all, > > Has any one managed to successfully set up IECC on an NT box to view their > Informix Databases on Unix boxes? > > What we have done this far: > > 1. Installed IECC on the NT box (Informix = 7.30.TC7) > 2. Installed IECC on our Sun Sparc box (Informix = IDS 7.31.UC2A) > 3. Started the server agent using startsa on the Sun box > 4. Sqlhosts has been set up on the Unix box > 5. Hosts.equiv has been set up on the Unix box > 6. Setnet32 has been set up on the NT box (such that I can see the > databases under Informix Neighborhood in the sqleditor > 7. > > I can see informix databases on other NT Servers, but can not see (or > discover) any of our Unix database servers or databases. > > Any suggestions on what we can do / try ? > > TIA - Regards, > > Stephen

Also sprach Stephen Manga <Stephen.Manga@dbgroup.co.nz> : : :Hi all, : :Has any one managed to successfully set up IECC on an NT box to view their :Informix Databases on Unix boxes? : :What we have done this far: : :1. Installed IECC on the NT box (Informix = 7.30.TC7) :2. Installed IECC on our Sun Sparc box (Informix = IDS 7.31.UC2A) :3. Started the server agent using startsa on the Sun box :4. Sqlhosts has been set up on the Unix box :5. Hosts.equiv has been set up on the Unix box :6. Setnet32 has been set up on the NT box (such that I can see the :databases under Informix Neighborhood in the sqleditor :7. : :I can see informix databases on other NT Servers, but can not see (or :discover) any of our Unix database servers or databases. : :Any suggestions on what we can do / try ? Couple of thoughts based on a lot of experience setting up IECC for classes I teach: 1. Double-check the port the OSAGENT is using on the Unix side (osagent is one of the daemons startsa kicks off) and on the NT side. If you run set in a dos window and look for OSAGENT_PORT, you'll see what NT expects. You can set the environment variable OSAGENT_PORT on your Unix box to this same value before kicking off startsa. I haven't had the time to verify that this is absolutely necessary or not, so it may not really matter. 2. Whenever I do a clean install of IECC on a windows box and start IECC up for the first time, no matter what I've done in setnet32, it fails to find the server running on the Unix box, even when I've confirmed that the two daemons startsa kicks off (admagent and osagent) are running. I have found the following process always corrects this problem: Start IECC and then dobleclick the Control Panel (in the right pane) then Network. That brings up an applet with 4 tabs. Choose the server tab. It may list your server already (from setnet32 settings). Remove that entry if present. Now choose Add. When prompted for the machine name (it will default to //NTHOSTNAME) type in the name of your Unix host, then choose next. It will complain that no server can be found on that box. Choose to continue anyway and click the check box indicating that a server will be found on this box later. It will then ask for the service name and protocol. Enter those in as appropriate (note: you can type the port number in for the service name if you want to avoid editing the services file). Click finish and the server should appear in the list on the Server tab. It may be exactly the same as before - that's fine. Click OK and it will warn you that you are about to overwrite the SQLHOSTS info in the registry; click OK to this as well, and you will leave the applet. If you either wait a minute or exit IECC and restart it, the server on the Unix box should now show up and be accessible. I have no idea why this works. 3. Don't know if this is still true with the latest revs of IECC, but it used to be that it would only work against a Unix-based server if the DBSERVERNAME was the network protocol; using DBSERVERALIASES to list the tcp connection would not work. Dave