J
Julian Abramowitz
What's the difference between using "sc \\computername stop service" from a Windows 7 computer over the network to stop a service on an XP computer and going over to the XP computer and using "net stop service" locally? I thought there was no difference.
I have a parallel printer hooked up to my old Windows XP computer. My Windows 7 and later computers lack such a port.
For whatever reason, the HP drivers don't like to cancel a job, and I usually need to first "cancel all print jobs", then stop and then start the spooler service (not restart, for some reason it doesn't work if I use net restart) on the XP machine (typically by using "net stop spooler" followed by "net start spooler").
Today I had such an issue, and I was trying to cancel one job and print another from Windows 7. I was feeling lazy, not wanting to go into the other room, so I opened up the network printer, cleared the jobs, then ran CMD as administrator and typed:
sc \\slickswintel stop spooler
then when it reported a success I counted to five, then typed
sc \\slickswintel start spooler
When it said the spooler was back online, I tried to print, but it did not work, and the canceled job from the other day was still "deleting".
Yet when I bit the bullet and got up and logged in with my admin account on the other computer and repeated the procedure (the admin account is the same on all my computers), it worked.
What's the difference between using sc stop/start remotely and net stop/start locally? I thought it was supposed to be the same.
I don't ever remember having an issue like this with a difference before.
P.S. I'm unsure if this belongs in network, devices & drivers, or what.
Continue reading...
I have a parallel printer hooked up to my old Windows XP computer. My Windows 7 and later computers lack such a port.
For whatever reason, the HP drivers don't like to cancel a job, and I usually need to first "cancel all print jobs", then stop and then start the spooler service (not restart, for some reason it doesn't work if I use net restart) on the XP machine (typically by using "net stop spooler" followed by "net start spooler").
Today I had such an issue, and I was trying to cancel one job and print another from Windows 7. I was feeling lazy, not wanting to go into the other room, so I opened up the network printer, cleared the jobs, then ran CMD as administrator and typed:
sc \\slickswintel stop spooler
then when it reported a success I counted to five, then typed
sc \\slickswintel start spooler
When it said the spooler was back online, I tried to print, but it did not work, and the canceled job from the other day was still "deleting".
Yet when I bit the bullet and got up and logged in with my admin account on the other computer and repeated the procedure (the admin account is the same on all my computers), it worked.
What's the difference between using sc stop/start remotely and net stop/start locally? I thought it was supposed to be the same.
I don't ever remember having an issue like this with a difference before.
P.S. I'm unsure if this belongs in network, devices & drivers, or what.
Continue reading...