- #MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS INSTALL#
- #MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS DRIVERS#
- #MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS UPDATE#
- #MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS DRIVER#
#MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS INSTALL#
The issue here is that I install the printer using a TCP/IP address for the port. Whilst I may not be a trail-blazer, it's good to see we can all share from our experiences.
WSD might be great for road warriors (as well as letting Windows manage default printer - yet another Windows 10 10586 gotcha!) who want to print to somewhere while they're in transit, but it's not great for deskbound offices where everything is static.
#MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS UPDATE#
Maybe it could also be something to do with 10586 update as well (my computer is still 10240). It looks like it might also have something to do with printer age as well, where my office printer (Brother MFC-9840CDW) has installed the WSD port, but did not default to it after Windows 10 upgrade. and the other with the basic Remove Device and Properties. However, I now see two printers (with identical names) one with full access to Printer Properties, etc. Once I disabled WSD, Windows 10 went WTF!, put the printer off-line at which point I reset it to IP addressing. Different manufactures will be located elsewhere, but it's a start to look at the devices in a SMB environment. This is available as an On or Off setting. In the Kyocera's case it was under Advanced -> Network -> Protocol. Depending on the printer models (my client has several Kyocera models in their office - small business non-AD or server management) where I was able to turn WSD off on most of the newer printers. I know this is an old post, with another similar end result (see link below) but just putting it out there as I happened to look this up tonight after fixing a client setup today to see what other spice community members had seen.Īfter upgrading my clients computers to Windows 10, all of a sudden their printers started to pick up WSD as the default (now I find out you can stop that as part of the upgrade process - too late he cried!) and printing slowed to unproductive speeds after a few days. I believed that had been effective, but since obviously it goes back to a WSD port config, it was not.Īs far as I'm aware, the printer had been working on one of the PCs in question that I installed in July, but this has been a more recent problem. What I tried last night was to just change the port, but it would not allow any configuration of the existing port, which is why I resorted to the deletion/reisntallation. On some machines in some departments, we've started doing universal drivers, but I don't think this is one of those because most of their printers are not HP. Are you saying this is a function of the WSD? I was thinking it was a setting issue on the printers, but I could never find anything one way or the other. Now, it's interesting what you say because I have often wondered why some printers auto-discover and some printers do not.
#MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS DRIVER#
I installed some of these computers in the last few months, and typically, since we are not yet to GPO, I'll do them all manually via IP, and more often than not, it will not find the driver itself and so I will choose it from a list.
#MAC SAMSUNG THE CURRENT PRINTER PORT IS NOT SUPPORTED FOR THE PRINTER STATUS DRIVERS#
Also, after it's installed, instead of removing it and re-adding, have you tried changing the port to a TCP/IP port and leaving what's on there as far as drivers alone? Post back. Also, make sure you are using the right bit driver (x86 or 圆4 where approrpiate). Did you let it auto-discover for the driver or did you run a manufacturer's installer? That would make it use WSD for the port if you let it auto-discover the driver. That's what I've found works better at times.
How did you install the driver? Have you tried switching to a different driver? If you are using PostScript, try PCL5 if it's XP or PCL6 if it's Vista, 7 or 8. It makes it a WSD port with some long hex type number like "WSD-22dc14d6-c169-47e7-ab33-bf19e5958dfb.003a" At that point, the print job fails and/or printer is reported as being offline. They should NOT be uninstalling, what appears to be happening is that instead of it being the usual tcp/ip port of 10.65.x.x. We will be doing printers via GPO after we finish our move to a new AD, but for now they are all manual.
0 kommentar(er)
