Printable View
I want to use the dos command
shutdown -m computer -s
so I don't have to walk into my living room to turn of the family computer before going to sleep. When I run this command, the prompt says "access is denied." How do I get this access? I'm on a three computer LAN, all XP.
0ri0n
your local account on the box that you're currently using should be added to the administrators group of the box that you're attempting to shut down. this is assuming that you're running 2k/xp and that you've got a workgroup configuration. that's my guess though:)
Why dont u allow Remote Access from your other computer so you can just connect and click Shut Down without going to it ...
Can anyone explain how to do this??
0ri0n
yes of course , i'll explain it short and simple ;)
http://windows.about.com/library/weekly/aa020526a.htm
I think I've got it. Hopefully your under winXP pro.
Go to administrative tools>local security policy
In the window go to Local policies>user rights assignment>Shutdown the system
right click, go to properties.
click add user or group.
when you click the locations button you should see your workgroup, click on it then click ok.
Now click on advanced>Find now.
you should see a list of computers in your workgroup. Choose the ones you want to be able to shutdown the computer remotely then click ok>ok>apply>ok.
I got an error saying it was unable to save to the database which is why this didn't work for me. hopefully it works for you though. You may have to reboot for this to take affect.
Good luck.
Arighty, thanks for the help guys.
0ri0n
Sorry for the double post, couldn't edit the first one. I got what heretic said to work on my friends computer who's using professional, but I' only using home, and in administrative tools I don't have a local policies folder. Can anyone translate to Xp home for me? ThANKS
0ri0n
Ok... something about this bugs me.
You are not using DOS! You are using a DOS style command interrupter on Windows XP. If you don't believe me type:
ver
And see what it tells you. DOS has been gone since Win95 and was never a part of the NT line.
I know this is nitpicky, just like how the term "hardware firewall" bugs me as well... but computers are of an exact nature, therefore it is important to use exact language when discussing them. This way everyone knows what everyone else is talking about.
In the end it is better for everyone.
catch
PS. You can also configure the system to shutdown
if current_time > X
and system_has_been_idle > Y
This might be more effective for shutting down at bedtime, but of course lacks the flexibility of shutting down whenever.
I don't know if you can do the same thing on home. It lacks in the amount of tools compared to XP pro. I didn't even think they had an administrative tools. Try typing this at the run prompt:
gpedit.msc. It probably won't do anything though. If it works go under windows settings>local security policy and do the same thing that I told you. I'm glad it worked for your friend, mine wouldn't save the settings, I think I have some other settings keeping me from being able to let remote users shutdown the comp. You can try googling winXP Home remote shutdown. I found the above with google.
Good luck.
p.s. Tedob1 told me about a tool from systernals called psshutdown that will let you specify a user name and password. that should get you past the access denied. i'm going to try it today. here's the link
http://www.systernals.com/ntw2k/free...shutdown.shtml
0ri0n,
If XP Home won't allow you to do what you want, you could look at using something like VNC.
Real VNC
It allows you to remote control a PC or a server nice and easy. I've used it in the past for NT boxes at the other end of the world, and even that was a piece of cake.
(And it's freeware too! Although the authors do take contributions)
Cheers,
BrainStop
Sorry, I meant to say dos command...Quote:
You are not using DOS
Thanks to the rest of you guys.
0ri0n
I just found out that the shutdown command hasn't been blocked at my college. This could get fun...
=+=+=+=+=+=+=+=+=+
I just found out that the shutdown command hasn't been blocked at my college. This could get fun...
=+=+=+=+=+=+=+=+=+
do you like breaking bottles on the hyway and spray painting peoples pets too?
who doesn't? ;)
I bet they havn't made the books flame retardent either! or they havn't made the monitors so they can withstand bricks! or the keyboards water-proof!!!
now you aint gonna burn the books, smash in your monitor or take your keyboard swimming with you (at least i hope not) because your common sense should tell you that just because you can do something doesn't mean you should....and if not your common-sense then your instinct for self-preservation ;)
Just cause you can do something doesn't mean you have to do something
v_Ln
Please guys, I'm not gonna HACKSORZ THE NETWORK. I have friends that share their resources that will be more than happy to let me practice on their coms. I'm not an idiot...and our books arn't flame retardant. And as for that moniter well....
have you tested it. Just because it is not blocked doesn't mean you can shut down a remote computer. If you tried you would probably get a reply of "access denied". I'm not saying to try it, i'm just saying it probably wouldn't work anyway.Quote:
I just found out that the shutdown command hasn't been blocked at my college. This could get fun...
I'll get one of my friends to drop his firewall and let me try it out later, now I need sleep.
The title of this thread is funny
Shutting down a remote computer with dos.
it kind of suggests launching a denial of service attack on a remote computer, that is until you actually read the post.
Just wanted to point that out.
If you can get a copy of Pro you can create a group policy that can be copied and installed on the Home computers in the start-up process . . . this way you can either shut-down remotely or set a shut-down time . . .
I'm going to quote myself here and add on:
Today I just noticed another setting located in the same place(in the user rights assignments folder) called force shutdown from a remote system.Quote:
I think I've got it. Hopefully your under winXP pro.
Go to administrative tools>local security policy
In the window go to Local policies>user rights assignment>Shutdown the system
right click, go to properties.
click add user or group.
when you click the locations button you should see your workgroup, click on it then click ok.
Now click on advanced>Find now.
you should see a list of computers in your workgroup. Choose the ones you want to be able to shutdown the computer remotely then click ok>ok>apply>ok.
I got an error saying it was unable to save to the database which is why this didn't work for me. hopefully it works for you though. You may have to reboot for this to take affect.
Good luck.
I added the computer name that I wanted to be able to shut it down and bingo it worked.
I know this doesn't help people using xp home but if you have pro, this is how to give permission to a remote computer to let it shut you down. I actually had to set it to everyone on both of these because it wouldn't save to the database if I gave a computername. So now everyone with xp pro should be able to shutdown their machine from a remote machine on their network.
valhallen you never let me have any fun! :) anyway i was just funnen with him (notice no negs)
To shutdown a remote computer using shutdown.exe you must have admin rights on the network or as has been stated you get "Access Denied". Of course if your tired of school you could always pipe-up your rights.
Tedob1, I just shutdown one of my computers from another one without admin rights. Using the info provided in the post before yours is how I did it. In fact when I when to the computer I was shutting down it had a countdown and said that a shutdown has been issued by "Guest". I don't think that guest has admin rights. What I'm saying is that if you change the configuration with the steps from my last post in this thread you can make it to where anyone can shut down the computer remotely like I did. I set it to where the user "Everyone" can shutdown the computer, which is probably not good, but since I'm behind router with a firewall I don't think that it's a problem. By the way, does anyone know what port this uses. I would assume it uses port 139, but I could be wrong.