samba - Jan 2002 - Conf that works for samba-2.2.1a-32 doesn't work for samba-2.2.0a-0 - any idea why?

Hello,

I had recently set up a remote server with a configuration that only has 1
share, accessible by one user from only a few allowed hosts. It worked great and
I could access the share by typing the following into WIn2k's file manager:

\\<hostname or IP address here, both work>\webhome

I would be asked for a username/password and it worked great. I should perhaps
point out that this box was running SuSE Linux 7.3, samba-2.2.1a-32

Unfortunately that computer has hardware issues, so I'm trying to move the
setup to another computer, which is running SuSE Linux 7.2, samba-2.2.0a-0. I
diffed the working smb.conf to the 7.2 computer's default smb.conf, and
since I didn't see anything different, I just moved the default conf out of
the way and used the working conf the way it was, with the exception of changing
the netbios name.

However on the new server when I try to connect to it in exactly the same manner
as I connected to the old server, Windows (after pausing for a moment) gives me
the following error:

"Windows cannot find '\\<the_servername>\webhome'. Please
check the spelling and try again, or try searching for the item by clicking the
Start button and then clicking Search."

I get this error whether I use the hostname or the IP address, and I did check
the DNS on the hostname - it's fine.

Can anyone give me a clue as to why a conf that works on the first servers
doesn't work on the new server (remember, the "new" server is
actually running older software)

Thanks.


----------------------------------------------------
Jonathan Wilson
System Administrator

Cedar Creek Software     http://www.cedarcreeksoftware.com
Central Texas IT     http://www.centraltexasit.com

Ok, this is really stupid:

I'm used to SuSE 7.3 already, where the samba conf file is
/etc/samba/smb.conf.

In 7.2 the conf is /etc/smb.conf. I was fooled but the fact that the update to
samba-client that was made available for 7.2 made the switch to /etc/samba (duh,
SuSE) and has placed an smb.conf in there.

Anyway, now that I've figure that out I've pretty much got it working,
except for one thing: logging.

I've noticed on 2 7.2 boxes that I have on hand the smbd seems to do no
logging at all - /var/log is totally devoid of anything related to samba, not
only is there no separate log file but there's no smbd or nmbd stuff in
faillog, messages or warn either.

I even set

        log file = /var/log/samba/smb.log

in the globals section - still nothing

I also tried variations of         log file = /var/log/samba/%m

Which was the default.

Any ideas what I need to do to induce samba to log? It's strange that
it's ignoring the log file directive.

Thanks.

P.S. post take an unusually long time to reach the list....


At 05:25 PM 1/14/2002 -0600, you wrote:
>Hello,
>
>I had recently set up a remote server with a configuration that only has 1
share, accessible by one user from only a few allowed hosts. It worked great and
I could access the share by typing the following into WIn2k's file manager:
>
>\\<hostname or IP address here, both work>\webhome
>
>I would be asked for a username/password and it worked great. I should
perhaps point out that this box was running SuSE Linux 7.3, samba-2.2.1a-32
>
>Unfortunately that computer has hardware issues, so I'm trying to move
the setup to another computer, which is running SuSE Linux 7.2, samba-2.2.0a-0.
I diffed the working smb.conf to the 7.2 computer's default smb.conf, and
since I didn't see anything different, I just moved the default conf out of
the way and used the working conf the way it was, with the exception of changing
the netbios name.
>
>However on the new server when I try to connect to it in exactly the same
manner as I connected to the old server, Windows (after pausing for a moment)
gives me the following error:
>
>"Windows cannot find '\\<the_servername>\webhome'. Please
check the spelling and try again, or try searching for the item by clicking the
Start button and then clicking Search."
>
>I get this error whether I use the hostname or the IP address, and I did
check the DNS on the hostname - it's fine.
>
>Can anyone give me a clue as to why a conf that works on the first servers
doesn't work on the new server (remember, the "new" server is
actually running older software)
>
>Thanks.
>
>
>----------------------------------------------------
>Jonathan Wilson
>System Administrator
>
>Cedar Creek Software     http://www.cedarcreeksoftware.com
>Central Texas IT     http://www.centraltexasit.com
>
>
>-- 
>To unsubscribe from this list go to the following URL and read the
>instructions:  http://lists.samba.org/mailman/listinfo/samba
----------------------------------------------------
Jonathan Wilson
System Administrator

Cedar Creek Software     http://www.cedarcreeksoftware.com
Central Texas IT     http://www.centraltexasit.com