F5F Stay Refreshed Hardware Desktop Credentials from FreeNAS or TrueNAS aren't being recognized on the network.

Credentials from FreeNAS or TrueNAS aren't being recognized on the network.

Credentials from FreeNAS or TrueNAS aren't being recognized on the network.

J
JopperMan
Member
121
08-12-2016, 06:11 PM
#1
Hi everyone, I'm setting up a Truenas server using Windows SMB shares. I'm new to this and have tried following the guides to get everything working. I can access my Windows share from my laptop as expected, copying files and viewing them. However, when I use the same login from my Windows 10 desktop, I get an error saying "invalid network credentials." I've changed network settings on both machines to private, backed up credentials from my W11, and even tried mapping the drive or using the network section in File Explorer. I also reset my Windows 10 user account and logged back in on W11, but the issue persists on W10. I created a new account on W10 too, yet it still fails. I've connected a PCIE NIC on my PC with a new IP, but nothing changes. Any suggestions or checks you can recommend? This seems similar to the post you linked. Thanks!
J
JopperMan
08-12-2016, 06:11 PM #1

Hi everyone, I'm setting up a Truenas server using Windows SMB shares. I'm new to this and have tried following the guides to get everything working. I can access my Windows share from my laptop as expected, copying files and viewing them. However, when I use the same login from my Windows 10 desktop, I get an error saying "invalid network credentials." I've changed network settings on both machines to private, backed up credentials from my W11, and even tried mapping the drive or using the network section in File Explorer. I also reset my Windows 10 user account and logged back in on W11, but the issue persists on W10. I created a new account on W10 too, yet it still fails. I've connected a PCIE NIC on my PC with a new IP, but nothing changes. Any suggestions or checks you can recommend? This seems similar to the post you linked. Thanks!

T
techiseasy
Senior Member
688
08-12-2016, 07:32 PM
#2
It appears only the specific Windows 10 client you're using is displaying this issue, but other clients may also encounter the same problem.
T
techiseasy
08-12-2016, 07:32 PM #2

It appears only the specific Windows 10 client you're using is displaying this issue, but other clients may also encounter the same problem.

S
Sloth_Gaming
Member
137
08-12-2016, 08:30 PM
#3
I verified my work laptop (W10) and everything is functioning properly, indicating the problem might be on your desktop. Consider checking connections, restarting both devices, or looking into software conflicts.
S
Sloth_Gaming
08-12-2016, 08:30 PM #3

I verified my work laptop (W10) and everything is functioning properly, indicating the problem might be on your desktop. Consider checking connections, restarting both devices, or looking into software conflicts.