dbserver name "group" doesn't connect from Windows

From Unix /Linux: dbaccess database@database_group .... That works. From Windows: (Get -25555, saying it isn't in sqlhosts file... But the group is in the registry sqlhosts file.) ilogin and testing odbc connection to database server group ... Does not work. Unix sqlhost file: g_database_grp group - - i=7 inst1 onsoctcp host1 sqlexec1 g=g_database_grp inst2 onsoctcp host2 sqlexec2 g=g_database_grp Windows setnet32 Informix Server = g_database_grp Host Name = - Protocol = group Service = - Options = i=7 Note: I've tried 3.7, 3.5 TC8, 3.5 TC5 .... nothing gets around the -25555. The Database Servers are using Informix 11.50.FC6. The Connection Manager Server is using Informix_11.70.FC1. Also, ilogin and odbc connection on Windows DOES connects to inst1 and inst2 okay.... just not the group name. The original problem: I tried to use a "group" name for Connection Manager. Set up "dual" connection manager instances .... to avoid a single failure point. (I was able to get Connection Manager working using one Connection Manager, without a "group".) The Connection Manager "group" name DOES work with dbaccess on Unix/Linux, but does not connect from Windows ilogin or ODBC connection. That's when I decided to take the Connection Manager component out and see if a dbserver group works. And that's where I am stuck. The dbserver group name does not connect from Windows. Any suggestions?

Addtl Note: The individual instances inst1 and inst2 are also set in Windows via setnet32. Is anyone using a database server "group" now? That works? (...Accessing the database by a "group" name via ODBC.)

yes, it works. I've verified with regedt32.exe run regedt32.exe, and create key with group name under informix My Computer\\\\HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Informix\\\\SQLHOSTS\\\\g_ids HOST "-" OPTIONS "i=10" PROTOCOL "group" SERVICE "-" under the group g_ids, define IDS servers My Computer\\\\HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Informix\\\\SQLHOSTS\\\\g_ids\\\\ol_ids_1150_1 HOST "myhost" OPTIONS "g=g_ids" PROTOCOL "onsoctcp" SERVICE "9100" then run dbaccess connect to the group name "g_ids" Thanks

Thanks but, the dbaccess is the part that does work. Our application needs ODBC to connect to the database. Did you get "ilogin" or ODBC to work with the dbserver "group name"?

yes, both ilogin and the odbc test work fine. the tricky part is we need to define the server instances inside the group registry key.