SMB all of a sudden doesn't work!

[Geoff Bricker]

I setup an SMB and used crashplan to backup to a network folder. I disconnected my Ethernet at one point and reconnected and that's the only thing that has changed as far as I can recall. I since then rebooted several times (windows 10 pro 64 bit) but cannot access my drive. I can view the share and the folder but when I try to enter credentials, it doesn't work.

I've re-done my password for the user account on FreeNAS box as well, still not letting me access.

I don't even know where to begin on FreeNAS to figure out if there is a log someplace to even say what the error might be.

FreeNAS 11-Stable

 

[nojohnny101]

Per forum rules, please post your full system specs.

Does your motherboard have more than one ethernet port?

 

[Ericloewe]

Per forum rules, please post your full system specs.

And FreeNAS version.

 

[Geoff Bricker]

I did post the FreeNAS version, 11-Stable. As for the system specs, I wasn't sure that mattered since other items are working just not SMB. https://pcpartpicker.com/list/G8ZqM8 is the parts list.

Yes, it does have dual ethernet ports.

 

[Geoff Bricker]

FreeNAS-11.0-U1 (aa82cc58d)

 

[Geoff Bricker]

Apple timemachine backup works fine...but I see nothing when attempting windows

Code:

Jul 11 16:37:17 ultron afpd[30954]: Login by geoff (AFP3.4)
Jul 11 16:39:35 ultron afpd[30954]: AFP logout by geoff
Jul 11 16:39:35 ultron afpd[30954]: AFP statistics: 193945.19 KB read, 293218.96 KB written
Jul 11 16:39:35 ultron afpd[30954]: done

 

[nojohnny101]

Please post system specs next time in the thread. Call people lazy, but no one wants to follow an external link in researching your problem. PC part picker is also notoriously bad in many ways.

Annnnyways, so it looks like your motherboard has multiple LAN ports. Are you sure that you plugged back into the same port you had it in before?

Is this behavior the same if you try accessing from a different client machine?

I can view the share and the folder but when I try to enter credentials, it doesn't work.

What does this mean? That statement is incredibly vague. What kind of error does windows give you?

Have you tried restarting the SMB service? Have you tried restarting the client machine?

 

[Geoff Bricker]

Not a single thing has been said to even remotely begin to help me find the culprit within the freenas system (assuming thats where it lies)...

I rebooted the CLIENT computer (Windows 10 Pro 64Bit Intel Core i7 32GB DDR4 RAM yada yada yada) multiple times. That was the machine that had the ethernet cable removed and placed back (not that it would matter, since the network is clearly functioning based on previous post).

If you've used windows 10 and have gone to map a network drive, the message is not "incredibly" vague. Perhaps you're unclear with it. Its quite simple though, if you goto your computer (called 'This PC') you can then click Computer and then Map Network Drive. Once you do that, you can browser or type in the network location. I chose to browse and type in manually. Browsing shows the server name and the share drive, however when I try to access it after being prompted for my credentials, it fails (when it originally succeeded when first used prior to this randomly stop working).

I also have restarted the SMB service on the FreeNAS server which has done nothing to assist the problem in any way. Still cant find anything else in the system to even begin telling me where the problem may lie, like logs etc for that particular service.

Also I don't know how PC part picker can be bad when its quite literally the exact make, model of everything in there. I can understand you guys not wanting to click another link, but that statement seems useless and another one of those "Lets act like we're helping while kicking them when they're down".

This is what people hate about forums. I get it, I didn't follow some of the initial rules but now every single thing is left just picking that out rather than the problem. "Hey try this but in the future to make things easier for everyone including yourself, you need to make sure to do XYZ" instead every freaking response is something else that is not helpful.

 

[Ericloewe]

Not a single thing has been said to even remotely begin to help me find the culprit within the freenas system (assuming thats where it lies)...

I rebooted the CLIENT computer (Windows 10 Pro 64Bit Intel Core i7 32GB DDR4 RAM yada yada yada) multiple times. That was the machine that had the ethernet cable removed and placed back (not that it would matter, since the network is clearly functioning based on previous post).

If you've used windows 10 and have gone to map a network drive, the message is not "incredibly" vague. Perhaps you're unclear with it. Its quite simple though, if you goto your computer (called 'This PC') you can then click Computer and then Map Network Drive. Once you do that, you can browser or type in the network location. I chose to browse and type in manually. Browsing shows the server name and the share drive, however when I try to access it after being prompted for my credentials, it fails (when it originally succeeded when first used prior to this randomly stop working).

I also have restarted the SMB service on the FreeNAS server which has done nothing to assist the problem in any way. Still cant find anything else in the system to even begin telling me where the problem may lie, like logs etc for that particular service.

Also I don't know how PC part picker can be bad when its quite literally the exact make, model of everything in there. I can understand you guys not wanting to click another link, but that statement seems useless and another one of those "Lets act like we're helping while kicking them when they're down".

This is what people hate about forums. I get it, I didn't follow some of the initial rules but now every single thing is left just picking that out rather than the problem. "Hey try this but in the future to make things easier for everyone including yourself, you need to make sure to do XYZ" instead every freaking response is something else that is not helpful.

You're nitpicking one paragraph out of five, which have several very pertinent questions.

As for your problem, try to redo the share's permissions (follow the videos in the Resources section).

 

[nojohnny101]

Oh! I didn't even get from your first post that you unplugged the ethernet cable on your client machine NOT your FreeNAS box. That changes things quite a bit.

That's a bit odd behavior. See if you can find anything relevant in:
/var/log/samb4/log.*

Just trying to help. Everything said is in that mindset.

 

[Geoff Bricker]

Thanks, nojohnny101 for telling me where to find the log. I resolved the issue by going into my windows credentials management and wiping out the entries for this completely, and re-searching for it through network and re-adding it. It would appear that even though it could see info, it wasn't properly sending over credentials which means most like a windows cache or something error and not on the freenas side. Its all resolved.