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

    Can no longer access windows network in v7.10

    I had managed to get file sharing working both ways under v7.04 with the WinXp machines on my network, but this no longer works. I tried copying and old smb.conf file that worked previously, but no joy. Does anyone know which random text strings I need to type in which obscure file to make it work this time?

    I'd appreciate if anyone who has worked it out could give me a clue.

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

    Could you post your smb.config file (/etc/samba/smb.config) so we can maybe find something in there?
    Do you have samba installed?
    HP Pavilion dv6 core i7 (Main)
    4 GB Ram
    Kubuntu 18.10

    Comment


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

      Sure - from testparm:

      [global]
      interfaces = lo, 127.0.0.0/8, eth0
      bind interfaces only = Yes
      security = SHARE
      obey pam restrictions = Yes
      passdb backend = tdbsam
      passwd program = /usr/bin/passwd %u
      passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spas
      sword:* %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
      invalid users = root

      [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
      read only = No
      guest ok = Yes


      I suspect something in here is "wrong" - but then it used to work. Actually, in the above I changed the parameter to "interfaces = lo, 127.0.0.0/8, eth0" from "interfaces = lo, eth0" in a troubleshooting attempt.

      Also, it does not appear to be a problem with Ethernet connectivity, as I'm accessing the internet fine.

      Yes, I have samba installed. Thanks for responding!

      Comment


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

        Sure no problem.

        For some reason gutsy wants this line in smb.conf
        force user = fintan
        here is my smb.conf as a reference:

        [global]

        workgroup = FINTANHOME
        interfaces = eth0
        map to guest = bad user

        [Data]

        path = /Data
        read only = no
        guest ok = yes
        case sensitive = no
        strict locking = no
        force user = fintan



        [HP4200]

        printing = cups
        path = /var/tmp
        printable = yes
        guest ok = yes
        guest only = yes
        I hope this points you in the right direction
        HP Pavilion dv6 core i7 (Main)
        4 GB Ram
        Kubuntu 18.10

        Comment


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

          Well, I realized the smb.conf file I posted above was more corrupt than I thought, and the workgroup was missing. I fixed it and added the force user string, but I still get a "timeout on server" error. Here is what it looks like now. Who is supposed to be the server here - do I need to enable WINS?


          [global]
          workgroup = PRO
          server string = %h server (Samba, Ubuntu)
          obey pam restrictions = Yes
          passdb backend = tdbsam
          passwd program = /usr/bin/passwd %u
          passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spas
          sword:* %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
          invalid users = root
          force user = cmf

          [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
          read only = No
          guest ok = Yes

          Comment


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

            You don't have this somewhere?

            msdfs proxy = no

            It reintroduced itself with the upgrade, and used to make trouble in Feisty Fawn

            Comment


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

              No, I do not think the "msdfs proxy = no" thing has crept back in (I'll double check). I've got 2 machines that worked on the network with v7.04, so I have smb.conf files that worked. Also, I built a new machine starting with v7.10, and it doesn't work any better.

              Comment


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

                I've got 2 machines that worked on the network with v7.04, so I have smb.config files that worked
                Are those machines still working with samba? If so how do their smb.configs differ from your 7.10 smb.config ?
                HP Pavilion dv6 core i7 (Main)
                4 GB Ram
                Kubuntu 18.10

                Comment


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

                  Originally posted by CentaurHauler
                  No, I do not think the "msdfs proxy = no" thing has crept back in (I'll double check). I've got 2 machines that worked on the network with v7.04, so I have smb.conf files that worked. Also, I built a new machine starting with v7.10, and it doesn't work any better.
                  The reason I ask is, after the upgrade my network was gone. When I was to introduce the force user = I found this:

                  Code:
                  guest ok = yes
                  read only = no
                  case sensitive = no
                  strict locking = no
                  # msdfs proxy = no
                  username = 
                  msdfs proxy = no
                  So, at least some times, this can reintroduce itself.

                  Comment


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

                    Actually, I can still see my v7.04 server from all the windows machines, but i can no longer browse the network from my server - I get the same timeout error. I'm still wondering about the WINS services.

                    I do not recall when this changed, as I do not normally access the network from the server - it may have been an update I did that I don't remember.

                    Comment


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

                      How can I "reset" the smb.conf file to whatever 7.10 would have generated on a clean install?

                      Comment


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

                        Centaur -

                        I've scanned the posts you've made so far, and it seems that you know what you are doing. But I hate to assume, so ....

                        This Windows, Linux, and Samba link appears to be very well written and documented. I have no idea if it may shed some light on your problem, but ....
                        Windows no longer obstructs my view.
                        Using Kubuntu Linux since March 23, 2007.
                        "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                        Comment


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

                          Thanks Snowhog - I actually am quite the novice, trying to learn just enough to get it to work. Unfortunately, I've learned more than I planned on.

                          I suppose I'll have to actually read up and figure out what is going on, and the links will be helpful. I've got some other stuff that I need to attend to for a couple of days, but I hope to get back to it soon.

                          Comment


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

                            You're welcome.
                            Windows no longer obstructs my view.
                            Using Kubuntu Linux since March 23, 2007.
                            "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                            Comment


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

                              Well, I made some progress - I can see the Kubuntu machines on my network when browsing from Windows machines. But I cannot access them, as I cannot satisfy the username and password request. Also, I cannot see anything from the Kubuntu machines, and I get a timeout error.

                              I uninstalled and reinstalled samba, and then did some minor mods of the samba.conf file.

                              I gotta say - this sucks.

                              Comment

                              Working...
                              X