alindzon said:

I did some digging, and noticed the sql browser service was disabled.  Turning on that service has resolved this issue.

I want to point out that you should never rely on the browsing list. In your case you could've tried with 127.0.0.1/./(local) since you knew it was installed locally probably default instance.