Can no longer mount windows share via fstab mount -a

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
badams_ios
Level 2
Level 2
Posts: 71
Joined: Tue Jun 18, 2013 7:55 pm

Can no longer mount windows share via fstab mount -a

Post by badams_ios »

I had some drive corruption that I repaired but now a share on my windows nas server won't mount from fstab. It used to work just fine.

Here's the line from fstab, but of course nothing has changed in the fstab file.

//192.168.1.61/Man-CaveSync /media/syncovery cifs credentials=/home/cave-man/.smbcredentials,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dir_mode=0777 0 0

I can get to it just fine from browsing the network.

I get:
sudo mount -a
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Clewless

Lenovo ThinkServer
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
20 GB RAM
3 TB WD Black, hardware raid 5 - /home
Nvidia GeForce GT 220
32" TV
In the Man Cave :)


Mint Mate 17.1

Media Center, image and video editing

User avatar
austin.texas
Level 20
Level 20
Posts: 12048
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: Can no longer mount windows share via fstab mount -a

Post by austin.texas »

Maybe something here could help.
HowTo: Samba Browsing Problems Checklist
http://forums.linuxmint.com/viewtopic.p ... 46&start=0
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018

altair4
Level 19
Level 19
Posts: 9848
Joined: Tue Feb 03, 2009 10:27 am

Re: Can no longer mount windows share via fstab mount -a

Post by altair4 »

The only other thing I can think of doing is to run smbclient in diagnostic mode to see what's happening:

Code: Select all

smbclient -d3 -U altair //192.168.1.61/Man-CaveSync
Change "altair" to the user name that's expected on the server.
If it's successful you will end up with a prompt:
smb: \>
Just enter quit to end the connection.

If it's not successful you will end up with a rather large output but it may indicate something obvious like the ip address or share name changed ......
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

badams_ios
Level 2
Level 2
Posts: 71
Joined: Tue Jun 18, 2013 7:55 pm

Re: Can no longer mount windows share via fstab mount -a

Post by badams_ios »

Altair4, I get the following after running that diag:

Enter administrator's password:
Connecting to 192.168.1.61 at port 445
Doing spnego session setup (blob length=0)
server didn't supply a full spnego negprot
Got challenge flags:
Got NTLMSSP neg_flags=0x628a8215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60088215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60088215
Domain=[GENAS] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

If I ping the name of the server, genas, I get:
I get the desired results.

The NAS server is an old Windows home server, and the only user account is "administrator". ALL shares are set to everyone - full access.

When browsing the network I get inconsistent results. Some times it loads the shares with no problem, some times is shows no folders at all.

All my windows machines can access the server just fine.

It's only this machine and after fsck fixed a LOT of corruption.

Is there a . folder or config file under /Home that could have been removed when fsck fixed the issue?

Example: After fsck fixed the corruption, I had no panel/start menu ...etc. I had to delete the contents of /Home/.config
Clewless

Lenovo ThinkServer
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
20 GB RAM
3 TB WD Black, hardware raid 5 - /home
Nvidia GeForce GT 220
32" TV
In the Man Cave :)


Mint Mate 17.1

Media Center, image and video editing

altair4
Level 19
Level 19
Posts: 9848
Joined: Tue Feb 03, 2009 10:27 am

Re: Can no longer mount windows share via fstab mount -a

Post by altair4 »

A NT_STATUS_BAD_NETWORK_NAME error can mean that the share doesn't exist but more frequently it means the share doesn't exist for you.

In other words it's a permissions problem on the server. It's not that the server is rejecting your credentials it's that the user name you are passing has no permissions to access the folder being shared. I have no experience with Windows Server 2003 unfortunately.

I don't see how this could be an issue on the Linux client but being forced to remove $HOME/.config seems to have been an extreme measure.

Can you boot to the install DVD using it in a live session and try to access the server that way? If you can it would indicate that something is messed up with your install.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

badams_ios
Level 2
Level 2
Posts: 71
Joined: Tue Jun 18, 2013 7:55 pm

[SOLVED] Can no longer mount windows share via fstab mount -

Post by badams_ios »

Like I say... I can browse to it. All shares on that server are set to everyone full access. I created a new share and it works fine. I guess I'll mark it as solved, as I don't have time to keep playing with it.
Clewless

Lenovo ThinkServer
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
20 GB RAM
3 TB WD Black, hardware raid 5 - /home
Nvidia GeForce GT 220
32" TV
In the Man Cave :)


Mint Mate 17.1

Media Center, image and video editing

Post Reply

Return to “Hardware Support”