Win 10 Build 21H1 breaks SMB 1.0 printer UNC path support
ad...@reviews.wox.org
Just a heads up that SMB 1.0 support in the latest windows 10
build 21H1 update seems to be broken for the print protocol even
if it is enabled in "turn windows features on/off" Not sure if
this is universal so your milage may vary depending on the given
scenario.
Your print queue will simply throw "error printing" or if you view
the UNC path directly eg \\1.2.3.4\yourprinter it will throw an
error 0x00000709
File sharing SMB 1.0 support appears to be unaffected, and will
continue to work as expected.
This means some older SMB based printer sharing devices/print
servers, samba linux print servers, and older windows workstations
with shared printers may be unable to print any more if you
upgrade your windows 10 past build 2004.
Previously this issue has cropped up in earlier versions of
windows, and was fixed by either a "net use lpt2: \\path\printer"
then using lpt2 in printer setup or changing registry permissions
to full control on application packages/restricted/administrators
in HKEY_CURRENT_USER\Software\Microsoft\WindowsNT\CurrentVersion\Windows
But this does not appear to work in build 21H1
I will let you know if I find a work around, although I expect
only a minority of you may be impacted by the issue anyway, since
it is unlikely any of you are reproposing old hardware for print
servers.
If anyone else knows a work around let me know.. it is
inconvenient to have to pdf work request documents and copy them
over the network to print at the moment, and I cant move the
printer to a newer machine as a cash register needs to print to
it!
-- New and improved 2600... well.. ..we drew on some flames and polished it a bit.. -- Google - making sure, life is no more, than 1984... --
Kent
--
--
------------------------------------------------------------
You received this message because you are subscribed to the "2600 Australia" group.
To post, send email to: 2600-au...@googlegroups.com
To subscribe, send email to: 2600-austral...@googlegroups.com
For 2600 monthly meetings, visit http://www.2600AU.org
For more options, visit this group at http://groups.google.com/group/2600-australia
To unsubscribe, send email to: 2600-australi...@googlegroups.com
Disclaimer: Comments to this mailing list are owned by the poster
------------------------------------------------------------
---
You received this message because you are subscribed to the Google Groups "2600 Australia" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600-australi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/2600-australia/00b2052f-7067-4895-7bd7-202ad2614259%40reviews.wox.org.
ad...@reviews.wox.org
Well the same update seems to have rolled out on my cafe computers now, (it effects windows home and pro) and all of them cant print either. Time to buy a dedicated network print server I guess.
I might try to uninstall updates on the cafe machine until the problem goes away to narrow it down to the exact update, (although half the time it wont let you bloody MS)
On 18/10/2021 2:28 pm, Kent wrote:
Have you tried adding the server to the trusted list?[Hkey_local_machine\software\policies\microsoft\windows nt\printers\pointandprint\]"Serverlist"="1.2.3.4"
Just a heads up that SMB 1.0 support in the latest windows 10 build 21H1 update seems to be broken for the print protocol even if it is enabled in "turn windows features on/off" Not sure if this is universal so your milage may vary depending on the given scenario.
Your print queue will simply throw "error printing" or if you view the UNC path directly eg \\1.2.3.4\yourprinter it will throw an error 0x00000709
File sharing SMB 1.0 support appears to be unaffected, and will continue to work as expected.
This means some older SMB based printer sharing devices/print servers, samba linux print servers, and older windows workstations with shared printers may be unable to print any more if you upgrade your windows 10 past build 2004.
-- New and improved 2600... well.. ..we drew on some flames and polished it a bit.. -- Google - making sure, life is no more, than 1984... -- In politics - Later never happens.
ad...@reviews.wox.org
it. The first one does, and i immediately kick myself for
not writing down which one it was.
face palm moment.
On 11/11/2021 3:20 pm, ad...@reviews.wox.org wrote:
> That fix doesn't seem to work.
>
> Well the same update seems to have rolled out on my cafe
> computers now, (it effects windows home and pro) and all
> of them cant print either. Time to buy a dedicated network
> print server I guess.
>
> I might try to uninstall updates on the cafe machine until
> the problem goes away to narrow it down to the exact
> update, (although half the time it wont let you bloody MS)
>
ad...@reviews.wox.org
Well in the internet cafe side at least, it was KB5007186 to
blame, the same update will throw page fault in non paged area
after install on a few older ASUS gaming laptops too i notice. A
quick search online suggests this sh*tty update breaks a few other
things too.
Sadly removing that update doesn't fix my accounting machine, as
presumably the same breaking change went out in one of the updates
installed after it too.
I did notice tho, on some machines that a weird "printing software
update" appeared on some machines after kb5007186 crashed a few
times. It seems pretty random, but at a guess some printer makers
running smb on their printers complained, and MS did a patch so
theirs still work.
I've got another client who's own (quite recent model) printers
stopped working around the same time, so I am surprised this
breaking change hasn't popped up more.
I guess hardly anyone uses network printers, or they didn't make
the connection and just got a new printer that didn't use SMB.
-- New and improved 2600... well.. ..we drew on some flames and polished it a bit.. -- Google - making sure, life is no more, than 1984... -- In politics - Later never happens.
Sid E
PC LOAD LETTER
What the fuck does that mean?
--
--
------------------------------------------------------------
You received this message because you are subscribed to the "2600 Australia" group.
To post, send email to: 2600-australia@googlegroups.com
To subscribe, send email to: 2600-australia+subscribe@googlegroups.com
For 2600 monthly meetings, visit http://www.2600AU.org
For more options, visit this group at http://groups.google.com/group/2600-australia
To unsubscribe, send email to: 2600-australia+unsubscribe@googlegroups.com
Disclaimer: Comments to this mailing list are owned by the poster
------------------------------------------------------------
---
You received this message because you are subscribed to the Google Groups "2600 Australia" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600-australia+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/2600-australia/733a6cf9-63c4-9b79-e9c8-2fdcf8e0d938%40reviews.wox.org.
ad...@reviews.wox.org
Either that or you are required to load a politically correct apology letter, perhaps you don't identify as one of the zillion imaginary non-genders society expects now..
On 27/11/2021 1:27 am, Sid E wrote:
PC LOAD LETTER
What the fuck does that mean?