Hi! In October I worked with a client-server (using winsock.dll) 16 bit aplication emulated in wine (Not using ODBC), it worked fine. This aplication needs to connect to a server using port ctsql 5557/tcp, this service is in my /etc/services. And wine made all realy fine (Version 20011108). With the release 20011226 (I think)started the problem. Something changed with winsock 16-bit. I've upgraded my system , I use Debian Woody ( to wine version 20020122); now the aplication doesn?t work, it can?t connect to the server. I make a netstat, and the aplictation tryes to connect to 512 (exec) port and not to 5557 who I need. I change all services but the aplication always goes to 512 exec tcp port. What could be the problem?. I think wine read /etc/services but not send the correct port number (using always 512) to winsock.dll, or winsock.dll doesn?t works fine. P.D. Working with the same Server and Port (5557/tcp) with 32bits aplications work fine and fast. P.D. Thanks to Carol Farlow for her first anwser.
On Wed, 27 Feb 2002 13:13:16 +0100, in comp.emulators.ms-windows.wine David Barrena <david@molina.subs.map.es> wrote:> > I've upgraded my system , I use Debian Woody ( to wine version > 20020122); now the aplication doesn?t work, it can?t connect to the > server. I make a netstat, and the aplictation tryes to connect to 512 > (exec) port and not to 5557 who I need. I change all services but the > aplication always goes to 512 exec tcp port. What could be the problem?. > > I think wine read /etc/services but not send the correct port number > (using always 512) to winsock.dll, or winsock.dll doesn?t works fine.A trace with "--debugmsg +winsock" would be usefull Rein. -- Rein Klazes rklazes@xs4all.nl
The trace: (read my /etc/services ok ctsql/tcp (5557) but goes to wrong port 512) trace:winsock:WS_LibMain 0x40eb7000 0x1 (nil) trace:winsock:WSAStartup16 verReq=101 trace:winsock:WSAStartup16 succeeded trace:winsock:WINSOCK_gethostbyname16 "molina" trace:winsock:WINSOCK_getservbyname16 "ctsql", "tcp" trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketA created 0044 trace:winsock:WS_connect socket 0044, ptr 0x40de6a66, length 16 trace:winsock:WS_send socket 0044, ptr 0x40de6e68, length 170, flags 0 trace:winsock:WS_recv socket 0044, buf 40de7268, len 1024, flags 0 trace:winsock:WS_recv -> 18 bytes trace:winsock:WS_closesocket socket 00000044 trace:winsock:WS_LibMain 0x40eb7000 0x3 (nil) Wine exited with a successful status
The trace: (read my /etc/services ok ctsql/tcp (5557) but goes to wrong port 512) trace:winsock:WS_LibMain 0x40eb7000 0x1 (nil) trace:winsock:WSAStartup16 verReq=101 trace:winsock:WSAStartup16 succeeded trace:winsock:WINSOCK_gethostbyname16 "molina" trace:winsock:WINSOCK_getservbyname16 "ctsql", "tcp" trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketA created 0044 trace:winsock:WS_connect socket 0044, ptr 0x40de6a66, length 16 trace:winsock:WS_send socket 0044, ptr 0x40de6e68, length 170, flags 0 trace:winsock:WS_recv socket 0044, buf 40de7268, len 1024, flags 0 trace:winsock:WS_recv -> 18 bytes trace:winsock:WS_closesocket socket 00000044 trace:winsock:WS_LibMain 0x40eb7000 0x3 (nil) Wine exited with a successful status On Wed, 27 Feb 2002 13:13:16 +0100, in comp.emulators.ms-windows.wine David Barrena <david@molina.subs.map.es> wrote:> > I've upgraded my system , I use Debian Woody ( to wine version > 20020122); now the aplication doesn?t work, it can?t connect to the > server. I make a netstat, and the aplictation tryes to connect to 512 > (exec) port and not to 5557 who I need. I change all services but the > aplication always goes to 512 exec tcp port. What could be theproblem?.> > I think wine read /etc/services but not send the correct port number > (using always 512) to winsock.dll, or winsock.dll doesn?t works fine.A trace with "--debugmsg +winsock" would be usefull Rein. -- Rein Klazes rklazes@xs4all.nl