Samba 5670: session setup failed: ERRDOS ?

fatum112 · 11-20-2005, 04:52 PM

hi,

I'm currently trying to setup a network with linux fedora core 3, to a windows XP computer...
i have read about 10 diferent samba tutorials... didn't help a thing...

i can do the ping test.. on my linux computer aswel as a ping test from my linux computer to my windows XP computer...

but when i try to connect localy with the code:

mount //localhost/tmp /mnt

i get at first the password: ( i don't know which password it should be so i tryed root, and a samba user password...)

i get the error message:

5670: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
SMB connection failed

i'm trying to setup the network for 2 days now...
i formated my linux 4 different times...

my smb.conf is as followed:

Quote:

#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = workgroup

# server string is the equivalent of the NT Description field
server string = test

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
; printing = cups

# This option tells cups that the data has already been rasterized
cups options = raw

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# all log information in one file
# log file = /var/log/samba/smbd.log

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details.
; security = user
# Use password server option only with security = server
; password server = <NT-Server-Name>

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no

#============================ Share Definitions ==============================
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = no
; encrypt passwords = yes
username map = /etc/samba/smbusers
; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; guest ok = no
; guest account = nobody
; guest ok = no
; guest account = nobody
[homes]
comment = Home Directories
browseable = no
writeable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
printable = yes

# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; read only = yes
; write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765

[html]
comment = Downloads
path = /var/www/html
writeable = yes
browseable = yes
valid users = fatum

i really hope one of you guys can help me out.. because i'm stuck at this point...
(and also with 2 hardware factors, listed at hardware forum...)

Thanks already,
Fatum

sirkware · 11-21-2005, 12:51 AM

Try this command:

mount -t smbfs -o username=tridge,password=foobar //fjall/test /data/test

Just substitute the (smb) username and (smb) password you want to use. As well as the path of the mount.

Hope this helps.

fatum112 · 11-21-2005, 04:07 AM

thanks... now that works to.. but i'm still unable to connect from windows to linux...
since a short time i can now connect to my self and connect to the windows computer...

but the windows computer says nothing except an error, (it should give a login screen)

so what can i do now?

sirkware · 11-21-2005, 04:17 AM

Be sure your shared directories/folders has proper permissions for users to have access to. If you have SELinux installed, you need to remove the protection of SELinux to smbd and nmbd daemons.

sirkware · 11-21-2005, 04:21 AM

Read my post here on how to disable SELinux on smbd and nmbd daemons:

http://www.linuxquestions.org/questi...5&pagenumber=1

fatum112 · 11-21-2005, 06:10 AM

big problems there... there is no samba branche to bee seen in the policy of SElinux....

so what is wrong when it's no where to be seen?...

got msn or something?
it's maybe easyer to talk that way...

regards,
Fatum

sirkware · 11-21-2005, 06:53 PM

Have you tried adding your users to smbpasswd? If not, add the users that you want to have access to your computer. The command is:

smbpasswd -a <user>

If still that doesnt work and if you are using KDE then I recommend you to install smb4k. Here's the link about this http://www.linuxquestions.org/questi...07#post1957207

Hope that helps.

fatum112 · 11-21-2005, 08:06 PM

hi,

Itś not my linux computer who can't browser trough the network... my linux computer can read,wright, etc perfectly, but my windows computer can only see my linux computer...

When i try to acces my computer (linux) with the windows machine... it tells me acces denied...

when it should promt for a login name & password..

so i can't even try to login, because it doesn't connect...

so i do not think smb4k will help me, because of what i read... it seems to me that it helps linux computers browser on windows computers... i just need the oppesit of that..

sirkware · 11-21-2005, 11:29 PM

In your smb.conf, uncomment following line:

security = user

Then, add yours users to the smbpasswd (refer to my previous post).

Restart your smb daemon. Try if that would work.

fatum112 · 11-22-2005, 07:20 PM

didn't work...

for some strainge reason my linux server is not accepting a connection to be made trough a windows network...
maybe the problem is that my network is working trough a router... on windows this is no problem...
i just use a "workgroup" and no domain...

i'm sure i got something wrong... because a wile ago my linux allowed the windows computer to the login screen... (at that time i didn't have my settings configured correctly..so i couldn't login...)

is there something what i'm doing wrong?

Firewall Is on (because the network is on the same card as my internet connection)
SElinux protection is on (but no samba to allow at SElinux)

Linux Fedora core 3:
Can connect to my self,
can connect to the windows XP computers by browsering the ip: 192.168.2.103

Windows XP:
Connecting with the local network browser
Trying to enter server --> error

With run:
\\192.168.2.102
Trying to connect ---> Error

All errors are before the login screen appears
it says that i'm not allowed to acces the computer and i need to contact the systems administrator...

I really want to step over to linux, but before i do i first need to configure everything correctly... the main part is the network because this computer contains storage places over the network and printer for the hole network..

sirkware · 11-22-2005, 09:36 PM

Maybe this would help:

http://forums.fedoraforum.org/archiv...p/t-29224.html

sirkware · 11-22-2005, 09:41 PM

Also this one:

http://www.fedoraforum.org/forum/showthread.php?t=28596

sirkware · 11-23-2005, 06:23 PM

Quote:

Originally posted by fatum112
didn't work...

for some strainge reason my linux server is not accepting a connection to be made trough a windows network...
maybe the problem is that my network is working trough a router... on windows this is no problem...
i just use a "workgroup" and no domain...

i'm sure i got something wrong... because a wile ago my linux allowed the windows computer to the login screen... (at that time i didn't have my settings configured correctly..so i couldn't login...)

is there something what i'm doing wrong?

Firewall Is on (because the network is on the same card as my internet connection)
SElinux protection is on (but no samba to allow at SElinux)

Linux Fedora core 3:
Can connect to my self,
can connect to the windows XP computers by browsering the ip: 192.168.2.103

Windows XP:
Connecting with the local network browser
Trying to enter server --> error

With run:
\\192.168.2.102
Trying to connect ---> Error

All errors are before the login screen appears
it says that i'm not allowed to acces the computer and i need to contact the systems administrator...

I really want to step over to linux, but before i do i first need to configure everything correctly... the main part is the network because this computer contains storage places over the network and printer for the hole network..

Sorry about yesterday. Just got something to do and I was not able to look into your samba more closely. Anyway, what I noticed is that your encrypt passwords and smb passwd file settings are commented. I believe you have overwritten it just like the security settings. Can you uncomment that too? Also, I have tried looking at your smbpasswd file and I got an error. I can't read it (maybe different language) but I think it's an error Im getting when trying to view the file.

fatum112 · 11-24-2005, 02:29 AM

hi,
no problem about yesterday, i was just wondering what you where doing (since i didn't get a responce)
well i looked up smbpasswd in /etc/samba/smbpasswb didn't look like mutch i can read lol, load of X in the file and now and then a port and a name... (like mysql, devcot, etc)

the smbpasswb file in /usr/bin i couldn't open (i think that was obviouse)

and uncomment the settings... i think i can once i know where to look for

but i tried uncommenting the encryped passwords... but then i got the same error as i did before..

sirkware · 11-24-2005, 03:29 AM

Quote:

Originally posted by fatum112
well i looked up smbpasswd in /etc/samba/smbpasswb didn't look like mutch i can read lol, load of X in the file and now and then a port and a name... (like mysql, devcot, etc)

the smbpasswb file in /usr/bin i couldn't open (i think that was obviouse)

Sample smbpasswd should look like this:

sirkware:500:9018223315434E45AAD3B435B51404EE:431DB41B840987572B2889BE33CDCAC6:[U ]:LCT-430021C1:
nobody:99

8B69FD820088D121AA818381E4E281B:55FB63AFD507BC96D7E8BE73FBC74DE0:[U ]:LCT-43004470: