Good Morning,
I am running OpenSuse 13.1 XFCE Desktop. I am trying to connect to Network share that has been accessible to any Windows/Linux box that i have installed. I have been spending some tine doing some Google searches to resolve the issue.
smb.conf is the main Samba configuration file. You find a full commented
version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
samba-doc package is installed.
[global]
workgroup = HOME
name resolve order = bcast host lmhosts wins
netbios name = linux-7ed5
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
usershare allow guests = Yes
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
First, although your post seems reasonably clear to me, it’s proper form to post data in “CODE” tags (the hash button in your text editor if you’re using the Forums web client).
I’m sure you need to provide more concrete information about your problem, eg
What command and/or app client are you using to connect to your Network Share?
What was the response if you weren’t successful (post exact error returned)?
Some other minor things I notice in your smb.conf
You list bcasts first in order of name resolution. Although it’s possible to do this, most Admins list it last to minimize noise on the network.
Don’t know if I’m reading this right, but you might be permitting guests to connect when it looks like you are serving Users’ Home directories?
Whoops. I was trying to include most things…
The share is basically a HD on a NIC. Been using it forever it seems. This is the first time I have had an issue connecting to it No real “home user directories”. The workgroup is called home.
If I open the file manager and type smb://192.168.1.80/Hdd_a, I get Failed to open"File System". Failed to mount Windows Share: Connection timed out.
File Manager - Super User and Dolphin:
smb://192.168.1.80/hdd_a
Timeout on server 192.168.1.80
On 4/19/2014 9:16 PM, deano ferrari wrote:
>
> wliporace;2638028 Wrote:
>> Yes I can ping the device. I can even browse to the web interface. I
>> have a Linux Mint 15 box that I can get to it from.
> What response does the following give?
>
> Code:
> --------------------
> smbclient -L 192.168.1.80 -N
> --------------------
>
>
Wilporace;
In addition to above make sure that Samba Server, Netbios server and Samba client are all allowed services through the
firewall:
YaST>Security and Users>Firewall>Allowed Services
Make sure smb and nmb are both started:
systemctl status smb.service
systemctl status nmb.service
( I suppose you do not really need smb for just the client, but you indicate shares in your smb.conf and need smb for
those.)
If these two services are not started then you can start them with:
su -
systemctl start smb.service
systemctl start nmb.service
exit
To mount a cifs share you will need the full mount command. See: http://swerdna.dyndns.org/susesambacifs.html
for a good explanation. ( This site is often down so if you cannot reach it post back here.)
ping 192.168.1.80
PING 192.168.1.80 (192.168.1.80) 56(84) bytes of data.
64 bytes from 192.168.1.80: icmp_seq=1 ttl=64 time=1.49 ms
64 bytes from 192.168.1.80: icmp_seq=2 ttl=64 time=0.258 ms
64 bytes from 192.168.1.80: icmp_seq=3 ttl=64 time=0.260 ms
64 bytes from 192.168.1.80: icmp_seq=4 ttl=64 time=0.263 ms
64 bytes from 192.168.1.80: icmp_seq=5 ttl=64 time=0.276 ms
64 bytes from 192.168.1.80: icmp_seq=6 ttl=64 time=0.266 ms
--- 192.168.1.80 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5001ms
I currently have the firewall disabled and I have the services enabled. I finally figured out that I needed to create a mount point on my PC. /mnt/hdd_a then issue the command:
sudo mount -t cifs -o guest //192.168.1.80/hdd_a /mnt/hdd_a
This allowed me to mount the directory. My other question then becomes, Why can’t I just browse to the area like I have always done? Why do I have to mount it to see it?
From what I’ve seen, you can mount manually (the method you’re using) or Desktops seem to have the ability to dynamically discover and mount using some other method and using a supported protocol (eg smb, ftp, http, etc). The requirements to browse network resources are strict… You need to be a member of the same workgroup or domain to “see” resources, and you need appropriate permissions to access (and maybe see) the resource.
When you talk about browsing network resources (typically network shares), you can test using a web browser because browsers today typically understand all most used protocols and often return usable error messages. You can also test using a command line tool like curl (there are others (deano suggested one).
Also, if you’re not running a domain, a workgroup can suffer anomalies, especially for a machine first booting up into the network when it somehow doesn’t know which machine in the workgroup is the browse master.
Good Morning,
Sorry for the slow reply! Week has had me swamped already!
I understand Workgroups and Domains. Work has me in the Windows world! I used to be more in the NetWare world. Linux is where I enjoy learning. I am definitely learning Linux. I do have my PC paert of the same workgroup, but can’t browe.
I have the same issue browsing with a browser. I have seen on a couple of other sites, that something has changed. Just browsing to general shares worked. Now it no longer happens. An open share should be visible. Maybe I am missing something, but I am curious on why things changed.
I have the same issue browsing with a browser. I have seen on a couple of other sites, that something has changed. Just browsing to general shares worked. Now it no longer happens. An open share should be visible. Maybe I am missing something, but I am curious on why things changed.
I have to connect to remote windows shares from time to time. I only ever use Dolphin to do this (using kio-smb). It works without issue, (and handles the authentication as well.) Not clear to me what is failing for you.
What the heck is kio-smb?? When I look for it, I don’t see it as a package. I am not running KDE desktop, I am running XFCE for my desktop. So it is not available?
I guess I have missed a couple of things. So here they are:
If I understood your earlier posts, you mentioned that this relates to a NAS device?
A quick google of ‘Conversion error: Incomplete multibyte sequence()protocol negotiation failed: NT_STATUS_INVALID_PARAMETER’ leads me to wonder if you’re impacted by the bug reported here
Well, you could try setting the ‘client max protocol’ to force the highest protocol that will be used by the client. Refer to ‘man smb.conf’ for more details.
FWIW, here’s a blog reporting similar behaviour with OS X:
