And I now have a RHEL5 machine that supposedly causes odd share names to appear on the Windows end.
Odd thing is..it doesn't have smb or nmb installed.
What sorcery is this?
@matigo Something has been done to printing and sharing over the last few updates that is causing really weird things to happen. I've had customers who's Windows 7 boxes, sharing printers, have had the connections to those shares just vanish from the Windows 10 boxes.
What it is doing to RHEL5 boxes running SAMBA would be comical if I didn't have to deal with it.
@skematica The internet is loaded with "Whazat prs_grow stuff mean?". Mostly unanswered because 10 million different things can cause it.
- Network discovery not working
- Faulty network connection.
- Improper encryption settings on the Windows side.
- Airborne allergens
- Phase of the moon
- Pique
My solution is to kill off all the shares from that box and do something productive with the day.
Kill off all SAMBA printer shares from my Windows 10 box. Hear audible sigh of relief from the SAMBA-running machines on the network.
I do so love these little updates from Microsoft.
The message log I am looking can only be described as a confused cry for help/mercy.
How CUPS says, "Let's annoy Tom today"…
prs_grow: Buffer overflow - unable to expand buffer by 2 bytes.Seriously. I don't have the time or patience to track down something silly.
@c Tom the keep bugging me in Google Hangouts, I dare you. :)
He's a good guy. I was kidding.
"I can format your hard drives from here ,too" just sent to my beta-testing customer.
@JeremyCherfas A walk in the park would have been more enjoyable but it's in the early AM here and in the mid 40F range. :)
Speaking of which, I'm going back to bed. Might even call in, "Not interested", to work tomorrow.
/// @matigo @c