LanMan98 2.06 Connection lost (4)

The solution from Microsoft (but still don’t know that this is the correct diagnosis) to enable SMB1 is to type a long-winded and syntacically-correct instruction on the text window which threw up an error.

Are you talking about these instructions (that’s the Windows Server documentation, but I think the GUI stuff is the same on the desktop as well)?

If that fails and you go back to “the text window” (?), bear in mind that it says “PowerShell” on that page – trying to use the commands given in a standard Command window might not be that successful. You’ll find the PowerShell in the start menu, in the usual place. Oh, and it may need to be a PowerShell started as Administrator, too.

You’ll find the PowerShell in the start menu, in the usual place.

Various routes to the PS shell, one is: Right-click Windows logo, Select “Run”, type “powershell”, right-click icon on task bar and select run as administrator

On a windows note, if you’re using the Windows LPD (Unix print services) to provide a print share – the recent “update” of Windows will have broken it.

the recent “update” of Windows will have broken it.

…again.
Reading El Reg, it seems far far too many updates break something to do with printing.

it seems far far too many updates break something to do with printing.

Fixed.

What they need is someone like Nemo to tell them how stupid some of those changes are. :) Diplomatically of course.

You might, very briefly, question how I know it breaks LPD. Then you realise that I probably know of something like a Unix server based application that doesn’t support “slave” printing¹ so the requirement is either lots of print servers (one per client), lots of extra network points for the print servers (don’t do two port print servers²) OR you make the PC client present a print server service that Unix understands – hello LPD :)
20+ years down the line³, it still works – when MS aren’t being stupid.

¹ Basically, printing to the client terminal session print queue.