Announcement

Collapse
No announcement yet.

Can no longer access windows network in v7.10

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Re: Can no longer access windows network in v7.10

    Well in the smb.config you posted I saw this after closer reading:
    [CMF]
    path = /home/cmf
    read only = No
    guest ok = Yes
    I assume this is your share.
    So it should read something like this:

    [cmf]
    path = /home/cmf
    read only = no
    guest ok = yes
    case sensitive = no
    strict locking = no
    force user = cmf
    HP Pavilion dv6 core i7 (Main)
    4 GB Ram
    Kubuntu 18.10

    Comment


      #17
      Re: Can no longer access windows network in v7.10

      Well, I tried that, but not joy. The Windows machines give me a "connect to" dialog with username and password fields, but I cannot satisfy them.

      Comment


        #18
        Re: Can no longer access windows network in v7.10

        This may not apply to you, but one obscure problem I once had connecting with samba to older windows machines was the need for a short (8 character, I believe) password set on the windows shares.

        Have you tried connecting to a temp shared folder on the windows machine with no password set?

        Comment


          #19
          Re: Can no longer access windows network in v7.10

          Originally posted by CentaurHauler
          Well, I tried that, but not joy. The Windows machines give me a "connect to" dialog with username and password fields, but I cannot satisfy them.
          Try adding this line after the "interfaces" line:

          map to guest = bad user

          Comment


            #20
            Re: Can no longer access windows network in v7.10

            Well, still no improvement - I can see the machines, but cannot access them, and I cannot see anything from my Kubuntu machines.

            If someone has a working mixed Windows and Kubuntu 7.10 network (workgroup-based), could you post the complete smb.conf? Feel free to change usernames, etc. I would much appreciate it!

            Comment


              #21
              Re: Can no longer access windows network in v7.10

              I have a mixed network and will try to post you the samba conf file.

              But you haven't answeres my question.....

              Have you tried turning off the share password on a specific windows folder. In other words sharing it openly.

              If you can then write to that folder we have an indicator of where to further troubleshoot your problem.

              Comment


                #22
                Re: Can no longer access windows network in v7.10

                Sorry, I forgot to answer that - I have no share passwords on any of my Windows machines

                Comment


                  #23
                  Re: Can no longer access windows network in v7.10

                  Centaur-Hauler,

                  I've sent you the smb.conf file via PM.

                  This does seem like a Win security issue however, not so much a Kubuntu configuration issue..

                  Do your Windows machines use Msoft's auto-update feature?

                  Maybe some of your issue is not what changes were made to Kubuntu, but what changes were made (coincidentally in time) to your Win machines by auto-update.

                  A possibility?

                  Comment


                    #24
                    Re: Can no longer access windows network in v7.10

                    Can you describe exactly what you see when you get the password challenge, how is it worded and exactly what are your steps to reach that point (click by click).

                    Comment


                      #25
                      Re: Can no longer access windows network in v7.10

                      Gilf - thanks for the file. It doesn't look like you use a workgroup?

                      I can't send you the exact text right now, because I've been messing around with the WINS settings, as well as other changes suggested in this thread, and now I can't even see the machines at all.

                      This dialog is quite simple though, with the title "Connect TO" IIRC, and and place for username and password. I got it after browsing to the workgroup, and then clicking on the machine name. After giving the correct username and password, the dialog just keeps popping back up.

                      Anyway, I never let my machines auto-update (it does not seem like a "Genuine Advantage" to me!), and it has been many months since I did any manual ones.

                      It may be a security setting thing, at least in one direction - but I can still access my 7.04 file server just fine.

                      Your smb.conf file is pretty simple, and maybe I should try eliminating some of the stuff I've got in mine. I did delete the smb.conf files at one point and uninstall samba, so as to have it regenerate the file fresh.

                      I appreciate your help!

                      Comment


                        #26
                        Re: Can no longer access windows network in v7.10

                        CH Yes I do use a workgroup, it's called Workgroup.



                        Comment


                          #27
                          Re: Can no longer access windows network in v7.10

                          It appears that nmbd is not running on most of my machines. It is running on one, and I'm trying to figure out the difference. I've found various documents on the web concerning how to run it, but so far they all assume that files are located in different directories, so it is making thing difficult. If anyone has any instructions more relevant it would be appreciated.

                          Comment


                            #28
                            Re: Can no longer access windows network in v7.10

                            Just one observation:

                            For some time I have had seemingly the same problem as the thread starter with one of my PCs - one of two XPs. The rest is a mix of Win2000, XP (visiting granddaughter) and Kubuntu version mix. Some wired, some WIFI. All but the one XP was ok. For the two last weeks it got worse - it was totally shut out.

                            Then, today something strange happened:

                            1. My new Logitec Bleuetoot mouse disappeared. And so did my Sony-Ericsson 750i, my iPac ... and so on.

                            2. Deleted the HP Bluetooth both as network card and Bluetooth unit in System Properties (hope I remember right, my XP is not English.)

                            3. The firewall broke down - closed itself. (Sunbelt Kerio free.)

                            4. Rebooted, "new hardware found etc."

                            5. Open Bluetooth and find both the mouse and other Bluetooth units. (Redo pairing etc.) Start Firewall.

                            6. Network places - no problem from the XP computer.

                            7. Now some issues going the other way!

                            CentaurHauler - my guess is you too may have an XP problem, not Samba.

                            Attached - my working smb.config. And yes, I know it is rather open, so I have to take care how I use the share folder.
                            Attached Files

                            Comment


                              #29
                              Re: Can no longer access windows network in v7.10

                              Also, don't know if this applies or not, but the security for XP home edition and XP professional have different requirements, apparently.

                              Comment


                                #30
                                Re: Can no longer access windows network in v7.10

                                Well, I've had limited success. I can see the network and shared Windows machines from my 3 Kubuntu v7.10 machines. Also, I can access 1 of the Kubuntu machines from the Windows machines. Here's the smb.conf file from it:

                                [global]
                                workgroup = PROD
                                server string = %h server (Samba, Ubuntu)
                                interfaces = 127.0.0.0/8, eth0
                                security = SHARE
                                map to guest = Bad User
                                obey pam restrictions = Yes
                                passdb backend = tdbsam
                                passwd program = /usr/bin/passwd %u
                                passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *passwd:*password\supdated\ssuccessfully* .
                                syslog = 0
                                log file = /var/log/samba/log.%m
                                max log size = 1000
                                dns proxy = No
                                panic action = /usr/share/samba/panic-action %d

                                [printers]
                                comment = All Printers
                                path = /var/spool/samba
                                create mask = 0700
                                printable = Yes
                                browseable = No

                                [print$]
                                comment = Printer Drivers
                                path = /var/lib/samba/printers

                                [cmf]
                                path = /home/cmf/
                                force user = cmf
                                read only = No
                                guest ok = Yes
                                case sensitive = No
                                strict locking = No

                                All the machines Kubuntu 7.10 and 7.04, Windows XP (Home and Pro) can see and access each other EXCEPT that no one can see two of the 7.10 machines. On these two machines SWAT reports that nmbd is not running. I'll look to see if there is any other difference in the smb.conf files that might be responsible.

                                Comment

                                Working...
                                X