RE: ViewPoint Pro -> I*NET won't connect

John, It's too early to say you've overlooked something. This stuff gets pretty obscure. Try using the ilogin utility found in the informix/bin directory. It will also give you the -932 error but might give you a pointer to the problem. Also, make sure that /windows/services is the real services file. It's easy to end up with more than one of these and not know which one is live. (Sure, you can telnet into the sqlexec port but you probably still skipped the services name lookup.) Two more suggestions: 1. Make sure the last line in you services file has a carriage return after it. That is, the last line in the services file should be blank. 2. Try moving your sqlexec service to the top of the services file. --Craig (craig@chemistry.utah.edu) } } I thought I had everything configured correctly on both the DOS and } SCO side; } } /etc/services } sqlexec 1525/tcp } } /windows/services } sqlexec 1525/tcp } } We're running Windoze 3.11 (WfW) w/ a current MS TCP/IP for it and } WinSock. Telnet works just fine, as does FTP. } } I ran a sqlexecd w/ INFORMIXDIR & SQLEXEC set (and $INFORMIXDIR/bin } in the path) and I can telnet into the sqlexec port (though it'll } disconnect if I hit the enter key). } } Trouble is, when I try to start up either VPRUN or VPPRO they give } up with: } } ______________________________________________________ } |-| Informix - New Era ViewPoint Runtime |v|^| } |------------------------------------------------------| } | [Informix][VPRun] SQL Error (-932): Error on network | } | connection, system call failed | } |______________________________________________________| } } So, I have no idea where to go from here. I've even plugged in the } raw IP address for the SCO box w/ I*NET server into setnet, though } I'm still using the symbolic name for the port. } } What have I overlooked? }