Samba Access Problems

Tim Holmes tholmes at mcaschool.net
Thu May 12 17:32:18 UTC 2005


> On May 12, 2005, at 9:26 AM, Tim Holmes wrote:
> 
> Good Morning Again Everyone:
> 
> This seems to be my day for problems
> 
> I am trying to access my File Server (FC2 Up2DATE running samba and
> authenticating against the domain)
> 
> I am working from my XP station, and when I browse the local network
to
> the box, I get an error message that states that I might not have
> permission to access the resource, (I do) and to contact my
> administrator (I am the admin), then it says that All Pipe Instances
are
> 
> busy. I have tried restarting samba and winbind, and also rebooting
the
> box to clear any hung up stuff in the processor.
> 
> Beyond that I am not sure where to go any suggestions are appreciated.
> 
> I can post any configs etc that you need, just let me know which ones
> you want.
> 
> Here is the smb.conf file
> 
> #Trial SMB.conf file copied from the quick start guide
> #Modified to fit the needs of MCASCHOOL
> 
> [global]
> workgroup = MCASCHOOL
> netbios name = SRVFS-01
> server string = MCASCHOOL File Server
> security = DOMAIN
> winbind separator = \
> winbind enum users = yes
> winbind enum groups = yes
> printcap name = cups
> disable spoolss = Yes
> show add printer wizard = No
> idmap uid = 15000-20000
> idmap gid = 15000-20000
> winbind use default domain = Yes
> use sendfile = Yes
> printing = cups
> 
> [homes]
> comment = Home Directories
> valid users = %S
> read only = No
> browseable = No
> 
> 
> 
> [Pictures]
> writeable = yes
> path = /share/pictures
> 
> [isoimage]
> writeable = yes
> path = /share/isoimage
> 
> [Ghost]
> writeable = yes
> path = /data/ghost_images
> 
> Have you looked at
> http://us1.samba.org/samba/docs/using_samba/ch12.html. I always start
> with the
> DIAGNOSIS.txt that I picked up from the samba site ages ago
> 
> 
>  [2005/05/12 11:14:23, 2] auth/auth.c:check_ntlm_password(312)
>   check_ntlm_password:  Authentication for user [tholmes] -> [tholmes]
> FAILED with error NT_STATUS_PIPE_NOT_AVAILABLE
> [2005/05/12 11:14:23, 2] smbd/sesssetup.c:setup_new_vc_session(608)
>   setup_new_vc_session: New VC == 0, if NT4.x compatible we would
close
> all old resources.
> [2005/05/12 11:14:23, 2] smbd/sesssetup.c:setup_new_vc_session(608)
>   setup_new_vc_session: New VC == 0, if NT4.x compatible we would
close
> all old resources.
> [2005/05/12 11:14:23, 2] auth/auth.c:check_ntlm_password(312)
>   check_ntlm_password:  Authentication for user [tholmes] -> [tholmes]
> FAILED with error NT_STATUS_PIPE_NOT_AVAILABLE
> [2005/05/12 11:14:23, 2] smbd/server.c:exit_server(571)
>   Closing connections
> 
> 
> That particular sequence was repeated over and over for about a minute
> in the log files
> 
> TIM
> 
[Tim Holmes wrote] 

I have been working my way through the fault tree specified above, and
have been passing all the tests till I reached the point called TESTING
CONNECTIONS WITH SMBCLIENT

Here is the session transcript


[root at SRVFS-01 samba]# smbclient //srvfs-01/Pictures
Password:
session setup failed: NT_STATUS_PIPE_NOT_AVAILABLE


Here is the smb.log from the relevant session (log level 3)


 [2005/05/12 13:07:22, 2] auth/auth.c:check_ntlm_password(312)
  check_ntlm_password:  Authentication for user [root] -> [root] FAILED
with error NT_STATUS_PIPE_NOT_AVAILABLE
[2005/05/12 13:07:22, 2] smbd/server.c:exit_server(571)
  Closing connections
[2005/05/12 13:07:31, 2] auth/auth.c:check_ntlm_password(312)
  check_ntlm_password:  Authentication for user [root] -> [root] FAILED
with error NT_STATUS_PIPE_NOT_AVAILABLE
[2005/05/12 13:07:31, 2] smbd/server.c:exit_server(571)
  Closing connections
[2005/05/12 13:10:50, 2] auth/auth.c:check_ntlm_password(312)
  check_ntlm_password:  Authentication for user [root] -> [root] FAILED
with error NT_STATUS_PIPE_NOT_AVAILABLE
[2005/05/12 13:10:50, 2] smbd/server.c:exit_server(571)
  Closing connections


If I had to guess, there is a problem with samba authenticating against
the domain, but that does not make sense, because several other servers
are authenticating against the same domain without any trouble

Any suggestions would be greatly appreciated

TIM






More information about the users mailing list