Menu

Can't browse domain

Help
Koenraad
2014-03-28
2014-03-28
  • Koenraad

    Koenraad - 2014-03-28

    Hi,

    I'm in the process of migrating my laptop from Opensuse 12.2 to Opensuse
    13.1.
    On Opensuse 12.2 I used smb4k 1.0.2 to connect to our company's
    windows-domain. No problems I can't live with.

    On Opensuse 13.1 I can't do anything. I set up smb4k to listen to the
    current master browser. That is a samba3 domain controller. When I start
    smb4k, it sees the domain-name and I am asked to enter a user and
    password (Please enter a username and password for the host). Why ?

    When I press escape and then click on the domain-name, this disappears.

    When I enter a user and password (my domain-user and password) there is
    a new request for a user and password, etc. I did enter those user and
    passwords about ten times in a row, without effect. What's going on ?
    What user and password is this supposed to be ?

    I tried to give a wrong password, and after 3 times the user should be
    disabled. But this does not happen. So it seems those user/password are
    not for the domain-controller.

    I am using smb4k 1.0.8, but first tried with 1.0.9.

    Where are the settings stored ? In opensuse 12.2 this was in
    ~/.kde/share/apps/smb4k so after some tries I copied these old settings
    (bookmarks.xml and custom_setting.xml) to ~/.kde4/share/apps/smb4k,
    which existed.
    But when I delete those files and modify some settings and exit smb4k,
    there are no new files. But the settings are saved somehow.

    Is there any way to debug things like log-files or something ?

    Koenraad

     
  • Alexander Reinholdt

    Beforehand I have to say that I could never test Smb4K in a real Windows domain, so it might fail there. However, if Opensuse 12.2 worked for you and 13.1 does not, I suspect that maybe some settings in Opensuse (like firewall, etc.) or Samba have to be adjusted... Is the firewall running? If so, try switching it off temporarily. Does the issue persist? If not, have a look here for a possible solution. Are the Samba settings the same? If not, please copy your old smb.conf over.

    If it should turn out that the problem is connected with Smb4K itself, I can produce a special version of Smb4K for you that writes debug info to the shell. This could then be inspected for potential causes of the problem. Normally, Smb4K does not produce any log files or debug output.

     

    Last edit: Alexander Reinholdt 2014-03-28

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.