User's can't access wireless network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Got a w2k PC that's got wireless NIC. Works fine if booted into admin
account first. Logoff and log on users (power users) OK - Users loose the
systray icon for the NIC - or at least it behaves as though NIC dead. But
NIC up and running and working fine. But if boot and log into User, withough
loggin in as Admin first, then NIC really is dead.

If then logoff and log in as Admin, with no reboot, NIC starts, and it
generates the following entry in event viewer:
The system detected that network adapter D-Link AirPlus G DWL-G510 Wireless
PCI Card #2 was connected to the network, and has initiated normal operation
over the network adapter.

Any body advise me how to get W2k to allow users to log in and have working
wireless NIC?

THanks
 
Mikek13 said:
Got a w2k PC that's got wireless NIC. Works fine if booted into admin
account first. Logoff and log on users (power users) OK - Users loose the
systray icon for the NIC - or at least it behaves as though NIC dead. But
NIC up and running and working fine. But if boot and log into User, withough
loggin in as Admin first, then NIC really is dead.

If then logoff and log in as Admin, with no reboot, NIC starts, and it
generates the following entry in event viewer:
The system detected that network adapter D-Link AirPlus G DWL-G510 Wireless
PCI Card #2 was connected to the network, and has initiated normal operation
over the network adapter.

Any body advise me how to get W2k to allow users to log in and have working
wireless NIC?

THanks
Click to expand...

In your post you say "the NIC is dead" "the NIC start" etc.
without stating exactly how you came to these conclusions.

The usual way to detect the condition of a network adapter is
to open its status panel via the Control Panel / Networks.

Another way is to start a Command Prompt, then to type

ipconfig /all

If you still believe that your wireless adapter is dead while
logged on as an ordinary user then I suggest you do the
following:

- Click start / run / cmd {OK} to start a Command Prompt.
- Type ipconfig /all > c:\ipconfig.txt {Enter}
- notepad c:\ipconfig.txt

Now paste the contents of ipconfig.txt into your reply.
 
Hi - thanks. I did detect this from Control Panel - and from IPCONFIG as
you had suggested. I should have posted the IPCONFIG messages that the cable
was disconected. Post below

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : lucindas
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : D-Link AirPlus G DWL-G510
Wireless PCI Card #2
Physical Address. . . . . . . . . : 00-0F-3D-60-EE-1E

When I had this trouble with WinME I just unticked the Check Media connected
box or whatever it was called. But the security of ME is somewhat simpler!

I guess this is really a security question.... but what do you think?

Thanks
 
I have seen this message a few times before, and in each
case it related to the security configuration of the wireless
network adapter not matching the security configuration
of the access point. However, on every machine I have
seen so far, the network adapter's operation was
independent of the current user, as it should be. You report
that the adpater works for admins but not for ordinary users.
Your observation is at variance with my own observations.

You could try to promote the user to admin status during
your tests, and see if this makes a difference. I don't think
it will but then one has to keep an open mind.
 
Hi - done that, and symptoms are the same in that now NIC works for user at
log on post boot. If I then put user back in power users group, it doesnt
work. .... unless any user with administrative rights logs in first.

Regards

M
 
I wonder if the NTFS permission structure on your disk has been
disturbed. If, for example, someone prevented the "System"
account from accessing certain files or folders under the c:\WinNT
folder then you might get the type of phenomenon you describe.
On the other hand - who would want to play around with the
permissions granted to the System account?
 
Back
Top