On Sun, 2006-02-12 at 22:12 -0500, Kim Briggs wrote:

On 2/12/06, SOTL wrote:

...

Hi All

I am new to setting up SAMBA.

I have 2 computers I am trying to network.

Both computers have OpenSuSE 10.0 installed.

...........

Any help in what my problem is and how to proceed would be appreciated.

SOTL

--

Hi SOTL,

I'm not trying to joke with you, but if both computers are running Suse, why not use NFS to interact with each other? Setting the server and client up with Yast was very easy for me (i.e., no conf files manually edited).

For one thing NFS is a constant connection whereas samba/SMB can be accessed on a temporary basis. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

On Monday 13 February 2006 07:42 am, James Knott wrote:

Ken Schneider wrote:

...

...

I'm not trying to joke with you, but if both computers are running Suse, why not use NFS to interact with each other? Setting the server and client up with Yast was very easy for me (i.e., no conf files manually edited).

For one thing NFS is a constant connection whereas samba/SMB can be accessed on a temporary basis.

Why can't NFS be used on a temporary basis?

Because this is the test setup to a future larger system which will have Apple, MS, and Linux boxes. SOTL

On Mon, 2006-02-13 at 20:47 -0500, James Knott wrote:

SOTL wrote:

...

On Monday 13 February 2006 07:42 am, James Knott wrote:

...

Ken Schneider wrote:

...

...

I'm not trying to joke with you, but if both computers are running Suse, why not use NFS to interact with each other? Setting the server and client up with Yast was very easy for me (i.e., no conf files manually edited). For one thing NFS is a constant connection whereas samba/SMB can be accessed on a temporary basis. Why can't NFS be used on a temporary basis?

Because this is the test setup to a future larger system which will have Apple, MS, and Linux boxes.

My question was not in respect to what you're doing, but about Ken's assertion that you couldn't use NFS for a temporary set up.

I didn't say you couldn't use it for a temporary connection. NFS is -usually- used for somewhat permanent connections whereas SMB can be used without a persistent connection. For casual browsing of shared file systems SMB (samba) would be a better fit for the OP's use. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

On Mon, 2006-02-13 at 09:20 -0500, SOTL wrote:

If on the other hand one is attempting to connect a number of missed MS, Apple, and Linux then one MUST use Samba.

MS give away a free package that includes NFS support for Windows. It may be client only. Not sure. It you cannot find it, I can dig up the link. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23

On Mon, 2006-02-13 at 13:36 -0500, Gordon Keehn wrote:

Roger Oberholtzer wrote:

...

On Mon, 2006-02-13 at 09:20 -0500, SOTL wrote:

...

If on the other hand one is attempting to connect a number of missed MS, Apple, and Linux then one MUST use Samba.

MS give away a free package that includes NFS support for Windows. It may be client only. Not sure. It you cannot find it, I can dig up the link.

The product was / is Microsoft Services for Unix. It gives the ability to configure a Win box as an NFS client or server, and to run a significant sample of *nix products natively under Windows. It does NOT support everything, comes with some surprising (to me) omissions in its software inventory (although in fairness I was able to circumvent many of these by building the products (and frequently pre- and corequisites) from source). It ALSO interferes with normal operation of some non-Microsoft products. Overall I prefer Cygwin, although I've never tried to access or serve NFS shares under Cygwin.

Did you mean something was missing in the NFS implementation? Or in other things also packaged with the product? How would cygwin add NFS to Windows? -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23

On Mon, 2006-02-13 at 18:54 +0100, Roger Oberholtzer wrote:

On Mon, 2006-02-13 at 09:20 -0500, SOTL wrote:

...

If on the other hand one is attempting to connect a number of missed MS, Apple, and Linux then one MUST use Samba.

MS give away a free package that includes NFS support for Windows. It may be client only. Not sure. It you cannot find it, I can dig up the link.

Curious, where did you hear that MS had that package? I looked on their site last summer and didn't find it.

On Mon, 2006-02-13 at 21:18 -0500, James Knott wrote:

Mike McMullin wrote:

...

On Mon, 2006-02-13 at 18:54 +0100, Roger Oberholtzer wrote:

...

On Mon, 2006-02-13 at 09:20 -0500, SOTL wrote:

...

