Appreciate the comments, but they are not taking into account the
scenario that affected my problem, as mine was different. In my case,
it had nothing to do with 'admin' group itself, but rather how I had
configured "Domain groups" and had omitted to explicitly add my Active
Directory userID.
In
I encountered this same message when I tried to add (1) an AT&T USB WLAN
adapter, and then again (2) when I tried to add a PPTP-VPN profile.
Here's what I figured out though:
1. I use centrifydc to connect this system to Active Directory.
2. I am working from my office at work, and my domain cont
I ran into this same problem. I checked over my sesman.ini file, and
found that the problem disappeared after a changed the ip-binding back
to 127.0.0.1. Apparently, it's a misconception on the part of some
(including myself) that the ip-binding needs to match that of the
static-eth0 address.
An
