That is very strange. I don't use current, but have 15.0 on several machines. All connect & interact with Windows shares without any problem... but I'm not using AD anywhere, so maybe not a fair comparison.

How old is that installation of Slackware current? My guess is that the difference that matters is the kernel version. If your Slackware current has a newer version of the kernel it might help to try a newer kernel on Slackware 15.

Did you install the linux-5.15.38 packages on your 15.0 installation?

regards Henrik

i cobbled this together for myself and coworkers to mount windows shares onto linux desktops. This worked well in a windows 2012+ active directory environment for read/write of those windows shares from linux


---
#!/bin/sh
# mount_CIFS.sh

read -p "Please enter your first.last: " USERNAME
CIFSMOUNT=/mnt/cifsmount

if [ ! -d "$CIFSMOUNT" ];
then
echo $CIFSMOUNT not found so i will make $CIFSMOUNT directory
sudo mkdir $CIFSMOUNT && sudo chmod 755 $CIFSMOUNT
echo mounting $CIFSMOUNT CIFS share
sudo mount -t cifs -o username=$USERNAME,uid=$(id -u $USERNAME),gid=$(id -g $USERNAME) //windows_server/share $CIFSMOUNT
else
echo $CIFSMOUNT found
echo mounting $CIFSMOUNT CIFS share
sudo mount -t cifs -o username=$USERNAME,uid=$(id -u $USERNAME),gid=$(id -g $USERNAME) //windows_server/share $CIFSMOUNT
fi

It must be the laptop itself - I migrated from 15 to current on laptop and it still can not work. My other machine works as simply as what the original responses indicate even after full current update.

It is a System76 Lemur Pro so would not think any adverse issues with Linux....

I'd be shocked if it's anything to do with the hardware itself.

If, by "migrated" you mean to say that you upgraded, then it's possible that you may still have a configuration file somewhere which is causing this behaviour.

Issues like this one are part of the reason why I'm an advocate for wiping and reinstalling rather upgrading between releases. I also advocate trying to keep things as "stock" as possible.