lan network issue

fluffybutt

fluffybutt

fluffybutt

Associate
Joined
14 Dec 2013
Posts
23
ok,
so ..
windows 10 pro, with ubiquity dream machine, virgin media v3 in modem mode 2 poe cctv, and 1 unraid server. various wifi plugs, laptops phones etc..
im asking for some help as i feel i have exhausted the "solutions" that have been offered to searching the issue.
i can see the unraid server, i can connect to the ui.
i can NOT access the shares on the win 10 pc..

i can connect to the shares via a laptop on wifi, and the ui.

im not 100% networking competent but have managed up until this time.
all firewalls were either turned off or uninstalled (kaspersky) to try any fixes given. im just at a point now where im getting nowhere.
like i said i have exhausted all the options i have found smb, netbios, etc .. it has to be something with my pc. if i do the network "repair" apparently my broadband modem is experiencing issues. even more confused.

any help will be gratefully received..
 
First of all can you ping the unraid server? and do you get a reply?
Secondly, how do you connect? e.g \\ip.address or \\hostname.local (example)
Thirdly have you got SMBV2 enabled on your file server? SMB1 is now blocked by default.

Try mapping the drive via command line "net use X: \\ip.address\share" (where X is the letter you want to assign the drive)

lets see what this comes back with first, there are more options/commands to net use but need to see above before going further.
 
I assume you've tried the suggestions in this post?

https://forums.unraid.net/topic/77442-cannot-connect-to-unraid-shares-from-windows-10/

If you can get to the Web UI form the same PC you can't access shares then I'd say it's definitely an SMB issue or inability to use guest logins or a a username/password mis-match if you are matching your Windows accounts with Unraid accounts. What error message do you get when you try and browse \\UnRaid.Server.IP in Windows Explorer.
 
This is definitely a Windows thing, welcome to SMB shares.

As above make sure you have SMBV2 enabled, make sure that network detection is turned on too.

Can you ping the device? Using cmd type ping <ip-address> and where IP address is, put in the IP of the unRAID server
 
good morning,
sorry for the late reply to you all..

i can ping the server,
C:\WINDOWS\system32>ping 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

trying to connect with \\192.168.1.10\media
OR \\DEATHSTAR\MEDIA
result in file not found

"net use X: \\ip.address\share" (where X is the letter you want to assign the drive)
results in
System error 2148073478 has occurred ..

i have already tried the above mentioned link and it is enabled


someone recommended this in smb

#unassigned_devices_start
#Unassigned devices share includes
include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end
#min protocol = SMB2

i CAN access the shares with no issues via wifi on a laptop. (the wifes laptop) just dont tell her ..

once again thanks for the advice, it is really appreciated ...
 
FeatureName : SMB1Protocol
DisplayName : SMB 1.0/CIFS File Sharing Support
Description : Support for the SMB 1.0/CIFS file sharing protocol and the Computer Browser protocol.
RestartRequired : Possible
State : Enabled
CustomProperties :
ServerComponent\Description : Support for the SMB 1.0/CIFS file sharing protocol and the Computer
Browser protocol.
ServerComponent\DisplayName : SMB 1.0/CIFS File Sharing Support
ServerComponent\Id : 487
ServerComponent\Type : Feature
ServerComponent\UniqueName : FS-SMB1
ServerComponent\Deploys\Update\Name : SMB1Protocol




PS C:\WINDOWS\system32> Get-SmbServerConfiguration | Select EnableSMB2Protocol

EnableSMB2Protocol
------------------
True


PS C:\WINDOWS\system32>




S C:\WINDOWS\system32> sc.exe qc lanmanworkstation
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: lanmanworkstation
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:\WINDOWS\System32\svchost.exe -k NetworkService -p
LOAD_ORDER_GROUP : NetworkProvider
TAG : 0
DISPLAY_NAME : Workstation
DEPENDENCIES : Bowser
: MRxSmb20
: NSI
SERVICE_START_NAME : NT AUTHORITY\NetworkService
PS C:\WINDOWS\system32>



so it looks like everything IS correct as of that link .. and no removing the # made no difference to the above results

so stressful
thank you for your time and help
 
do you see any shares if you browse the server? i.e. \\192.168.1.10 or \\servernamehere

If you're trying to access SMB1 share on Windows10 then that may be your problem. Windows10 is depreciating SMB1, even though the option is still there in the features list, they tend to stealth nuke it regularly requiring the option to be turned off, reboot and turned back on. It's been extremely hit and miss over the last few months in my experience trying to access some legacy devices, but SMB1 should've been removed a long time ago because of it's various security flaws.

Make sure your server is running SMB2 or above and you should have a much better time of it.
 
Just for testing...

Have you tried booting into safe mode with networking?

If you share a folder on your wife's laptop can you access it?

Do you have a spare HDD of any sort? If you have, stick a clean copy of Win10 onto it and see if you can connect from that.
 
Check that the network on your PC isn't tagged as public, needs to be home or work. Otherwise Windows firewall will block SMB.
 
good morning all ...
so replied in order of questions above...

tried safe mode with networking, unable to see anything ..

will try the share from the laptop today..

trying to free up some space on 1 to try..

and network is private..

had to change this "min protocol = SMB2" this morning as the tv could no longer locate the media files ...
why oh why is it so damn difficult to just do one thing ...
thanks again .. all your help is appreciated
 
Try this in regedit;

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth to 1 instead of 0.

This fixed the issue on 2 of my Win 10 PCs running LTSC not able to see shared drives.
 
One issue I had with connecting to my NAS recently is I changed the credentials but windows was still using my old login. I had to go in to the 'credential manager' in windows 10 and delete the entry. Reboot, then reconnect to the NAS. Might be worth a try.

Type 'Credential Manager' in to windows start bar and it will appear. When it opens up, click on 'Windows Credentials' and then look for the credentials that connect to your server and click 'remove'.
 
Have you tired flushing your dns?
Ipconfig /flushdns

or clear tour arp cache

needs admin priv cmd

ARP -d *
 
You must log in or register to reply here.
Back
Top Bottom