If on the other hand one is attempting to connect a number of missed MS, Apple, and Linux then one MUST use Samba. MS give away a free package that includes NFS support for Windows. It may be client only. Not sure. It you cannot find it, I can dig up the link.

Curious, where did you hear that MS had that package? I looked on their site last summer and didn't find it.

Well, it took a lot of hard work and sweat, but by putting "Unix" in the search box and hitting "Enter" I was able to ferret out the following.

http://www.microsoft.com/windowsserversystem/sfu/default.mspx

I was under the impression that it was nfs client only not the full suite. Obviously I was looking for the wrong thing.

On Tue, 2006-02-14 at 13:18 +0000, Kevanf1 wrote:

On 13/02/06, Mike McMullin wrote:

...

On Mon, 2006-02-13 at 18:54 +0100, Roger Oberholtzer wrote:

...

On Mon, 2006-02-13 at 09:20 -0500, SOTL wrote:

...

If on the other hand one is attempting to connect a number of missed MS, Apple, and Linux then one MUST use Samba.

MS give away a free package that includes NFS support for Windows. It may be client only. Not sure. It you cannot find it, I can dig up the link.

Curious, where did you hear that MS had that package? I looked on their site last summer and didn't find it.

It's been on the Windows CD since Windows 2000. I doubt that you would find it on the 9* series though.

They lost me at ME.

Kevanf1 wrote:

On 14/02/06, Mike McMullin wrote:

...

...

It's been on the Windows CD since Windows 2000. I doubt that you would find it on the 9* series though. They lost me at ME.

I only kept up with it because of my work at the time. I currently run Windows 2000 on this very PC - it's the one that has the scanner on it that Linux does not yet recognise....yet (it's coming). I have an XP disk.....it's atrocious.

My ThinkPad came with XP, so I shrunk the partition and installed Linux. I agree XP is bad, though ME is worse. XP's biggest problem is the user interface is so dumbed down, that it gets in the way. As I understand it, W2000 was the "best" (for lack of a better word <g>) version of Windows. What's really amazing is that companies use Windows for servers and then wonder why the servers fail!

Mike McMullin wrote:

On Tue, 2006-02-14 at 09:01 -0500, James Knott wrote:

...

What's really amazing is that companies use Windows for servers and then wonder why the servers fail!

Mayhap it's because it seems that Windows sets up easy but is a bear to maintain, but Linux is bear to set up and less problematic (IME) to maintain. "If it's that hard to set up, what do I have to do to keep it running?", and MS feeds that fear.

I suspect that often the people who make the decisions don't know there are superior alternatives. I work in the IT industry and the hands on tech types, such as myself, know about the alternatives and would rather work with them, but... My background includes various minicomputers from DEC, Data General and Pr1me, DOS, Windows, OS/2, Netware, VAX/VMS, Pr1mos and others, so I know of the various alternatives, and know from hands on experience that Windows is inferior. However, some CEO or manager who can't figure out how to do simple things in Windows makes the call on what gets used.

SOTL wrote:

On Sunday 12 February 2006 10:12 pm, Kim Briggs wrote:

...

On 2/12/06, SOTL wrote:

...

Hi All

I am new to setting up SAMBA.

I have 2 computers I am trying to network.

Both computers have OpenSuSE 10.0 installed.

...........

Any help in what my problem is and how to proceed would be appreciated.

SOTL

-- Hi SOTL,

I'm not trying to joke with you, but if both computers are running Suse, why not use NFS to interact with each other? Setting the server and client up with Yast was very easy for me (i.e., no conf files manually edited).

cheers, -- http://kimbriggs.com

A good question but then that goes to objective.

If one is trying to set up any number of boxes on a network where ALL the boxes are some version of Unix or Linux boxes THEN one would use NFS.

If on the other hand one is attempting to connect a number of missed MS, Apple, and Linux then one MUST use Samba.

Actually, no. NFS is available for Windows and I believe MAC.

On Monday 13 February 2006 12:00 am, Darryl Gregorash wrote:

On 12/02/06 11:06, SOTL wrote:

...

Hi All

I am new to setting up SAMBA.

I have 2 computers I am trying to network.

Both computers have OpenSuSE 10.0 installed.

I can SSH either one to the other. I ccan get and receiv e-mail and connect to web site. So issue is above ping level.

I purchased "SuSE Linux 10 Bible by Davies, Whittaker, and van Hagen' and followed setup procedure exactly. Bassically this is GUI setup.

