[kio] [Bug 337310] New: Dolphin/Krusdaer/Konqueror can't connect to samba shares: internal error

[roger_email2 at yahoo.co.uk]

https://bugs.kde.org/show_bug.cgi?id=337310

            Bug ID: 337310
           Summary: Dolphin/Krusdaer/Konqueror can't connect to samba
                    shares: internal error
    Classification: Unclassified
           Product: kio
           Version: unspecified
          Platform: openSUSE RPMs
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: smb
          Assignee: unassigned-bugs at kde.org
          Reporter: roger_email2 at yahoo.co.uk

OpenSUSE 13.01 
Computer: 32 bit
2 network cards: 1 for IP based Windows network (samba) bound to a fixed IP 1
for dedicated DHCP internet connection
Samba server?: No, client of windows IP network

No matter what GUI interface I use samba never connects to a windows IP network
first time and if I can get it to work never for more than one session.

Usual method of making it work is to stop/start the smb/nmb services
Go into the Firewall and delete the port settings (TCP: 137 138 UDP: 139 445),
save the settings go back in then edit the settings and put the port settings
back then stop/restart the smb/nmb services.

Previously that somehow made it work, however now that doesn't work I just keep
getting the same error message:
"internal error  please send a full bug report to http://bugs.kde.org"

Which isn't exactly descriptive..

Also noticed under var/log/messages in the yaST control centre this:
"2014-07-10T10:43:15.118754+01:00 linux-ztl5 smbd[16678]:   STATUS=daemon
'smbd' finished starting up and ready to serve connectionsFailed to delete
pidfile /run/samba/smbd.pid. Error was No such file or directory"

Looking in the log.smdb has this strange recording:

"  WARNING: no network interfaces found
[2014/07/09 07:49:50.420804,  0] ../lib/util/become_daemon.c:136(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve
connectionsopen_sockets_smbd: No sockets available to bind to."

This doesn't explain why since I installed SUSE months ago deleting  the ports
in the Firewall then putting them back in would make it work now suddenly its
dead.

Tried having the network connection automatically and manually connect and the
smb and nmb service started manually - no change. Have set the smb.conf to
point to the actual network card in case the second network card (which is
internet only DHCP) was being used. again intermittent and certainly no define
procedure for making it work per session just random changing and restoring of
settings and stopping/restarting the smb and nmb process and after 10 minutes
mindless faffing it will suddenly work even though technically nothing has
actually changed.


Reproducible: Always

Steps to Reproduce:
1.Open any GUI file manager or internet browser and try to connect to the samba
network
2.Type in an IP address of an existing Windows computer
3.
Actual Results:  
Error message:

"internal error  please send a full bug report to http://bugs.kde.org"

Expected Results:  
Should let me see the 50 computers on the Windows network, or at the very least
produce a non ambiguous error message this is Linux not Windows after all :)

I had issues with samba under Gnome in Ubuntu from 10.10 to 14.10 would see
only some of the computers on the network and after 10-15 minutes would
randomly show some more and hide others...

The best part was connecting the second network card to the internet, this
caused samba to lose connection with the IP network on the first card same
worked on laptops turn on the wifi samba loses IP network..

-- 
You are receiving this mail because:
You are the assignee for the bug.