Cannot see FC5 Samba shares from windows, Please help....PART1

[billydv]

From Fedora Core 5 I can read and write to any of the 5 networked computers in my household that are running windows xp but from a windows machine no matter what I do, when I click on the Fedora core 5 computer ( which shows up as a member of the workgroup), I get an error message saying that the computer is not accessible. I am including my Samba config files and hopefully someone can help me figure this out.

etc/samba/samba.config

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

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

# server string is the equivalent of the NT Description field
server string = Fedora Core 5

# 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

# 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
root = administrator

# 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/log.smbd

# 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>

# 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*success fully*

# 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_SNDBUF=8192 SO_RCVBUF=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
; security = user
; encrypt passwords = yes
guest ok = yes
guest account = billydv
; security = user
; encrypt passwords = yes
; security = user
; encrypt passwords = yes
; security = user
restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto
username map = /etc/samba/smbusers
; encrypt passwords = yes
; encrypt passwords = yes
; security = user

# 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 ==============================
[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

[billydv]

This is the rest of the configuration files......



# 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


[billydv]
comment = home
path = /home/billydv
writeable = yes
valid users = billydv

[My Documents]
path = /MyDocuments/My Documents
writeable = yes


__________________________________________________ ___________

etc/samba/smbpsswrd

billydv:500088BE23E9C0C718AAD3B435B51404EE:75717 1B84160CCA37078DEA21A7869B9:[U ]:LCT-447F5E1D:

__________________________________________________ ___________

etc/samba/smbusers

# Unix_name = SMB_name1 SMB_name2 ...
root = administrator admin
nobody = guest pcguest smbguest
billydv = Billy DeVincentis

__________________________________________________ ___________

Please, if anyone also knows which services need to be running in order for this to work it would really be helpful, Thanks in advance.

[OLD_GOLD]

I've been having samba problems with FC3 and FC5. I cannot get a printer on my windows box to work on either although it worked fine on FedHat8.

I have also been umable to mount shares on the windows box onto the linux box using FC5. However I did find that if you make sure smb and lisa are running you can see them in konqueror and drag and drop files between the boxes. These are not started by default, you could modify the appropriate startup script to run them at startup but you can also start them manually. You could use the service program but I run the required files directly.

/etc/rc.d/init.d/smb restart
/etc.rc.d/init.d/lisa restart

If the service is not already running you will get a failed indication when the program tries to stop them for restart, that is no problem as long as the service starts ok.

[kentek]

Originally Posted by OLD_GOLD

I've been having samba problems with FC3 and FC5. I cannot get a printer on my windows box to work on either although it worked fine on FedHat8.

I have also been umable to mount shares on the windows box onto the linux box using FC5. However I did find that if you make sure smb and lisa are running you can see them in konqueror and drag and drop files between the boxes. These are not started by default, you could modify the appropriate startup script to run them at startup but you can also start them manually. You could use the service program but I run the required files directly.

/etc/rc.d/init.d/smb restart
/etc.rc.d/init.d/lisa restart

If the service is not already running you will get a failed indication when the program tries to stop them for restart, that is no problem as long as the service starts ok.

I too have issues with Samba and XP win pcs. The big item is always password encryption. Make sure your samba encrypts passwords. Also, I make user name/passwords same on both systems.
And here is an item I just found and implemented:
On windose server from Admin tools open Domain Security Settings
Go to Local Policies the Security Options
Scroll down to entry Microsoft network server: Digitally sign communications (always) and set this ti Disabled. (the default is always and it will say not implemented)
Then from dos win do gpupdate.
Thing should get better.

[wshawn]

This issue is usually the shares having share authentication instead of user authentication. You want them encrypted (tho, lets not get into the 0 bit encryption conversation)

Search this forum for my name and look for the how to on how to set up the shares in 6 steps.

[OLD_GOLD]

Thanks wshawn, I tried the things you suggested, using kde instead of gnome so things are in slightly different places but was able to make all the changes you suggested. Here's the problem:

nfs is running, smb is running, lisa is running.

I can see the shares on the konqueror gui and drag and drop files between the two computers (FC5 and win98), I can see all the shares and the shared printer on the windows box using smbclient.

when I try to mount a win98 share onto my linux box I get the message:
unknown filesystem type smbfs

I have been able to mount these share with other distros, RedHat8 and FC3 most recently.

My real concern is accessing the printer on the windows box (hp laserjet1000), because of a situation with drivers I want to keep it there instead of moving it to the linux box. It worked fine with RedHat8, I have been using rather unsatisfactory workarounds with both fedora versions.

[wshawn]

http://forums.fedoraforum.org/showpo...3&postcount=11

Check out jeremyreed's explanation on the different network protocols.

Personally, I typically do not use Lisa as I forbid file shares on any Windows machines as it is easy to get past the security of (and the Home editions can never be turned off). Also, in the Admin Printing are you directly connecting to the share (Networked WIndows SMB) for the printer or are you trying to mount it...

[OLD_GOLD]

Thanks again wshawn.
I never used lisa because I never needed it but it is the only way that I have been able to transfer files to the windows box with FC3 and FC5. I am behind a hardware firewall in my router so I'm not too concerned about it and I only use the windows box for some things I was given that don't have linux support. (A scanner, GPS and a lot of files in AmiPro format that I do need and would be a major time committment to convert to Open Office because they contain graphics, tables, equations and other things that the format conversion programs just don't handle.

I am using CUPS to print to my printers and I am set up to print directly to the printer, as I have always done,

Here is part of the cups error log generated when I try to print a test page from the printer manager to the shared laserjet 1000 on the windows box:

D [19/Jul/2006:21:19:37 -0400] [Job 917] renderer PID kid4=12569
D [19/Jul/2006:21:19:37 -0400] [Job 917] renderer command: foo2zjs-wrapper -P -r600x600 -p1 -s7 -m1 -d1 -n1 -I0
D [19/Jul/2006:21:19:37 -0400] [Job 917] renderer return value: 16777215
D [19/Jul/2006:21:19:37 -0400] [Job 917] renderer received signal: 16777215
D [19/Jul/2006:21:19:37 -0400] [Job 917] KID3 exited with status 1
D [19/Jul/2006:21:19:37 -0400] [Job 917] Renderer exit stat: 1
D [19/Jul/2006:21:19:37 -0400] [Job 917] Process dying with "The renderer command line returned an unrecognized error code 16777215.", exit stat: 1
D [19/Jul/2006:21:19:37 -0400] [Job 917] error: No such file or directory (2)
D [19/Jul/2006:21:19:37 -0400] [Job 917] The renderer command line returned an unrecognized error code 16777215.
E [19/Jul/2006:21:19:37 -0400] [Job 917] Unable to connect to CIFS host, will retry in 60 seconds...
D [19/Jul/2006:21:19:37 -0400] [Job 917] Renderer process finished

I think the 'exit stat 1' is a normal exit with the error code ignored, and I think that the problem is that it tries to connect to a CIFS host, which I understand win98 is not.

The error log shows several attempts to connect using CIFS, all fail. CUPS and the print manager show the file was sent.

Thanks again for your interest, I do appreciate it.

[bjw]

I can not access the FC shares from XP either

I have also installed Firestarter and checked the IP tables allow ports 137-139 445 are open for SMB

XP STILL complains about access permissions

tried several SMB cfgs and still the same problems

What I have also noticed after installing fire starter is that security level not longer work appears it may have been over written by Fire starter or something??

If you find out anything please let me know I am lost on this one

[bjw]

I can not access the FC shares from XP either

I have also installed Firestarter and checked the IP tables allow ports 137-139 445 are open for SMB

XP STILL complains about access permissions

tried several SMB cfgs and still the same problems

What I have also noticed after installing fire starter is that security level not longer work appears it may have been over written by Fire starter or something??

If you find out anything please let me know I am lost on this one

[wshawn]

Sounds to me like you have an SELinux Issue.

I wrote a How To for FC4, some of the content has slightly changed in the SELinux details, but that should get you running:

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

Currently I just allow everything, and depending on your needs, you can set up accordingly.

I created each person I want to have backup space on the server an account, so when they log into sama it sends them to their own folder (/home/user)

In that folder I create a soft link to /home/repo so they each can have read only access to our local files.

At first you may want to disable Selinux in regards to samba. I personally refuse to run with SELinux turned off in a networked environment.

[bjw]

Fire starter seems to have over written files for security level configuration. I can not longer get access to Selinux. I think this maybe a problem.
How would I reload security level files again is there a yum up date?

[wshawn]

I currently use shorewall, but when I used FireStarter a couple years ago, it only messed with routing tables, iptables, etc.

It never messed with SELinux.


You don´t see a SELinux option under the Administration menu?


I don´t have a fedora box in front of me at the minute. Only a Centos 5 server, and a couple of ubuntus.

[bjw]

correct

Security level hour glass appears then nothing??

[bjw]

I have installed FC 4 there is no admin menu that I can see