I then tried to access the SERVER from the CLIENT and the CLIENT from the SERVER.

I receiv the following error message on both computers:

Can not find slp:/ in the tree. Internal errot.

My /etc/samba/smb.conf filas are as follows: <snip>

This particular problem has nothing to do with your samba configuration. The error is referring to an absent "service locator protocol" which is enabled in /etc/init.d/slpd, and is disabled by default (why, I do not know, since quite a few places including Konqueror are already configured to use it). AFAICT the system is ready to use it, and all you need to do is enable the service, per session by running (as root) "rcslpd start", or by enabling it with "insserv slpd" (equivalently, run Yast, select System/System services (runlevel), and enable slpd).

Of course, you could also find all this in the SuSE Administrator's Guide.

Hi All and specially Darryl Thanks Darryl you were right about the slp services not being activated. They are now activated. Unfortunately I still get exactly the same error message namelu: Can not find slp:/ in the tree Internal Error It was suggested to me that the source of the problem may be that the smppasswd file and that I did not have the correct user or password set correctly. Attached are my CLIENT and SERVER files. _____ SERVER smppasswd # This file is the authentication source for Samba if 'passdb backend' is set # to 'smbpasswd' and 'encrypt passwords' is 'Yes' in the [global] section of # /etc/samba/smb.conf # # See section 'passdb backend' and 'encrypt passwords' in the manual page of # smb.conf for more information. root:0:7AFFBB23C42095FE1841B9F02226DD3D:CDA6A2FA4891C12AD967B90778206005: [U ]:LCT-43EED964: _____ CLIENT smbpasswd # This file is the authentication source for Samba if 'passdb backend' is set # to 'smbpasswd' and 'encrypt passwords' is 'Yes' in the [global] section of # /etc/samba/smb.conf # # See section 'passdb backend' and 'encrypt passwords' in the manual page of # smb.conf for more information. _____ The user name for the CLEINT is "trunk" with password "Clienttestpw" The user name for the SERVER is "office" with password "Servertestpw" _____ If someone sees something wrond with either of these files I would appreciate their help. Thanks SOTL

On 2/14/06, Darryl Gregorash wrote:

Your samba configuration doesn't matter here at all. All the services in /etc/slp.reg.d should appear, if they are configured and running.

I don't understand ... why would SLES have slp on by default, and what could slp possibly have to do with SAMBA? If you are trying to access samba via slp services, then that pre-supposes that your samba server has registered with an slp DA (samba does not natively use slp discovery) and then your client must have slp discovery mechanisms. And, again, samba clients do not (to my knowledge anyway) natively use slp discovery. why the focus on and concern about slp? Peter

On Tuesday 14 February 2006 08:32 pm, Darryl Gregorash wrote:

On 14/02/06 08:33, SOTL wrote:

...

On Monday 13 February 2006 12:00 am, Darryl Gregorash wrote:

<snip> Unfortunately I still get exactly the same error message namelu:

Can not find slp:/ in the tree Internal Error

It was suggested to me that the source of the problem may be that the smppasswd file and that I did not have the correct user or password set correctly. Attached are my CLIENT and SERVER files.

<snip>

Your samba configuration doesn't matter here at all. All the services in /etc/slp.reg.d should appear, if they are configured and running.

I did forget about one problem I am still having, and I have no idea what causes it. In the Konqueror navigation panel, if I open "network", then try to open the "Local Network" tree, I get the same error. However, just clicking on "Local Network" opens "service:/" in the main Konqueror panel, and one of the selections is SLP services. This one works if the slp server is running.

There are plenty of hiccups in the Konqueror configuration to use all this stuff; for example, the SWAT Samba configuration tool cannot be accessed from at least one link. Fortunately, there is at least one that does work.

An alternative, which I prefer, is to use Go (menubar)/Network Folders. This includes a link to SLP services, which does work.

