I've tried everything I can think of to get Samba working on my 11.0 server (built fresh, on a new empty hard drive). It's serving folders and files okay, but I can't get any users working, including Administrator, so there's no way the Windows machines (or even my Linux workstation) can be joined to my domain, of which this smb server is the PDC. And trying to use one of the smb printers from a Windows machine just results in a permissions problem. My Linux books, if they talk about Samba at all, simply show how to set up the server in YaST. That doesn't help, because everything there looks right. Except that every time I run the Samba server module, it asks me again for an Administrator/root password -- it doesn't seem to be able to create the user account, although no error is reported. I think I could probably get things sorted out using SWAT, but when I try to connect to localhost:901 no connection is possible. Firefox tells me that the site appears to be valid, but but it won't accept a connection. Has anyone else been down this road with 11.0? Things were working great in 10.3, but I really don't want to "upgrade" to that version again, if there's a simpler answer. (Of course, when I upgraded to 11.0 I should have saved a copy of samba.conf, but it's too late for that now.) Surely Samba is an important enough component of a server that it hasn't been overlooked in the move to 11.0. Right? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2008-07-05 at 16:01 -0700, Jerry Houston wrote:
I've tried everything I can think of to get Samba working on my 11.0 server (built fresh, on a new empty hard drive).
It's serving folders and files okay, but I can't get any users working, including Administrator, so there's no way the Windows machines (or even my Linux workstation) can be joined to my domain, of which this smb server is the PDC. And trying to use one of the smb printers from a Windows machine just results in a permissions problem.
My Linux books, if they talk about Samba at all, simply show how to set up the server in YaST. That doesn't help, because everything there looks right. Except that every time I run the Samba server module, it asks me again for an Administrator/root password -- it doesn't seem to be able to create the user account, although no error is reported.
I think I could probably get things sorted out using SWAT, but when I try to connect to localhost:901 no connection is possible. Firefox tells me that the site appears to be valid, but but it won't accept a connection.
Has anyone else been down this road with 11.0? Things were working great in 10.3, but I really don't want to "upgrade" to that version again, if there's a simpler answer. (Of course, when I upgraded to 11.0 I should have saved a copy of samba.conf, but it's too late for that now.)
Surely Samba is an important enough component of a server that it hasn't been overlooked in the move to 11.0. Right?
Make sure the service is allowed in the yast2 firewall. also, don't forget smbpasswd -a username to add the user to samba. Bites me in the ass all the time. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2008-07-05 at 16:01 -0700, Jerry Houston wrote: Also in /etc/xinet.d make sure swat says disabled=no and if you want to access from other than local, add to the ipaddress.
Michael S. Dunsavage
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael S. Dunsavage wrote:
On Sat, 2008-07-05 at 16:01 -0700, Jerry Houston wrote:
Also in /etc/xinet.d make sure swat says disabled=no and if you want to access from other than local, add to the ipaddress.
Michael S. Dunsavage
There were problems using the swat interface in the version shipped with SuSE 11.0. The configuration screens were blank. Configuration files used in SuSE 10.3 were copied into /etc/samba to get 11.0 working. On an email else where on this list a suggestion was made to download the version of samba maintained under the build or similar service. On updating from that repository ( http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11... )and re-starting the samba service, swat picked up the settings in the configuration files correctly. Presumably, other bugs have been taken care of as well. Sudhir -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sudhir wrote:
There were problems using the swat interface in the version shipped with SuSE 11.0. The configuration screens were blank. Configuration files used in SuSE 10.3 were copied into /etc/samba to get 11.0 working. On an email else where on this list a suggestion was made to download the version of samba maintained under the build or similar service. On updating from that repository ( http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11... )and re-starting the samba service, swat picked up the settings in the configuration files correctly. Presumably, other bugs have been taken care of as well.
Sudhir
I appreciate the advice, thanks. I updated samba from there, and restarted the server, but still no SWAT. Perhaps other things were fixed that will improve my experience with it, but so far, no joy. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2008-07-05 at 18:32 -0700, Jerry Houston wrote:
Sudhir wrote:
There were problems using the swat interface in the version shipped with SuSE 11.0. The configuration screens were blank. Configuration files used in SuSE 10.3 were copied into /etc/samba to get 11.0 working. On an email else where on this list a suggestion was made to download the version of samba maintained under the build or similar service. On updating from that repository ( http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11... )and re-starting the samba service, swat picked up the settings in the configuration files correctly. Presumably, other bugs have been taken care of as well.
Sudhir
I appreciate the advice, thanks. I updated samba from there, and restarted the server, but still no SWAT. Perhaps other things were fixed that will improve my experience with it, but so far, no joy.
I had to get to swat through webmin did you check xinet.d? and once you changed those settings did you do service xinet restart then you can do http://localhost:901 -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Jul 5, 2008 at 6:32 PM, Jerry Houston
I updated samba from there, and restarted the server, but still no SWAT.
Swat does not necessarily start with samba. Swat start is dependent on xinetd. See yast, and make sure its started. -- ----------JSA--------- "Ubuntu" is an African word meaning "Suse is too hard for me". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
<snip>
I appreciate the advice, thanks. I updated samba from there, and restarted the server, but still no SWAT. Perhaps other things were fixed that will improve my experience with it, but so far, no joy.
Have you enabled swat service? Navigate to Yast -> Network Services -> Network Services (xinetd). Under the "service" column, select "swat". If the "status" is off, press the "toggle status" button to change it to "on". Click on finish. From the command prompt as root run the command "rcxinetd restart". Open a browser and point to "http://localhost:901". In KDE4, typing this in dolphin file manager does not work. Use Konqueror or Firebird instead. For the last ten years or so, following this procedure has worked. Regards. Sudhir -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jul 06, 2008 at 02:00:50AM +0100, Sudhir wrote: [ 8< ]
There were problems using the swat interface in the version shipped with SuSE 11.0. The configuration screens were blank. Configuration files used in SuSE 10.3 were copied into /etc/samba to get 11.0 working. On an email else where on this list a suggestion was made to download the version of samba maintained under the build or similar service. On updating from that repository ( http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11... )and re-starting the samba service, swat picked up the settings in the configuration files correctly. Presumably, other bugs have been taken care of as well.
A lot. Samba of openSUSE 11.0 from the final media is 3.2.0 release candidate 1. Even if RPM reports 3.2.0 this is a build hack to make updates work on the RPM level. The final 3.2.0 will be available as an online update later. It's possible to follow the development in the TESTING repo as described in the openSUSE wiki at http://en.openSUSE.org/Samba article. Soon the code available there will be ahead of STABLE again. Samba developer quote of this sunday: My life is driven by bugzilla. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (6)
-
Jerry Houston -
Jerry Houston
-
John Andersen -
Lars Müller -
Michael S. Dunsavage -
Sudhir