Samba log problem.

[Kelly Roberts]

Hi guys,

Hope you can help me!!!

I have a Windows 2K PC connecting to a HP-UX 11.11 share using samba 3.0.0 which works ok but once connected and the log is created, inside the log the following message keep being displayed...
[2003/12/05 15:06:00, 1] smbd/service.c:make_connection_snum(698)
10.253.2.41 (10.253.2.41) connect to service mis_dev initially as user systems (uid=113, gid=20) (pid 15876)
[2003/12/05 15:06:00, 1] smbd/service.c:make_connection_snum(698)
10.253.2.41 (10.253.2.41) connect to service mis_dev initially as user systems (uid=113, gid=20) (pid 15876)
[2003/12/05 15:06:00, 1] smbd/service.c:close_cnum(880)
10.253.2.41 (10.253.2.41) closed connection to service mis_dev
[2003/12/05 15:06:00, 1] smbd/service.c:make_connection_snum(698)
10.253.2.41 (10.253.2.41) connect to service mis_dev initially as user systems (uid=113, gid=20) (pid 15876)
[2003/12/05 15:06:00, 1] smbd/service.c:close_cnum(880)
10.253.2.41 (10.253.2.41) closed connection to service mis_dev
[2003/12/05 15:06:03, 1] smbd/service.c:make_connection_snum(698)
10.253.2.41 (10.253.2.41) connect to service mis_dev initially as user systems (uid=113, gid=20) (pid 15876)
[2003/12/05 15:06:09, 1] smbd/service.c:close_cnum(880)
10.253.2.41 (10.253.2.41) closed connection to service mis_dev
[2003/12/05 15:06:10, 1] smbd/service.c:make_connection_snum(698)
10.253.2.41 (10.253.2.41) connect to service mis_dev initially as user systems (uid=113, gid=20) (pid 15876)

The log keeps growing until I disconnect the share.
This only happens on one PC...All others only have the connection message once.

Can you help??

[James A. Donovan]

Only thing I could find...

http://lists.freebsd.org/pipermail/freebsd-questions/2003-October/023937.html

I'd suggest you start by determining the diferences between this PC and the others that do not cause this issue.

[Steven E. Protter]

There must be something different about this user versus the others. Its going to be hard for me to investigate that, you have to.

I would ask, how are you doing user authentication? If you are doing it with a windows Primary Domain Controller, the problem could lie there.

If not try re-running the smbpasswd -a username password command and see if the logging stops.

This doesn't seem to be a connection issue, just an annoying log issue.

SEP

[Kelly Roberts]

Hi,

I've changed the log file size to keep the file small.....

Many Thanks...

[Darren Prior]

Hi,

If you're using a log file for each client you could use the include parameter for this client , including a file containing the line debug level = 0 to reduce the logging just for this one user. Of course this would mean that you get no other level 1 logging or above for this single client.

The include paramter is explained in Using Samba (The O'Reilly book), also in smb.conf man page.

regards,

Darren.

[Kelly Roberts]

Hi,

The problem seems that when the pc connects to the share, when I look at the status screen in samba it tells me that for that client there is at least 5 to 8 shares open.

This makes the screen difficult to see who is using what share...

Is there any way of only connecting once????

Many Thanks

[Darren Prior]

Hi Kelly,

How is the client PC connecting to the share - are they browsing the network, mapping the drive directly or some other method?

Can you run smbstatus and attach the output to show exactly what shares this client is connecting to?

The log section that you included at the top
of the thread only shows a single share - mis_dev.

regards,

Darren.

[Kelly Roberts]

Hi Darren,

It's connecting via windows explorer and mapping a drive to \\host\share using the id of systems in the smb.conf .

Here is the current list of connections.

[Darren Prior]

Hmmm - all but one of those are using the same smbd.

I think you need to step back and look at when the problem first appeared and what has changed around that time. For example, did you have this problem on previous Samba versions?

regards,

Darren.

[Kelly Roberts]

Hi all,

Rebuilt the Windows 2000 PC which have the problem.....

At the moment this seems to have cured the problem(or the problem has gone away)

Many Thanks for all your help.....

Kelly.