Zsoldier's Tech Blog

Summary WRT600N Firmware 1.01.36 Build 3 provides DHCP clients w/ DNS entries in a strange order. ISP's DNS -> Router -> Your static DNS entries By and large, I really like my WRT600N router. The thing is so dang versatile, but be warned it is not without it's issues. I'm currently using the latest firmware build 1.01.36 Build 3. There seems to be issues w/ the router's DHCP server. It issues DNS addresses in a weird order. It provides systems w/ the ISP's DNS servers as your primary and secondary, then the router itself as a tertiary, followed by any static DNS entries you've entered yourself. For most people this isn't an issue, but if are doing any kind of home networking, this leads to issues resolving local system names. Since the first thing your clients try to resolve a name against would be your ISP's DNS servers. They wouldn't have the first clue where to find "mylocalsystem". Windows is pretty good about this though ...

So I'm one to keep my filing system clean. Like in the Window's start menu, when it gets incredibly huge with each application having it's own entry, I begin to consolidate them into folders of like applications. On the mac, I thought it would be just as easy. I would move things like MS Office, and iLife 08 into their own folders. For the most part it is, but low and behold, unless the iLife applications are in the root of /Applications, the Mac Auto Software Updater doesn't see them so assumes they are not installed and does not apply patches. You can download them manually from Apple's website if you know what to look for, but that is such a pain the arse. Oh and you have to install one update after another. For instance, iPhoto has updates up to 7.5.3. I was at 7.5. Can't install 7.5.3 update, I have to install 7.5.1, then 7.5.2, then finally 7.5.3. WTF!? Are we still in Windows 3.11 age? Most advanced OS my ass. If there is a better way to keep m...

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