TL;DR: After SMB negotiates the protocol and establishes a session, my W10 PC sends a RST to my NAS causing the SMB connection to re-negotiate, forever.
I'm mostly sick of this not working and can't really be bothered typing up nice paragraphs, so this post might be a bit of a mess....
Everything was working, then one day it didn't. The only thing I remember changing in the timeframe was setting up Hyper-V (As part of my troubleshooting I removed it).
Usually, after I first boot up, I am able to access the NAS (Running FreeNAS latest stable) and see the list of shares, but accessing anything after that gives an error (Specifically “The specified server cannot perform the requested operation”).
Directly accessing the NAS or a share by the direct path gives a 0x80004005 Unspecified Error.
Other (Win 7) devices on the network can access the shares fine.
After a few days of being frustrated I pulled out Wireshark and set that running while I tried to access the share, here is what I see, repeated many many times (Until Windows devices to time-out, I guess), with some WebDAV scattered around (And obviously, failing):
Looking through the packets it seems to create a normal SMB2 connection, authenticates and upon receiving the accept-completed from the session setup it sends a TCP RST, which resets the connection and causes it to re-start the connection and negotiations again.
Things I've tried (Among other things that I've probably forgotten):
I'm at a total loss of where to go from here (And Microsoft decided to remove the ability to mount NFS shares as a network drive in Windows 10…) and wondering if anyone has any further things for me to try, even if they are blatantly obvious things to do – I expect the solution will be something very silly/simple (At this point I'm willing to try pretty much anything).
Full Samba log: https://gist.github.com/Cameron-D/372eb5e64cb04acc4758
Can provide packet dumps or any other debug info if they would be useful.
I'm mostly sick of this not working and can't really be bothered typing up nice paragraphs, so this post might be a bit of a mess....
Everything was working, then one day it didn't. The only thing I remember changing in the timeframe was setting up Hyper-V (As part of my troubleshooting I removed it).
Usually, after I first boot up, I am able to access the NAS (Running FreeNAS latest stable) and see the list of shares, but accessing anything after that gives an error (Specifically “The specified server cannot perform the requested operation”).
Directly accessing the NAS or a share by the direct path gives a 0x80004005 Unspecified Error.
Other (Win 7) devices on the network can access the shares fine.
After a few days of being frustrated I pulled out Wireshark and set that running while I tried to access the share, here is what I see, repeated many many times (Until Windows devices to time-out, I guess), with some WebDAV scattered around (And obviously, failing):
Looking through the packets it seems to create a normal SMB2 connection, authenticates and upon receiving the accept-completed from the session setup it sends a TCP RST, which resets the connection and causes it to re-start the connection and negotiations again.
Things I've tried (Among other things that I've probably forgotten):
- Different APs (I have a WD router that also does file sharing, got rid of that for the time being, ruling out everything possible). Yes, my PC is on wireless, I don't really have any way of running Ethernet to the other end of the house at the moment)
- NIC driver updates.
- Enabling, disabling, reinstalling the NIC and drivers.
- Removing/disabling all virtual network devices (ISATAP, Teredo etc.), although they do eventually reinstall themselves it still doesn't work while they're uninstalled.
- Disabled network device power management.
- FreeNAS up-to-date.
- Windows up-to date.
- Both devices can see each other (I can access HTTP interface and other jailed services).
- Both computers can access the internet and other devices on the network.
- IP configuration:
- Tried static and DHCP.
- Checked DNS (Get hostnamemismatch in logs, but that has never been an issue), both devices can resolve each other.
- Tried static hostnames through hosts file, both hostname and FQDN.
- Error occurs using both IP address and hostname.
- Enabling Windows Guest account.
- Forcing SMB encryption to be disabled from Windows.
- Turning the firewall off.
- From the Network Interface Properties I've:
- Reinstalled Client for MS Networks.
- Reinstalled File and Printer Sharing for MS Networks.
- Disabled IPv6.
- ...for wireless and (unused) wired interface.
- I had Hyper-V installed and a virtual switch running, removed all Hyper-V related network things and uninstalled Hyper-V.
- In FreeNAS' CIFS config I've:
- Played with various compatibility versions
- Changing guest account and password requirement
- Changing hostname lookups and interface bindings
- Scanning through Windows' logs doesn't seem to reveal anything of interest
- FreeNAS/Samba logs – even at debug level – contain nothing useful (there is a hostnamemismatch for each connect, but that doesn't mean much in this context).
- Rebooting every piece of hardware/network equipment.
- Virus scan.
- MS Defender Disabled.
I'm at a total loss of where to go from here (And Microsoft decided to remove the ability to mount NFS shares as a network drive in Windows 10…) and wondering if anyone has any further things for me to try, even if they are blatantly obvious things to do – I expect the solution will be something very silly/simple (At this point I'm willing to try pretty much anything).
Full Samba log: https://gist.github.com/Cameron-D/372eb5e64cb04acc4758
Can provide packet dumps or any other debug info if they would be useful.
