M
Mike W
We have a security template that restricts most users from
using network utilities (ping, tracert etc.) However, we
have experienced a unique problem with XP and NBTSTAT.
When an admin uses nbtstat -A (IP addy), it works great.
When a user (granted READ/EXE perms) uses the same
command, they get "Failed to access NetBT driver - NetBT
may not be loaded".
Now for the interesting part. I am logged on as an
admin. I used the RUNAS command line to open another
instance of CMD.EXE as the user. Then typed the command
in the new window. It works in window #1 (admin), but not
in window #2 (non-admin). Both users have the right to
read/execute the command.
Have tried tracing through regmon, processmon and filemon,
but can't seem to find what else NBTSTAT is looking for or
using that the user doesn't have the rights for.
using network utilities (ping, tracert etc.) However, we
have experienced a unique problem with XP and NBTSTAT.
When an admin uses nbtstat -A (IP addy), it works great.
When a user (granted READ/EXE perms) uses the same
command, they get "Failed to access NetBT driver - NetBT
may not be loaded".
Now for the interesting part. I am logged on as an
admin. I used the RUNAS command line to open another
instance of CMD.EXE as the user. Then typed the command
in the new window. It works in window #1 (admin), but not
in window #2 (non-admin). Both users have the right to
read/execute the command.
Have tried tracing through regmon, processmon and filemon,
but can't seem to find what else NBTSTAT is looking for or
using that the user doesn't have the rights for.