F5F Stay Refreshed Power Users Networks Issue with SMB on Windows 10 following repairs. Unable to restore functionality.

Issue with SMB on Windows 10 following repairs. Unable to restore functionality.

Issue with SMB on Windows 10 following repairs. Unable to restore functionality.

D
Da_Shadows
Member
185
09-05-2016, 05:36 AM
#1
Windows 10 client struggles to reach SMB share while other devices work. I can ping the server from my PC but not access the share, receiving a generic error. SMBv1 is disabled on both server and Windows, yet enabling it didn’t resolve the issue. Need guidance on troubleshooting steps. Please share any logs or screenshots if possible. Thanks!
D
Da_Shadows
09-05-2016, 05:36 AM #1

Windows 10 client struggles to reach SMB share while other devices work. I can ping the server from my PC but not access the share, receiving a generic error. SMBv1 is disabled on both server and Windows, yet enabling it didn’t resolve the issue. Need guidance on troubleshooting steps. Please share any logs or screenshots if possible. Thanks!

N
NayZayRay
Member
189
09-05-2016, 05:54 PM
#2
Can I send a message to Truenas? (Name not an IP address) Are you still using the DNS Cache feature in Windows? Does WS-Discovery appear on your NAS? (Network - Global Configuration)
N
NayZayRay
09-05-2016, 05:54 PM #2

Can I send a message to Truenas? (Name not an IP address) Are you still using the DNS Cache feature in Windows? Does WS-Discovery appear on your NAS? (Network - Global Configuration)

H
Hiudy
Member
90
09-05-2016, 07:13 PM
#3
Thank you for your response. I understand the DNS cache service is turned off on Windows, as shown in the screenshot. (Is it supposed to be enabled?) I’m unable to address the other two questions at the moment because I’m working and will update you once I’m back home. Thanks again for the feedback.
H
Hiudy
09-05-2016, 07:13 PM #3

Thank you for your response. I understand the DNS cache service is turned off on Windows, as shown in the screenshot. (Is it supposed to be enabled?) I’m unable to address the other two questions at the moment because I’m working and will update you once I’m back home. Thanks again for the feedback.

P
PunjabiAK74U
Member
73
09-05-2016, 10:12 PM
#4
I checked this recently too. It has to be turned on, or else it messes with all the networking features in Windows. That covers things like linking to your NAS. I tried enabling it, restarted, and everything worked perfectly—no issues connecting to my NAS afterward.
P
PunjabiAK74U
09-05-2016, 10:12 PM #4

I checked this recently too. It has to be turned on, or else it messes with all the networking features in Windows. That covers things like linking to your NAS. I tried enabling it, restarted, and everything worked perfectly—no issues connecting to my NAS afterward.

L
liseypop
Member
214
09-06-2016, 01:38 AM
#5
Activated the DNS cache and restarted the computer, but issues persisted. Both IP address and hostname can be pinged successfully. WS-Discovery is active in TrueNAS. Feel free to share additional ideas if you have any, and thank you for your help!
L
liseypop
09-06-2016, 01:38 AM #5

Activated the DNS cache and restarted the computer, but issues persisted. Both IP address and hostname can be pinged successfully. WS-Discovery is active in TrueNAS. Feel free to share additional ideas if you have any, and thank you for your help!

R
Rosario17_
Posting Freak
897
09-06-2016, 02:28 AM
#6
That sounds confusing. I expected it to be something like 192.168.1.232 with a name, but it just showed the IP address.
R
Rosario17_
09-06-2016, 02:28 AM #6

That sounds confusing. I expected it to be something like 192.168.1.232 with a name, but it just showed the IP address.

J
JuicyDiamond
Member
85
09-06-2016, 09:15 AM
#7
No worries, your help was more than welcome, thanks a lot! Yes, I tried both \\192.168.1.232\ and \\192.168.1.232\Name_of_the_share\. When it was still working I was able to use \\192.168.1.232\ when putting the path in the file explorer manually but when adding it as a network location/mapped drive I needed to use the \\192.168.1.232\Name_of_the_share\. If anyone else in the forum has any idea, please let me know, I would be more than happy to test other possible solutions.
J
JuicyDiamond
09-06-2016, 09:15 AM #7

No worries, your help was more than welcome, thanks a lot! Yes, I tried both \\192.168.1.232\ and \\192.168.1.232\Name_of_the_share\. When it was still working I was able to use \\192.168.1.232\ when putting the path in the file explorer manually but when adding it as a network location/mapped drive I needed to use the \\192.168.1.232\Name_of_the_share\. If anyone else in the forum has any idea, please let me know, I would be more than happy to test other possible solutions.

G
GoCoyotes
Junior Member
22
09-07-2016, 11:35 PM
#8
I checked all available resources and still couldn't find a fix. After more testing, it seems the issue lies with Windows itself. Since I installed a new Windows on an extra SSD and everything functions properly, the problem must be related to the operating system. I'm going to format Windows and begin from scratch.
G
GoCoyotes
09-07-2016, 11:35 PM #8

I checked all available resources and still couldn't find a fix. After more testing, it seems the issue lies with Windows itself. Since I installed a new Windows on an extra SSD and everything functions properly, the problem must be related to the operating system. I'm going to format Windows and begin from scratch.