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

spitz@GANS2X.ana.med.uni-muenchen.de (Richard Spitz) writes: >One common cause for this problem is the "services" file on the >PC side. If the line "sqlexec 1525/tcp" is the last line of this >file, and not followed by a "return", Microsoft's TCP/IP (I don't >know if others have the same problem) cannot read the entry correctly, >leading to the above error. >If this is the case on your system, just enter a "return" after the >last line in the services file, so the EOF marker sits in a line by >itself. That should solve your problem. No, the sqlexec was in the middle of the services file. I later dicovered, through the use of ilogin, that I needed both a userid *and* a password to the user where the db subdirectory lived. I also needed to plug an entry into DbPath w/i setnet to finally get connected to the database we wanted. The use of logins w/ no password had to be discarded; The damn thing wouldn't even *try* to connect w/o a password entry. *SIGH* Once I did that we had a reasonable connection. I also turned on logging for sqlexecd to monitor activity and this helped a lot; I could *finally* see when the MS-DOG box actually made a connection. Craig's recommendation to use ilogin helped *a lot*. -- John R. Campbell, Speaker to Machines soup%penrij@kd3bj.ampr.org 1438 SchoolHouse Road, Perkasie, PA 18944 (USA) "Son, you'll *never* learn about impotence the hard way!" - me LugNuts is *NOT* a brand name for a jock strap