Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Windos
win32.3rdparty
win32.directx.audio
win32.directx.ddk
win32.directx.graphics
win32.directx.input
win32.directx.managed
win32.directx.misc
win32.directx.networking
win32.directx.sdk
win32.directx.video
win32.dirx.grap.shaders
win32.gdi
win32.international
win32.kernel
win32.messaging
win32.mmedia
win32.networks
win32.ole
win32.rtc
win32.tapi
win32.tapi.beta
win32.tools
win32.ui
win32.wince
win32.wmi
windows.mediacenter
winfx.aero
winfx.announcements
winfx.avalon
winfx.collaboration
winfx.fundamentals
winfx.general
winfx.indigo
winfx.sdk
winfx.winfs
  
 
date: Tue, 14 Feb 2006 04:15:30 -0800,    group: microsoft.public.win32.programmer.directx.networking        back       


Socket Connection times out   
We are trying to build client and server components using WIN32 socket APIs. 
Code does work when the client code is standalone console application, but 
when converted to NT Service to run in background asynchronously it fails to 
connect to the server.

We receive error code 121 (which is Semaphore timeout is expired)

Case 1: Server code is residing remotely. Client code is local - It fails 
with above error
Case 2: Server and client code are local it works well
Case 3: Server and client code on remote machines, it work well.

We have issues with Case 1 and unable to figure this out. Please help. 

Thanks
Bala
date: Tue, 14 Feb 2006 04:15:30 -0800   author:   Bala Prasad Peddigari

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us