If you're bluetooth setup on your laptop is putting up its own winsock then you may have competing stacks. That could definitely cause you to have the problem you're having. Since I"m not familiar with the hardware or firmware that your using I can't offer anything except to say that the likely culprit is the competing winsock, the win32 and the one from your bluetooth (if I'm reading your post right). This is just a guess but I think you're getting closer to the answer.

R