I am still getting the exact same error message Can not find slp:/ in the tree. Internal errot. Thought fixing password issue might solve the problem but it did not or if it did I do not know it. I recall many noons ago trying to set Samba up. I did not suceed at that time principally because I did not have a network but simply two computers connected together. Can be done but it was not worth the effort. Anyway if I recall one needs a mount point for Samba and that what one had was something like: /mnt/Samba I checked for this in both computers and I do not have such mount point. Is this required? As far as the Samba Password file please disregard previous posting of CLIENT and SERVER smbpasswd files. These files have now been set as follows. Hopefully this is correct but maybe not as I am not sure of here is that the GUI user and the Samba user are the same in both computers. Is this correct? GUI-User = trunk with password of <ClientTestPW> Samba User = trunk with password of <ClientTestPW> CLIENT-smbpasswd # This file is the authentication source for Samba if 'passdb backend' is set # to 'smbpasswd' and 'encrypt passwords' is 'Yes' in the [global] section of # /etc/samba/smb.conf # # See section 'passdb backend' and 'encrypt passwords' in the manual page of # smb.conf for more information. trunk:1000:15289F3520D59967AAD3B435B51404EE:DF17935909BFC2B9B5D21BCA66CB7D62: [U ]:LCT-43F31C60: _____ GUI-User = office with password of <ServertTestPW> Samba User = office with password of <ServertTestPW> SERVER-smbpasswd # This file is the authentication source for Samba if 'passdb backend' is set # to 'smbpasswd' and 'encrypt passwords' is 'Yes' in the [global] section of # /etc/samba/smb.conf # # See section 'passdb backend' and 'encrypt passwords' in the manual page of # smb.conf for more information. office:1000:7AFFBB23C42095FE1841B9F02226DD3D:CDA6A2FA4891C12AD967B90778206005: [U ]:LCT-43F2D61C: Thanks for previous help. SOTL

On Wednesday 15 February 2006 04:42 pm, Darryl Gregorash wrote:

On 15/02/06 07:43, SOTL wrote:

...

On Tuesday 14 February 2006 08:32 pm, Darryl Gregorash wrote:

...

<snip> An alternative, which I prefer, is to use Go (menubar)/Network Folders. This includes a link to SLP services, which does work.

I am still getting the exact same error message

Can not find slp:/ in the tree. Internal errot.

<snip>

Your Samba configuration is still irrelevant; it will still be irrelevant tomorrow as well. This is not a Samba error.

There is at least one place in Konqueror that gives that error, even if the slp server is running. If all you need is to access the samba server, you do not even need to go that route.

Use "Go/Network Folders", which opens up remote:/ and includes links to all remote network services, including Samba.

Thanks for the help. Sorry if I am not understanding this. I tried the above in both CLIENT and SERVER. I was not able to see any other computers or any Windows network. For CLIENT only So, for CLIENT ONLY [as SERVER does not have Gnome installed in it at this point] I logged out of KDE and logged in Gnome to eliminate any issues with Konqueror. I then clicked on Computer {which brough up the Gnome Computer File Browser ->Network -> Windows Network - tux-net [My Network] -. Linux [at which point I had 3 options] 1) users -> [Got Log in screen] -> Logged in as trunk [trunk is the user in CLIENT]. I could see all home files on CLIENT. I could NOT see any files on SERVER. 2) profiles {got same results as user} 3) groups got error message that I had not formed any groups which is correct. Since I did not have a option to log in as office [user in SERVER] I attempted to add that user name to CLIENT. This was promptly denied as office is not a CLIENT user. I noted that I do not have a mount point such as /mnt/Samba. Is this relevant? Thanks again SOTL

On 15/02/06 17:48, SOTL wrote:

<snip> Thanks for the help.

Sorry if I am not understanding this.

I do not know what is so hard to follow. In a couple of places, the SLP links in Konqueror are broken. However, SLP is not necessary to get to samba. You can do it, but it is not necessary. Just type "smb:/" in the location bar and hit <enter>. Now on to your samba problem, which is completely different.

I tried the above in both CLIENT and SERVER. I was not able to see any other computers or any Windows network.

