Printer Using WSD vs IP
-
I run into this from time to time.. The computer decides after it has been out of the office that instead of using the set port of the Static IP address, it drops back to WSD?, where then it fails to print.
Why does Windows think it knows better by using teh WSD port rather than the USER SET IP port?
#WindowsisFrustrating
-
following thread.
FYI, I rarely if ever have this problem when printing through a Windows Print Server, but that idea is quickly dieing.
-
Hate WSD with a passion in a business environment.
-
WSD is so terrible. It automatically adds a printer to every pc on a network if network discovery is on.
"Hey lets install this printer automatically when you join a network. Doesn't matter if youre an engineer and this printer is for HR, you logged in to the network you get this printer now."
WSD takes control away from you; that's MS' new strategy: Control everything badly, but better than most IT people.
But i suppose you cant really blame them when you see the terribleness of many IT people.
Theres a post from ThanksAJ on spiceworks about this, have you tried that? -
You can try disabling WSD on the printer itself, if it isn't a service for Windows to see perhaps it wont try to use it.
-
@momurda said in Printer Using WSD vs IP:
You can try disabling WSD on the printer itself, if it isn't a service for Windows to see perhaps it wont try to use it.
This is the same thing we do to avoid this nasty printer plague
