|
||
|
|
|||||||
| Welcome to the Exploding Garrmondo Weiner Interactive Swiss Army Penis. |
|
GFF is a community of gaming and music enthusiasts. We have a team of dedicated moderators, constant member-organized activities, and plenty of custom features, including our unique journal system. If this is your first visit, be sure to check out the FAQ or our GFWiki. You will have to register before you can post. Membership is completely free (and gets rid of the pesky advertisement unit underneath this message).
|
![]() |
|
|
Thread Tools |
Merv, I thought it was /m \\COMPUTER_NAME?
It's been too long since I've used Windows, but that's what all my online references say. And if she's not an administrator, you could disable her right to alter the file (since in Scheduled Tasks, it'll run as whoever you set it up with). Beyond that, you can try the below. The first line kills her account (makes it impossible to log in with it), and the second shuts down the box with some extra switches. Code:
net user ACCOUNT_NAME /active:no shutdown /s /f /t:30 /c "Shutting down in 30 seconds. Please save your files." To enable the account again, another scheduled task that calls as below would work fine: Code:
net user ACCOUNT_NAME /active:yes Jam it back in, in the dark. |
Do both computers have the same Workgroup set? If not, I believe remote shutdown attempts will always fail. Further, is the computer actually named "FAMILY"? Check in System Properties to make sure (enter it in the command as displayed--I don't think Windows cares, but you never know).
Next, when the other machine is on, get its IP. I will assume 192.168.0.100, so alter that as necessary below. Then, enter this into Explorer's address bar (as in the File Manager) and hit Enter:
If that works, try running your shutdown command again using the IP address instead of the computer's name? There's nowhere I can't reach. |
That's why I mentioned the account name/passwords being equal.
![]() Back on Windows 98, I was required to use accounts with the same username and password pair to share files and devices amongst them. Even 98->XP seemed to need this. Technically speaking, I don't think Windows XP even cares about computer names on workgroup logins like this. Again, not sure though. This thing is sticky, and I don't like it. I don't appreciate it. |
From what I gathered of the first post, the Family computer is connected through Wireless. If you just knocked the connection off (or shut the box down), she'd be able to kick it back on and connect to that other, slow network, would she not?
Or did I just completely misunderstand you? Interesting router feature, though--I've never seen that before. I am a dolphin, do you want me on your body? |
I don't think that'd be the cause of the problems, no. If you got in with \\address\C$ on a guest account, that's a bit of a security issue. Beyond that, I don't really know what to tell you. Does Task Scheduler recognise that batch file I posted earlier? If so, why not give it a shot, since it'd kick her off and kill the account. :P
For help with your router's configuration, check out http://www.portforward.com and see if they have documentation to help you. How ya doing, buddy? |