If you cannot see any other computers, check to see if any firewall is blocking the ports that Samba uses. That can be done in the Samba setup in Yast (server for sure, maybe the client setup also, I don't recall just now). You can also access the Samba configuration in SWAT, http://localhost:901 in any browser. If the firewall is open on both systems, then make sure you can get it working without requiring user logins. To do this, allow guest logins in the setup. Do this on both machines. You may need to set this for each shared object, I don't recall if it can be done globally. In /etc/samba/smb.conf, if a shared object is allowed for guests, you will see the line "guest ok = Yes". It does seem rather curious is that you have a [netlogon] section configured on the SERVER machine, but netlogon is disabled on the CLIENT system. I am not sure if this is relevant, but the two configurations should probably be the same insofar as logging in is concerned. One thing for sure: You should consult the Samba documentation. Install the samba-doc package, then read /usr/share/doc/packages/samba/Samba-Guide.pdf or the html version under /usr/share/doc/packages/samba/htmldocs/Samba-Guide/.

I noted that I do not have a mount point such as /mnt/Samba. Is this relevant?

I don't have any such mount point. Some other general comments that probably aren't going to solve the problem, but may be of importance for security, etc.: 1) Neither system has a netbios machine name. This is not necessarily the same as the hostname, and I am not sure if the hostname is sent if the netbios name field is left empty. Personally, I always set the netbios name so there can be no possible confusion. (Each system's netbios name must of course be unique.) 2) Neither configuration is restricted to a particular interface, which may open either or both systems to external security threats, depending on firewall configuration. Restrict samba to listen on the internal interface only. Specifying the IP of the internal interface is sufficient, if you are using fixed IPs in your private LAN. 3) You also have not set "hosts allow" which will allow any system to try to connect to your samba servers. Restrict this to your local subnet, eg. 192.168.0. (which means the same in this case as 192.168.0.0/24). You can also restrict to specific IPs.

On 16/02/06 06:46, James Knott wrote:

I also have not been able to use it. When I run slp:/ I simply get an empty Konqueror window. I have NFS and Samba running.

Then don't use it. SLP is a service locator. I really have no idea how it works, but it sure isn't necessary to use nfs or samba. Use Go/Network Folders, which brings up "remote:/" If you use the navigation panel (F9) in Konqueror, you can easily create a folder in the sidebar to do the same thing.

On 18/02/06 09:41, SOTL wrote:

On Thursday 16 February 2006 02:25 am, Darryl Gregorash wrote:

...

On 15/02/06 17:48, SOTL wrote:

...

<snip> Thanks for the help.

Sorry if I am not understanding this.

I do not know what is so hard to follow.

Sorry but my reference was to Samba and Samba Server connections not Konqueror.

When you are trying to hammer nails with a broken hammer, the condition of the nails does not matter.

<snip>

...

One thing for sure: You should consult the Samba documentation. Install the samba-doc package, then read /usr/share/doc/packages/samba/Samba-Guide.pdf or the html version under /usr/share/doc/packages/samba/htmldocs/Samba-Guide/.

Went to above doc; opened "Samba by Example" Chapter 1 No Frills Samba Server

OK, so much for that.. try /usr/share/doc/packages/samba/htmldocs/Samba-HOWTO-Collection/ instead, particularly Chapter 2 (Fast Start). This works for a server configuration: [global] workgroup = MIDEARTH netbios name = HOBBIT security = share [data] comment = Data path = /export read only = Yes guest ok = Yes To control who can actually connect to the system, one or both of the following are recommended in the global section: interfaces = <IP of NIC to listen on> hosts allow = <subnet of allowed hosts> eg, if you want to listen on the interface that has IP 192.168.1.106, then interfaces = 192.168.1.106 hosts allow = 192.168.1. Note how that subnet is specified. Change all names and IPs to what is relevant to your network, and yes, it will give you a functioning smb server with no security controls. I won't bother wading through all the ways to specify "interfaces", this is the easiest if you use fixed IPs on this network. For read-only access, the shared directory should be chmod 0744. If you want to allow read/write access, then of course "read only = no", and the directory should be chmod 0766. Also do the steps in the section "Anonymous Read/Write server" in the "Fast Start" document above. BTW, your server does *not* have a MAC address of 192.168.1.106. A MAC address looks like this: 00:50:FC:8B:4D:D1

I do knowsince I do not know Samba but it is my belief that CLIENT is not connecting to SERVER mount point if that is what they call /plans directory created in procedure 1.1 item 3. I don't know why you are even bothering with this mount point stuff. That is used by smbmount, to mount a remote filesystem that you access via smb. On the client system, you should only need to specify the workgroup and a Netbios name; then on that client, type smb:// in any browser location bar and hit <enter> (maybe Mozilla, etc will need to be further configured, but Konqueror already is configured). Once you can access the server, you can create direct links to its shared folders, eg. smb://HOBBIT/export.

If you really must use mountpoints, then read "man smbmount".