Had some network issues yesterday that resulted in a bad network card. I switched over to the on-board network port and everything seems to be working fine except I cannot access any of my shares. Every time I try to open or browse to a share it asks for credentials but does not accept any username or password I give it. I've tried browsing by name and IP and neither works, tried resetting passwords, tried different machines, ran the new permissions tools, rebooted and nothing seems to allow me to access the shares. I also made sure that the unRAID server is on the same workgroup as the PCs, is set to the SMB master and the user credentials match the server. I did run the update to 6.2 at some point yesterday so I'm not sure if that might have caused the issue but I doubt it. I've had this issue in the past and usually running the new permissions tool and a reboot will fix it but this time seems not so much.

 

I did also install and run the Fix Common Problems tool but it found no permissions issues.

 

Any help or direction on troubleshooting this problem would be greatly appreciated.

 

Thank you

 

(Sys Log, Diag Logs and Plugins Screenshot included below)

tower-syslog-20160921-1237.zip

tower-diagnostics-20160921-1236.zip

tower-diagnostics-20160921-1026.zip

Still having problems connecting to the shares. Anybody out there willing to help me out here? Thanks.

It is probably because you changed NICs.  There are possibly two ways to correct this:

 

1) Boot your server in the gui mode and go to Settings->Network Settings and make adjustments and save them.

2) Delete the /flash/config/network.cfg file and restart the server.  You should then be able to access the gui and make network settings from the default values.

@dlandon thank you for replying.

 

I'm not sure what settings need to be changed. The server is currently online on the network ie. I can ping it and get to the gui. The network settings page shows two available ethernet ports one of which is configured and one of which is not. I changed no settings after the NIC switch, I just assumed that unRAID picked up the switch and propagated the settings on the new NIC after the reboot.

 

Should I disable the current ethernet port in unRAID (eth0) and enable eth1 and configure it?

 

Also I forgot to mention that I tested a third machine last night and was able to access the shares from it after putting in my unRAID user credentials but still unable to access the shares from my Win10 VM on unRAID or the other machine I tested yesterday.

It looks like you are saying that a Windows 10 VM is not able to access the shares.  If that is correct, check the VM setup and be sure to use br0 for the network bridge.

 

If other computers on the network cannot access the shares, try to remove any unRAID credentials from the Windows computer and then reboot the computer.

The VM is on the br0 bridge and is able to communicate on the network. I've also tried removing the credentials and rebooting both machines that will not connect to the shares.

 

I notice that in the dashboard that the network details shows eth0 1000 Mb/s, full duplex, mtu 1500 which I'm pretty certain that it's a 10/100 port which is the reason I got the separate network card in the first place. Not sure if this is relevant or not. I did order another NIC to replace the bad one which should be here tomorrow but I feel like that probably won't fix this issue as everything else seems to be working fine and I was able to access shares from one laptop on the network.

 

I saw another topic on the forum where a user had issues with the NIC after the upgarde to 6.2 (https://lime-technology.com/forum/index.php?topic=52079.0) doubt it's related since is server hardware vs desktop hardware but I thought I'd point it out either way.

 

Anything else I can try while I wait for the replacement NIC?

After doing some more research I believe this is an issue between the latest Windows 10 update and the unRAID 6.2 update. Last night the one laptop I had that would still allow me to connect to the shares over the network installed the latest updates for Win10 and after the install and reboot I'm having the same issue connecting to the unRAID shares as my unRAID Win10 vm.

 

So I'm not sure how to proceed from here. I guess I could just uninstall the Win10 updates and see if that fixes this issue or maybe there is a way to roll back the unRAID 6.2 update. Can somebody help me out here? How should I go about resolving this issue? At this time I have no way to access the shares on my server.

If your shares are public try a random username without any password, e.g., user

All shares are currently set to public. Tried "user" no password same outcome with both name and IP. Even tired from command line net use.

Can somebody please help me out here. This has been going on for 3 days now. I've been reading on the forums and troubleshooting on my own and I'm not able to figure this out. I've tried all the basic and obvious stuff. Could really use some assistance on this problem.

I think this is usually a Windows problem (if I skimmed through this right).  Are you absolutely sure you removed the credentials, using the Windows Credential manager?  Then immediately tried to access the share using the correct user and password?

@RobJ I'm pretty sure. See attachment for verification.

Was able to get an Ubuntu VM to connect to the server using the root user and password but it rejects all the other unRAID user name passwords I try to authenticate with. Still unable to access the server from a Windows machine.

So I guess my only course of action left is to go with the LimeTech support service. I've pretty much exhausted all my efforts to troubleshoot this issue and nothing has resolved it. Anybody know if the LT support option is worth it? I'm pretty much out of options so I don't know what else to do hopefully they can fix it.

Was able to solve this issue by removing unmenu and it's packages (http://lime-technology.com/forum/index.php?topic=11764.0), removing all plugins and rebooting the server. After the reboot I was able to access all shares without an issue. I haven't started adding plugins back one by one to see which one was causing the issue yet.