Printable View
I run Win 7. Ive recently stopped winPcap from running at boot so I had to start it myself. when trying to run it from the command line it then asks me for administrator password. I am the sole user for this computer, my account is set up as administrator so i typed the password I use to log onto OS with.
It doesn't work.
I tried disabling my account password and it still asks for one. Is there a different default one Im not aware of?
Im not getting it.
which version of W7 you running
and as per normal MS traits, there is an admin account set up as you build the PC
hopefully you wont have a blank password set up
OR failing that, try adding the full name to your account
is it on a domain
mydomain\myaccount
or even
thisPC\myaccount
but there are lots of things that can trip you up
and in about two more OS's MS should have 'em all set in place :D
version 6.1.7601 SP 1
no domain
lmao, you'd think they'd have them figured out by now :drink:Quote:
but there are lots of things that can trip you up
and in about two more OS's MS should have 'em all set in place :D
Try disabling UAC temporarly then try again to run the command.
or place a shortcut to the cmd prompt onto the Desktop, then all you need to do is right click and choose the Run as Administrator.
This can be done by clicking the start button, then in that little search box type cmd . Then simply right click on the little icon that appears, then select send to Desktop. It will make a shortcut icon onto your desktop.
Only other idea i can think of at the moment is just to turn of UAC completly.
I think if you type 'cmd' into the start search, and then press ctrl+shift+enter, it will open the session as an admin.
Have you tried starting it from services.msc?
I swear to god I am such a *tard ...
I had tried all the above suggestions and none of them worked.
this is the cmd command I was using:
runas /u:administrator "net start npf"
and of course it was asking me for the password. I figured since I had the admin account set up for myself that it would be the same password as to access my account (the sole one on my computer). I was wrong.
I changed the command to this:
runas /u:[my account name] "net start npf"
And of course I was then able to use my password.I also took ownershipof the cmd program first but that still didn't work using the original command syntax.
Though I finally figured it out I still don't understand why the /u:administrator switch didn't work since I am the administrator.
If anyone who can explain this and who doesn't mind keeping this thread open long enough to do so would, I would be really appreciative.
Thanks
Did you enable the account named “administrator”?
( Check the properties of the user “administrator” to see if it is disabled or not )
Is your account name -> Administrator or is it something else?Quote:
runas /u:[my account name] "net start npf"
Exactly what service is npf? Is it present in the listed services display from services.msc?
Yes, the admin account is enabled.Quote:
Did you enable the account named “administrator”?
( Check the properties of the user “administrator” to see if it is disabled or not )
No, my account name is my old military call name, not administratorQuote:
Quote:
runas /u:[my account name] "net start npf"
Is your account name -> Administrator or is it something else?
NPF is Net Packet Filter for capturing live network packets through WireShark (WinPCap)Quote:
Exactly what service is npf? Is it present in the listed services display from services.msc?
I could not find it anywhere in services.msc. there is no search function but I spend quite a while scrolling through it looking.
That's most likely the reason for your net start command failure.
From a cmd window enter net start. You'll get a list of running services.
Then pick a service to play with and enter net stop <service name>
followed by a net start <service name>.
You don't need to use "the" administrator account as long as your own account has admin privileges.
lol, yeah ok. I just messed with it and you're right.
Thats another example of me trying to be cleverer than the situation calls for :p
Im in the midst of writing a batch to automate it right now anyways, soo ........ problem solved.
(Until Im back here because I messed up the .bat file somehow, lol
Thanks
Please accept this as an educated guess rather than a definitive technical explanation, but I believe that foxy~ has it right.:)Quote:
Though I finally figured it out I still don't understand why the /u:administrator switch didn't work since I am the administrator.
If anyone who can explain this and who doesn't mind keeping this thread open long enough to do so would, I would be really appreciative.
I haven't really played with Windows 7 that much, but Windows creates a default administrator account of its own when you install it. In addition the first user account that you create is defaulted to be a member of the administrators group.
AFAIK, the default administrator account only shows up when you log in into safe mode, and the default password is blank. I have seen the default account use the same password as the original user, but I am not sure if that was Windows or the user altering it afterwards.
The bottom line is that I believe that the default admin account is only available in safe mode, which would be why your first command failed?
If anyone knows better, please enlighten us. :)
You know - I never even thought of that, but I think you're right. when i get some time quick, I'll check it out and let you knowQuote:
The bottom line is that I believe that the default admin account is only available in safe mode, which would be why your first command failed?
The command failed because it was attempting to start a nonexistent service.
The default Administrator account is visible and can be managed as part of normal Windows 7 operations via Computer Management, Local Users and Groups. It has the same privileges as any other account in the Administrators group. After installing the OS the next thing I do is disable the Administrator account and Guest account. I am discussing a non-domain environment. In a Windows domain things get more complicated because there are separate local and domain sets of users, groups and privileges interacting with each other.