Re: winsock 16 BIT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 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


_______________________________________________
wine-users mailing list
wine-users@winehq.com
http://www.winehq.com/mailman/listinfo/wine-users

[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux