Samba access problem

[MikeL_4]

We recently upgraded Samba from 2.2.8a to 3.0.21a. I am able to access my Samba shares without any problem but one user can't.

In his log I show:
[Thu Mar 9 11:11:26 2006
, 2] lib/access.c:check_access(322)
Allowed connection from (10.18.0.216)
[Thu Mar 9 11:11:26 2006
, 2] smbd/sesssetup.c:setup_new_vc_session(772)
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old
resources.
[Thu Mar 9 11:11:26 2006
, 2] smbd/sesssetup.c:setup_new_vc_session(772)
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old
resources.
[Thu Mar 9 11:11:26 2006
, 2] smbd/server.c:exit_server(614)
Closing connections

My global settings for Samba are:
[global]
workgroup = NA
netbios name = ASK_HPUX
netbios aliases = ask_hpux
server string = Sources Server
security = SERVER
map to guest = Bad Password
password server = 10.18.0.66, 10.18.6.67, 10.25.160.170, 10.25.159.119
passdb backend = smbpasswd
guest account = pcguest
log level = 2
log file = /var/log/samba/log.%M.%I
deadtime = 10
printcap name = lpstat
preferred master = No
local master = No
domain master = No
wins server = 10.25.160.163
admin users = msylvia, rprewitt, mlense
hosts deny = 10.130., 135.108., 10.28., 10.131., 10.200.

Any idea as to what might be causing this ??

[Mark Greene_1]

Did the Wins entry for his PC change?

mark

[MikeL_4]

If you mean the wins server entry, no it's always been that way..

[Geoff Wild]

What's in your username.map file?

To be honest - I prefer SECURITY=ADS or DOMAIN if ADS isn't running.

Are you running samba or HP's CIFS?

Are you using winbind?

Rgds...Geoff

[MikeL_4]

Don't know of this file: username.map ?

security=server is the way it was set up since way before me...

Running samba version

Not using winbind

[Geoff Wild]

Well, first plug - If running on HP-UX I would use HP's CIFS - and not the Open Source one.

Anyways, you upgraded Samba from 2 to 3 - was there a reason for that? Most do because of the ADS support. If you are not running Active Directory, then 2.2.12 would have been an okay upgrade path.

That said, the odd thing here is, you can access but another user can't.

Is that user in the "admin users =" list?

Do you have a "valid users = " list in the smb.conf file?

Try increasing the "log level = " to say 5 and see what the error is.

Rgds...Geoff

[Geoff Wild]

Sorry - forgot to ask - which version of HP-UX are you running? as I know you can't run version 3 of samba on 11.0 (at least I know HP doesn't support it).

Rgds...Geoff

[Rita C Workman]

..ok....this may be from left field.

If you do the same check for everyone...then could it be possible that resources just aren't letting him in. Are you getting any nfile alerts. Samba opens several files for every connection. If you run out of resources..the next guy can't log in.

Like I said...just a left question.
Rita

[MikeL_4]

nfile is set to 11408
ninode is set to 2048
maxfiles is set to 200

This server is only used to run Samba and used by about a half dozen SA's to store miscellaneous files, depots, etc....

[MikeL_4]

PS: there are no messages in syslog about any parameters being reached...

[MikeL_4]

HPUX Version 11.11

[MikeL_4]

I've attached a copy of the log from the user who is getting the connection failures in case that helps..

[MikeL_4]

I was comparing the samba log from the failing pc and comparing it to my pc when I map a drive and everything was the same until we get to the following:

Faailing pc:
NativeOS=[Windows XP 3790 Service Pack 1] NativeLanMan=[] PrimaryDomain=[Windows XP 5.2]

Working pc:
NativeOS=[Windows 2002 Service Pack 2 2600] NativeLanMan=[Windows 2002 5.1] PrimaryDomain=[]

Then the working connection goes on with:
[Fri Mar 10 08:16:07 2006
, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(641)
Got user=[] domain=[] workstation=[ORL02MLENSE] len1=1 len2=0
[Fri Mar 10 08:16:07 2006
, 5] auth/auth_util.c:make_user_info_map(162)
make_user_info_map: Mapping user []\[] from workstation [ORL02MLENSE]

Where it looks like the failing pc keeps trying to authenticate him ???

[Fri Mar 10 08:26:11 2006
, 5] auth/auth.c:make_auth_context_subsystem(476)
Making default auth method list for security=server
[Fri Mar 10 08:26:11 2006

[Dave Poeschel · Accepted solution]

I don't know if this applies here but you might want to take a look at the following...

Problem - 64 bit Windows XP clients cannot connect to the CIFS Server when it is
configured with smb.conf parameter "security=server". Other
Windows clients could also fail to connect if they have the local policy for
LAN Manager set to "Send NTLM response only" as does the 64 bit
Windows XP clients by default.
Workaround - Use the Administrative Tool and proceed with the following steps on
each failing client:
Step 1. Select "Local Security Policyâ .
Step 2. Select "Local Policies".
Step 3. Select "Security Options".
Step 4. Select "Network security: Lan Manager authentication level".
Step 5. Set it to "Send LM & NTLM response" or â Send LM & NTLM - use
NTLMv2 session security if negotiatedâ .

[MikeL_4]

Thanks for all replies.

Dave, this is what we did last Friday that resolved the problem after we opened a case with HP Support for CIFS.. Thanks