You are not logged in.
Hello everyone!
I've been using arch for about 3 months and, apart a few glitchs I'm very satisfied with it.
I have three machines running arch in my home, two desktops and a notebook, and I want to share files between then.
The general idea is that the desktops and cable modem are connected by wires to a wireless router.
I've choose SAMBA as the network protocol because eventually a windows machine might need access to the files (either a friends notebook, or one of the desktops running windows for gaming).
I've followed the instructions and installed samba on all the machines, and initially, everything worked exactly as I wanted.
After the first reboot, I've started to have some problems that I seem to be unable to resolve:
When trying to connect to the servers browsing in nautilus ou dolphin (I have machines running, KDE, Gnome and Kdemod, and the problem is the same for all), i cant enter the "workgroup" group... See, I can type the name of the server and bypass the group, entering directly in the machine, and everything works... But when trying to enter the "domain" my access is denyed.
I've tried to reboot the machines, in different orders, I've tried to configure one of them as "Primary Domain Controller" following these instructions: http://samba.netfirms.com/PDC.htm but the problem persists.
Also, on a sidenote, samba seems to not start correctly (despite the daemon beeing in rc.conf), I usually have to use "sudo /etc/rc.d/samba restart" after boot to make sure it's working.
As I seldom reboot the server, its just a small nuisance. But making my "non-technical" wife, family and friend type the server names has been a problem.
Thanks for any help.
Last edited by Raws (2009-11-19 20:04:45)
Offline
Same problem here... I can still access the computers by entering their names, but cannot view the machine listing in workgroup. I'm asked for an username and a password, but my domain user doesn't seem to work. That's annoying.
In love I believe and in Linux I trust
Offline
I have had the same problem. Do you also use the default "user" security mode?
In order to solve this, I have logged in to the server, erased contents of '/etc/samba/private/smbpasswd' since I had only one user in it (do at your own risk, though).
And I have added the user using
smbpasswd -a <username>
Strangely enough, '/etc/samba/private/smbpasswd' remained empty, but the problem disappeared.
Last edited by Bubla (2009-11-10 13:41:27)
Offline
See this thread:
http://bbs.archlinux.org/viewtopic.php? … 42#p653242
Matt
"It is very difficult to educate the educated."
Offline
Hi!
This tip didn't work for me.
As root I've removed /etc/samba/private/passwd.tdb and smbpasswd in both desktops.
Then, as my regular user in the machines, I've used "sudo smbpasswd -a" to add the users, one by one... (I've received a message that the file passdb.tdb had been updated when I was adding the first user)
After that, I've used "sudo /etc/rc.d/samba restart" on both desktops.
When trying to access the domain as regular user I keep receiving messages to login as user/password, but my password is not accepted and I end up with a message "denyed access to workgroup".
Any new Ideas?
f the text of the files and logs is necessary I would like, please, that someone put a link to the instructions to paste them in the forum as I never did that.
By the way... thanks a lot for the help so far.
Offline
Also,
yes, I'm using "user" security mode, and my user is allowed on the shares in the respective machines.... But I dont know where would be the place to put the user as allowed to go to the domain, or if this place do exist.
I've looked in the thread http://bbs.archlinux.org/viewtopic.php? … 42#p653242 but it does simply explain the procedure that i've already done (except, of course, if I missed something).
Thanks again
Offline
I am using "share" security mode and I didn't created any users for samba. So how am I supposed to solve this?
Offline
With two other distros the problems seem not to happen.. On Arch I'm still asked for a password to see the domain members. And no, it does not work to just provide my SMB user + password. Is there a chance to be a compatibility issue between dolphin/newer Samba or newer Samba/older Samba?
In love I believe and in Linux I trust
Offline
It's doesn't appear to be caused by dolphin or samba. I have this problem on my laptop with nautilus and don't have dolphin or samba installed. I beleive the recent smbclient update is causing this.
Edit: I just verified this by downgrading smbclient to 3.3.8-1. Now nautilus works properly.
Last edited by kakalaky (2009-11-11 00:33:56)
Offline
Well, when I said samba I was referring to the part of samba that's used by dolphin to access the shares. So yes, smbclient would have been more proper.
In love I believe and in Linux I trust
Offline
I had the same problem after latest samba updates to my server.
I tried to remove username that listed in /etc/samba/private/smbpasswd with smbpasswd -x username
it did'nt work and then i just added same username and password. smbpasswd -a username and it worked.
It seems that default passwd file has changed from /etc/samba/private/smbpasswd
to /etc/samba/private/passdb.tdb you have to readd users.
Last edited by decaturguy (2009-11-12 15:59:41)
Offline
That can't be all there is to this. The server I'm connecting to isn't running Arch and hasn't had any samba updates applied since this problem started. My Arch client can't browse the workgroup using smbclient 3.4.3-2 but can using smbclient 3.3.8-1. Every other distro I've tried (and windows) can browse the workgroup.
Offline
Kakalaky has a very good point. Every other system is seeing the workgroup machines. Only my Arch machine has become overly secure and asks for a password before even entering a machine or another.
Last edited by ckristi (2009-11-13 08:39:12)
In love I believe and in Linux I trust
Offline
In my case, as I've pointed before, I've already deleted and readded all users, and the problem persists...
Offline
To be clear, the problem I am having is that dolphin asks for a user name and password when I try to browse the workgroup "WORKGROUP" on my home network. No matter what I enter, I am continuously prompted for a username/password. If I click cancel, I am denied access. The server is using user type security.
I am using KDE 4.3.3-1 from the Arch repos (not KDEmod).
samba is at version 3.4.3-2 on the server and client.
smbclient is at version 3.4.3-2 on server and client.
On my server:
Stop SAMBA
Delete everything in /etc/samba and /etc/samba/private except smb.conf
Delete everything in /var/cache/samba
Run smbpasswd -a dmartins and enter the same password as my user account on the server.
Start SAMBA
The problem still exists.
On the client:
SAMBA is not running.
Created a smb.conf file
[global]
workgroup = WORKGROUP
netbios name = sirschmoopy
security = user OR share (neither works)
Add the same user as above using smbpasswd -a
Start SAMBA
It still prompts for a password and eventually denies access. Any idea how to get some verbose output from dolphin to a log file or terminal?
Offline
That is exactly my problem. The only difference is that I use three machines with three different DEs (gnome, KDE and KDEMod) so I'm prety sure this is not DE related.
And I have the same problem with nautilus too.
If there is any additional info about my systems that could be useful, please, point it out.
Thanks for any help
Offline
Yep, same problem if you use smbclient from console. It asks for password and denies access to seeing the workgroup machines. I do not remember the exact command syntax, and I don't have ATM a Linux machine near me.
In love I believe and in Linux I trust
Offline
Samaba server is running on an Arch install and the shares could be accessed from a windows PC and from a ubuntu install with due credential (sambapassword file removed from /etc/samba/private folder) . The share could not be accessed thro' the net work option in nautilus on another arch install. still the share can be reached using File->connect to server option in nautilus. In other machines with Arch /open box / pcmanfm I use a script to mount the share using mount.cifs. This is for the records.
Last edited by kgas (2009-11-16 15:56:58)
Offline
I've got exactly the same issue, I've managed to dill with it, just like kgas said, by adding to my places (GNOME) a tab with my server, this option is available when you choose "connect to a server" in nautilus. I think that's the only reasonable solution for now, we'll have to wait for some update (I'm not sure what exactly is causing this bug).
On MacOS and XP everything works great with the same samba server.
Offline
Okay, well it definately sounds like the problem is on the client side.
I see the following errors in /var/log/samba/log.nmdb on the server and am wondering if they are related to the problem. 192.168.48.100 is the IP of the Arch client I am having problems with.
[2009/11/15 21:13:12, 1] nmbd/nmbd_incomingrequests.c:327(process_node_status_request)
process_node_status_request: status request for name WORKGROUP<20> from IP 192.168.48.100 on subnet UNICAST_SUBNET - name not found.
[2009/11/15 21:13:14, 1] nmbd/nmbd_incomingrequests.c:327(process_node_status_request)
process_node_status_request: status request for name WORKGROUP<20> from IP 192.168.48.100 on subnet UNICAST_SUBNET - name not found.
Anyone else seeing similar errors?
Offline
dmartins, I noticed the similar error but I could not find a fruitful solution from a search yet. As the shares can still be accessed I can wait for the bug fixes from the back end.
Offline
Same here. It's a bit of a nuisance as I'm unable to browse the windows network at all, no way to mount anything.
Offline
I am getting exactly the same error, however smb4k seems to work okay here. perhaps kde/dolphin has issues with the new libsmb? only speculation though.
Offline
Its a bug with samba 3.4.3 https://bugzilla.samba.org/show_bug.cgi?id=6880 , there is already a patch that solves the problem too.
Last edited by codestation (2009-11-18 05:02:32)
Offline
codestation, thank you! I had a look on the samba bugtracker today but didn't come up with anything. I will look at creating a PKGBUILD to include that patch.
Offline