[Bug 21106] New: RPC clients that connect via ncacn_ip_tcp to a Windows RPC server are broken

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=21106

           Summary: RPC clients that connect via ncacn_ip_tcp to a Windows
                    RPC server are broken
           Product: Wine
           Version: 1.1.35
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: rpc
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: winesku at googlemail.com
                CC: robertshearman at gmail.com


Created an attachment (id=25343)
 --> (http://bugs.winehq.org/attachment.cgi?id=25343)
Call Stack in 1.1.35 when things go awry

With version 1.1.35, all my RPC clients that work over ncacn_ip_tcp to connect
to a windows server don't work anymore. Things still worked without any
problems in version 1.1.34. The problem is, that now with version 1.1.35, every
RPC fails because NdrClientCall2 returns ERROR_NOT_ENOUGH_SERVER_MEMORY (1130,
"Not enough server storage is available to process this command"). I have
debugged this and things start to fail when NdrClientCall2 is in the
PROXY_GETBUFFER phase. There it calls into the following call stack 

rpcrt4_conn_tcp_read at rpc_transport.c 1452
rpcrt4_conn_read at rpc_binding.h 77
RPCRT4_default_receive_fragment at rpc_message.c 1297
RPCRT4_receive_fragment  at rpc_message.c 1363
RPCRT4_ReceiveWithAuth at rpc_message.c 1396
RPCRT4_Receive  at rpc_message.c 1553
I_RpcReceive  at rpc_message.c 1851
I_RpcSendReceive  at rpc_message.c 1911
NdrSendReceive  at ndr_clientserver.c 214
NdrClientCall2 at ndr_stubless.c 747

Please also see my attachments to this issue with screenshots of the debugger
when things go wrong in 1.1.35 and the same situation in 1.1.34 where things
worked. I will also attach a couple binaries to easily repro the problem.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.