Hello,
I work on ACER F900 with in the InTheHand.Net 2.4.0.0 Beta in c#. I try to send files with OBEX from F900 to my computer. It work fine with files which size is between 1 to 9822 bytes. After 9822 (so 9823 bytes), I got an "IOError on socket." :
Une requête d'envoi ou de réception de données n'a pas été autorisée, car le socket n'est pas connecté et (lors de l'envoi sur un socket datagramme en utilisant un appel sendto) aucune adresse n'a été fournie; ; WidcommRfcommStream_Closed
===> A request to send or receive data was not authorized, because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied; ; WidcommRfcommStream_Closed

à InTheHand.Net.Bluetooth.Widcomm.Wid

So we see that the remote device closed the connection. What we see here is actually partly caused by a bug in ObexWebRequest.  I had not personally looked at the OBEX classes until recently, and have now fixed many bugs and flaws in them. One (bug 23462) I fixed was that ObexWebRequest will always attempt to send a DISCONNECT packet, even if an error occurred earlier -- and the connection has likely been closed!  That's what's happening here some error occurred -- which might have useful information -- and the connection closed, but we cause an error by writing to the connection and thus lose the first error.  If you want, you can compile a version from the code repository which has this fixed, however....

Maybe something is wrong with the content of the file so the server returns an error/closes?  I don't understand what you're trying to send, but from my reading of the code you are sending a pile of zero bytes.  It seems a new byte array (Buffer) is created, it is not written to, so it full of zeros, it is then written to a new file, and the contents of that file are sent.  Eek,  Surely you need some content in the array...

(Some comments in general.

• Use "Camel case" for variable names, e.g buffer, newStart, newFileName, etc.  Then its simple to tell quickly whether an identifier is for a class/method/property or for a variable.  See http://msdn.microsoft.com/en-us/library/ms229043.aspx
• Don't use BinaryWriter -- well very rarely.  The Stream class and subclass are streams of bytes, so in your case fs.Write(buffer, 0, buffer.Length) is good.  BinaryWriter should only ever be used in partnership with another .NET program using BinaryReader -- it encodes some data types in unexpected ways that will confuse programs not using BinaryReader).

And on ObexWebRequest with local content.  There's no need to write to a file just for ObexWebRequest to read from that file. See the example in the user guide.  e.g. like:

    ...
    using (Stream content = request.GetRequestStream()) {
       content.Write(buffer, 0, buffer.length);
    }
    ObexWebResponse response = (ObexWebResponse)request.GetResponse();
    ...

 )

Thanks for answering and for your work !!!

 I use now the last version (InTheHand.Net.Personal 2.5.0.0 and Widcomm 2.5.0.0) and I now got this error {"Connection closed whilst reading an OBEX packet."} in InTheHand.Net.ObexWebRequest.GetResponse()

Stack :

à InTheHand.Net.ObexWebRequest.StreamReadBlockMust(Stream stream, Byte[ buffer, Int32 offset, Int32 size)
à InTheHand.Net.ObexWebRequest.CheckResponse(ObexStatusCode& status, Boolean isConnectResponse)
à InTheHand.Net.ObexWebRequest.DoPut()
à InTheHand.Net.ObexWebRequest.GetResponse()
à TestInTheHand.Form1.button1_Click(Object sender, EventArgs e)
à System.Windows.Forms.Control.OnClick(EventArgs e)
à System.Windows.Forms.Button.OnClick(EventArgs e)
à System.Windows.Forms.ButtonBase.WnProc(WM wm, Int32 wParam, Int32 lParam)
à System.Windows.Forms.Control._InternalWnProc(WM wm, Int32 wParam, Int32 lParam)
à Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain)
à System.Windows.Forms.Application.Run(Form fm)
à TestInTheHand.Program.Main()

The message is "Operation failed." and the Status is System.Net.WebExceptionStatus.Success

In Output, I got this trace :

I got exactly the same error with ObjectPushApplication sample ! 

Thanks !

So that's as I suspected.  The remote device is closing the connection whilst we're still expecting a response. :-(

What's the remote device type and what content are you sending to it.  Can you try sending to the "Bluetooth File Transfer Wizard" application (StartMenu->Accessories->Communications).  Does it accept the PUT successfully?

 Hello,

The remote device type is a PC with a BELKIN USB dongle. I always can send files with "Bluetooth File Transfer Wizard", of any size.

How yo know if my F900 accept the PUT ?

 Thanks

 Exactly

The Belkin dongle is running Widcomm (the about box says WIDCOMM Bluetooth Software 5.5.0.3200), the receive app is the built-in service, you're rigth.

I've sent 100,024 bytes from WM Widcomm ObexWebRequest to WinXP Widcomm built-in OBEX server. successfully.  So I wonder what's different in your case.  What file extension are you sending (I'm sending .txt (obexpush1.txt)) and what content (here just ASCII text)?

In my code, I create a "false" text file :

String CurrentDirectory = GetCurrentPath();
String Filename = CurrentDirectory + @"\testfile_{0}.txt";

I can send you my code, if you want.