Bluetooth Dongle and Windows XP built-in management

Summary:
  • Make sure the Bluetooth Support Service is running as "Local System" or an account w/ administrative privileges.
Ran into an interesting issue today. Just recently purchased this little AZIO bluetooth dongle for my work laptop. It came w/ software/drivers so I installed them. Don't know what it was about it, but the software ran like crap (high cpu, buggy connections to my phones). So I decided to drop back to using the straight Microsoft built-in management.
I had no issues connecting my phones, but was getting an access denied message anytime I tried enabling a service for my phone like DUN (Dial-Up Networking). I have admin permissions so a security seemed odd. Not sure if this is by default, but it ended up being that my "Bluetooth Support Service" was running as a "NT Authority\Local Service" account. As soon as I changed it to "Local System", everything was working

Comments

Anonymous said…
We have just added your latest post "Zsoldier's Tech Blog: Bluetooth Dongle and Windows XP built-in management" to our Directory of Bluetooth - http://www.blutooth.info . You can check the inclusion of the post here:http://blutooth.info/story.php?title=zsoldiers-tech-blog-bluetooth-dongle-and-windows-xp-built-in-management . We are delighted to invite you to submit all your future posts to the Directory and get a huge base of visitors to your website.


Warm Regards

Blutooth.info Team

http://www.blutooth.info

Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

vCenter: Cluster Skip Quickstart Workflow via API