Thanks for your replies. Reading up on the wiki about the BOM character this does seem to fit with the example i have shown. I should read it out in HEX to confirm it later. It might just be the cause of the problem. I have no idea why it would put the character there when i haven’t asked for it. But it might just be part of the serializer of the library.
If this is the case, my solution would be to flush the stream before i start sending my first message. I imagine it would do the same as whatever Freddy did to get it to work.
Either way, if the server default is UTF-8 (or it expects UTF-8 at least) it might still be a good idea to write it on the help page in any rate. Maybe this BOM character could be mentioned as well. Could save a bunch of people a day worth of headaches over a single invisible set of bytes 
Thanks for the help so far, i will post the results of my flush before sending data to confirm if it worked.