Hi,
They're blowing smoke at you (resources? come on now, this is XP, not
98). The problem lies in how they've written their supporting software.
In most cases, I do not install any supporting software, just the nic
drivers (if not natively supported) and let Wireless Zero Config do it's
thing. The problem with the supporting software supplied by NG and others
is that it installs in admin-only and you have to change permissions on
the program folder to allow non-admin users the right to read and execute
the files within it. You shouldn't need to use it, WZC should be able to
handle it.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
Associate Expert - WindowsXP Expert Zone
Windows help -
www.rickrogers.org
Same situation here Rick! Doesn't seem to matter if it is a notebook or
desktop PC -- no internet access is available from anything but
Administrative accounts! Limited or Power Users accounts won't cut the
mustard. The NG management utility won't even load (in the SysTray) in
non-Admin profiles, even if you click on its exe icon from the Programs
menu or its own NG directory. The NG utility attempts to fire up, but
ultimately refuses (with no error message). Switch back to any ADMIN
account, and all is well again (NG icon appears as it should in
SysTray, and wireless connection works).
BTW I have a new Netgear WG311v2 (driver + utility) coupled with a NG
WGR614 [v6] router producing this idiotic behavior (on desktop PC
running XP Pro SP2). Would Windows Wireless Zero Configuration have
anything to do with this?
Netgear Support seems to point the finger at Microsoft or possibly
"user configuration" (lack of proper permissions or rights) as the most
likely culprits, yet I have never read anything that claims there is
such a limitation in XP. Hard to believe an Administrator would be
required to assign internet access rights to every limited user
account! If this should be the case, where the heck in gpedit would I
do it??
When I talked to the NG tech support earlier this week, they insisted
it must be some sort of Microsoft bug or resource limitation (once I
got them to put down their silly, pre-arranged "troubleshooting"
scripts). They refuse to acknowledge any of their NIC drivers or
utilities produce these kinds of limitations, or require ADMIN rights
to function correctly. Yet ironically, I've seen them address this
exact issue on SOME of their wireless NIC card driver updates (but not
all models!)
So I ask, is this an XP or Wireless Zero config hang-up, or is Netgear
simply blowing smoke here?
Cam