Hi All, We have a Client/Server implementation using Windows RPC.We have a remote procedure at the server end which offers certain services.Any client requiring those services simply need to make a call to the remote procedure as if it is a local procedure & the call transfer to server is handled by RPC,RPC library being used is rpcrt4.lib.It's working fine in all cases except when the server is hosted on a particular INTEL machine which has Win XP.All other machines have Win 2000. In this particular case sometimes the clients are strangled out...During certain test runs it had been working fine for more then 24 hours.But when problem comes after some 10-15 mins the clients are stopped.Before getting stopped the clients show behavior of unstable connection.We have tried RpcMgmtSetComTimeout,but in vain. Kindly guide us in this regard. Thanks in advance Chandra Prakash

Are there any error messages in the event viewer?? (start\run\eventvwr)

No there arn't any error messages in the eventvwr. The most probable point of client stopping however seems to be either the server not accepting the client's request/the server not returning.

What type of OS are the other machines? Are they Windows 2000 professional or are these windows 2000 servers? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rpc/rpc/rpcmgmtsetcomtimeout.asp Also keep in mind that windows xp allows only for 10 simultaneous file-sharing connections

hi Ryon, All other machines have windows 2000 server.File sharing information might not be useful since clients hang even when we test Client/Server with 6 clients. I have used the rpcmgmtsetcomtimeout after reading the usage from the link which u have also provided. Anyway do u think the rpcrt library provided by windows may be different in 2000 server & XP which might be the source of problem.Though we tried to handle all exceptions but may be WinXp reports the error in some different way which we might not have handled.Another thing is that problems in Os's etc are one aspect but the Client/Server should recover properly from all exceptions.One request might fail,but then client should safely move on to next request. Kindly try to think & guide with this viewpoint also.

Did you read the requirements? Client Requires Windows XP, Windows 2000 Professional, Windows NT Workstation, Windows Me, Windows 98, or Windows 95. Server Requires Windows Server 2003, Windows 2000 Server, or Windows NT Server.

No not at all.If this requirement scenario holds then,I think we have nothing more to look for.If microsoft doesn't allows win Xp to host an RPC server then there is no point in fighting for the same. Kindly suggest some links which underlines these requirements.As far as our research goes we havn't seen any OS being secluded from the list of RPC Server,although 2000 & 2003 server are ofcourse a much better choice. Thanx Ryon for keeping the hopes alive by ur prompt replies.