topic Re: samba configuration in Operating System - Linux

samba configuration

Nick D'Angelo — Tue, 04 Mar 2003 19:45:13 GMT

I have two machines, as close to the same as possible with RH8.

One machine is on the Winblows network and the samba shares are accessible.

On the other PC, the PC appears on network Neighbourhood, but errors when I try to connect to it.

I copied the smb.conf file from the 'working' RH machine to the other, made some minor customizations to it, ie share directories are a little different and still no go.

Any ideas?

Re: samba configuration

Steven E. Protter — Wed, 05 Mar 2003 00:23:55 GMT

These two machines can talk to each other right? No networking problems.

You may need to re-run the process that creates the samba passwords.

Here is a cut and paste version.

As user root.

sbmpasswd username password

The password should be the actual user password.

SEP

Re: samba configuration

John Poff — Wed, 05 Mar 2003 02:10:57 GMT

Hi,

Have you checked the Samba log files on the machine that is having problems? If the log files don't provide any clues you can jack up the debug level in the Samba startup script and bounce Samba. I'd suggest starting at debug level 3 and working up from there. Samba in debug mode will generate lots of messages in the log file but it can give you some good information.

JP

Re: samba configuration

Steven E. Protter — Wed, 05 Mar 2003 03:59:24 GMT

Log files are a great idea. I keep forgetting about those.

If you need to reprocess passwords, here is a more complete procedure now that I have my book in front of me.

1) Add a intended samba user

useradd -m chuckp
passwd chuckp
(don't forget to follow good security and not use anything guessable)

cat /etccc/passwd | /usr/bin/mksmbpasswd.sh > /etc/samba/smbpasswd

smbpasswd chuckp

Change the password if you wish.

service smb restart

(that's red hat, probably other dist).

SEP

Re: samba configuration

Balaji N — Wed, 05 Mar 2003 04:04:43 GMT

u might have already checked this, but just in case.

1. are any firewall running on the box which is not working.
2. try using the ipaddress rather than the host name while browsing the share.
3. try adding the linux box ipaddress to the lmhosts file on the windows box.

my 2p's.
-balaji

Re: samba configuration

Ralf Puchner — Thu, 24 Apr 2003 07:19:24 GMT

I wonder why nobody asked for the type of samba-server. Is it a domain controller or only in workgroup mode?

This is important because as a PDC you must register each workstation and user, it is also not possible to have the same domain/name on another samba server.

What happened if you type in the following commands on the workstations?

net view \\
net use \\\ /user:administrator

Please post your smb.conf for further informations.

Re: samba configuration

Francisco J. Soler — Thu, 24 Apr 2003 10:58:33 GMT

Hi,
if you don't want to use smbpasswd, and want the users share the same passwords that linux box, you can enable plain text passwords in smb.conf file and modify the register in the windows pc's to enable this capabilitie.

I send you the .reg files for different windows OS.

Frank.

Re: samba configuration

Chakravarthi — Thu, 24 Apr 2003 11:16:21 GMT

ok,

try restarting the smb service, check both smbd and nmbd are properly running or not, what error you are getting when trying to connect

Re: samba configuration

Nick D'Angelo — Mon, 16 Jun 2003 17:07:32 GMT

Interestingly, I have the same problem on a HPUX11.i server now.

It used to be setup as 'test' and now we have moved it to production (changed ip address and hostname). We used to be able to browse to it from the Winblows world via network neighborhood, but since we moved it to production, we can not.

If I go to my PC and type in: net view \\hostname, I can see all the shares just fine, however I can NOT browse to it from the net neigh.

Nickd

Re: samba configuration

Caesar_3 — Mon, 16 Jun 2003 18:14:16 GMT

Hello!

Check the permissions for the computers
that you want to enter your server,
maybe they don't have the needed permissions
or the server can't recognise them

Caesar

Re: samba configuration

Steven E. Protter — Tue, 17 Jun 2003 01:33:20 GMT

Changing the hostname of the system just prior to going production with it is like putting it in production minus half the tests.

There are a lot of products like oracle that will stop working if the hostname changes.

We do it a little differently since we once had a rollout, prior to my time as head admin blow up hugely due to this problem.

Among the products that can break with a hostname change:

omniback v 3.X
openspool
Veritas backup

We set up the machine from step A-Z with its production hostname.

When its fully tested, we change the DNS record that used to point to the old production system to point to the new production system.

Example:

our current production server is called jufprod

our new production server is going to be moriah

The actual step that puts the server into production is the DNS change. All the configuration was done in advance with a new production IP address. The oracle configuration files have IP addresses in them, not host names.

In the world of DNS the system will forever have two hostnames, until we are sure we can drop support for the old one. HP-UX could care less.

Is this the cause of your problem? Probably not. To be sure I'd have to see your smb.conf file.

I'll try and remember to post mine in the morning.

Here is a working Linux one now!!!

SEP

Re: samba configuration

Jerome Henry — Tue, 17 Jun 2003 04:52:38 GMT

But if you check smb.conf file and see that host is correctly set, samba shouldn't complain about this name and Ip changing.

Check if you do not have any access list set on a switch somewhere...

J

Re: samba configuration

charlie_20 — Wed, 18 Jun 2003 07:22:55 GMT

Hi there people,

Maybe an option to try,

I've got an RH and installed Samba.(2.2)
Now 3.0 is out....-->> samba.org ..with intergrated deamons (smbd + nmbd).

But oke i've got problems there because
the password of the windows user is encrypted.
and so the samba deamon must accept ecrypted passwords. (or you can make it plain text and have to do it also in the registry of windows --but it's not recommended)
so once you diceded about the passwords you can configure the username on the samba + linux manager + on the windows mashine (they have to be the same)

Then copy the smb.conf to the propper dir.
then restart the smbd + nmbd deamons and you will see the redhat server in network neighborhood (on the windows mashine)

That's all folks....

1.password encrypt YES / NO
2.SMB.Conf (chmod 777 / 755 if needed)
3.check firrewall (allow the server / client)
4.if it fail rpm -Uhv samba.3.0 install and try again.
5. option for newbees (like me) go to www.webmin.com (it's free)install the rpm package.
Go to the webbrowser and type the ip address of the linux box :10000 on this port and login with root access. you can configure everything there with a mouse click (also the start up fase (boot up segment, wich was asked before).....good luck fellas..

should be working now....

Re: samba configuration

charlie_20 — Wed, 18 Jun 2003 07:23:56 GMT

Re: samba configuration

John Meissner — Wed, 18 Jun 2003 11:32:54 GMT

For the easiest Samba install ever:

install Red Hat 9

Sharing with Samba via RH 9 is almost as easy as creating a share in Windoz

I've tried to configure samba with RH 7.3 and 8 and never had much luck... when i tried with 9 it was SO easy.

Re: samba configuration

Nick D'Angelo — Mon, 23 Jun 2003 17:59:03 GMT

Onto RH9. then.

Thanks for all your ideas.