Bluetooth and Winsock2 connect problem   

I've written an MFC app that uses the Bluetooth functionality of Winsock2. 
My app runs fine on the 50 or so XP SP2 machines it's been installed on but 
I've run across two machines now where it fails with a WSAEADDRNOTAVAIL 
error when calling connect(). As a test, I wrote a console app that uses 
Bluetooth sockets and it works fine on the bad machines, but any GUI app, 
whether built with MFC or the SDK fail on them. I also compiled the 
Bluetooth sample app that came with the platform SDK and it behaves as my 
app does - if I build it as a console app, it works and if I wrap a window 
around it, it fails with the same error. Bluetooth appears to be functioning 
fine on the bad machines as I can pair my PDA to them and communicate with 
it, but GUI apps that use Winsock fail. Wiping one of the machines and 
reinstalling the OS fixed the problem but that's not a good option when 
supporting a customer. Any ideas what could cause a conflict like this? And 
is there a better group to post this question too?

Thanks,
Dave

date: Wed, 4 Jan 2006 18:54:18 -0500   author:   Dave Abdallah

Re: Bluetooth and Winsock2 connect problem   

Hi,
I had that problem once, but I did not tested the console situation.
I remember it was due to the wrong stack installed: winsock will only 
work with MS bluetooth stack, I think.
regards,

	e.

Dave Abdallah wrote:
> I've written an MFC app that uses the Bluetooth functionality of Winsock2. 
> My app runs fine on the 50 or so XP SP2 machines it's been installed on but 
> I've run across two machines now where it fails with a WSAEADDRNOTAVAIL 
> error when calling connect(). As a test, I wrote a console app that uses 
> Bluetooth sockets and it works fine on the bad machines, but any GUI app, 
> whether built with MFC or the SDK fail on them. I also compiled the 
> Bluetooth sample app that came with the platform SDK and it behaves as my 
> app does - if I build it as a console app, it works and if I wrap a window 
> around it, it fails with the same error. Bluetooth appears to be functioning 
> fine on the bad machines as I can pair my PDA to them and communicate with 
> it, but GUI apps that use Winsock fail. Wiping one of the machines and 
> reinstalling the OS fixed the problem but that's not a good option when 
> supporting a customer. Any ideas what could cause a conflict like this? And 
> is there a better group to post this question too?
> 
> Thanks,
> Dave 
> 
>

date: Tue, 10 Jan 2006 15:07:50 +0100   author:   ernie