I'm a beginner with Linux who for the first time ever with Fedora Core 1 was able to finally get things working so that the Linux and Windows boxes saw each other and could access files on each other.

The Linux box was even able to use the printers hanging off of the Windows machines. I only used the Gnome applets.

No more. After I used the "upgrade" option on the Core 2 disks, now although the Windows machines can still log on to the Linux box, the Linux machine can't see or access them. I've even done a complete Core 2 re-install but no joy.

Although the Linux box can access the Internet through the router, it doesn't even show itself when you click on the Network Servers icon. I successfully installed SWAT but when I try to use it it gives me a "connection refused" message.

I've been all over the menus and can't see anything else to do. Any suggestions?

Thanks for any help you can provide.

Just to update on my efforts to get the Linux box to see the Windows boxes. I get all green on the service startup poll when Fedora starts up as well as at shutdown. SMB client and services and NMB are among them.

Also, I find that the Linux box can ping the Windows boxes. but when I try to use the smb:// URL format to connect to the Windows boxes it either says that I don't have sufficient permissions or that it can't display all of the items.

Since I made no changes from before when it was all working under Core 1, I'm at a complete loss.

Thanks for any help you can provide.

hi

post ur smb.conf here
is it the same s u had in fedora 1
also can u smbmount ur windows shares

regards

Thanks for the feedback.

I've continued to wrestle with this. What I've noticed is that when I try to log into the Windows machines from the Linux box, I get a "you do not have sufficient permissions" message but it looks like I do when I check the properties.

I don't know what the smbconf file looked like for Core 1 since I was able to get everything running from the Gnome desktop apps.

Here's the smbconf file for Core 2. I've made only a couple of changes like workgroup=WORKGROUP.

Any suggestions you could make would be appreciated.

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

# server string is the equivalent of the NT Description field
server string = Samba Server

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

# 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.
# 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
password server = None
security = SHARE
winbind use default domain = no
[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
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


[vulcan]
path = /home/vulcan
writeable = yes

I've tried using SWAT but cannot get it to run. I keep getting a "The connection was refused when attempting to contact localhost:901". A poster on one of the other forums here said that meant that SWAT was not installed but it keeps telling that it is installed. I've checked the xinetd and it says "disable=no".

I don't know how to manually do an smb mount from the command line.

I should also add that I have 2 Windows machines and the Linux box all connected to a Linksys router along with the cable modem using the standard settings.

Thanks again.

hi

for smbmount
run
#smbclient -L <ip address of windows machine>

this will show u the shares of the windows machine

to mount that share in say /mnt/smb
#smbclient '//192.168.0.20/document' /mnt/smb

if it asks for password
press enter
192.168.0.20==ip ad of windows machine
document is the windows share
use it as it shows mounted(case sensitive)

also have u editied this smb.conf???i could not find any setings in the upper half of ur smb.conf

regards

gaurav

The only change that I made to the file was the workgroup=WORKGROUP line right at the top.

I wasn't able to mount any shares from the command line. I got a long error message about malformed smbconfig file.

I'm beginning to wonder if I should just go back to Core 1 where things worked from the Gnome applets on the desktop.

hi
to test ur smb.conf file,i.. to see if everything down there is fine should run
"testparm"

also i am not sure of this but there has been a option of selinux(security enhanced linux) in FC2 may b that also be some problem, but that should not stop to mount windows shares in linux

post ur command and messges here

regards

Masand,

Thanks for your help on this. The more I thought about it today, the more I thought that my last comment was the way to go. So I'm going to wipe Core 2 from the machine and re-install Core 1. Once I get everything set up, this time I will copy the various config files like smbconf to a floppy. Then I'll try upgrading to Core 2 and copy in the config files that I saved from Core 1. Maybe that'll work.

wait!!!!!!!!!!!!!

before doing anthing like that i advice u have a look again at a feature called the selinux feature(security enhanced linux)
which is new in FC2
even if u bring ur smb.conf from FC1 then too it might not work
my smb.conf which was working in RH9.0 gave me some problems here and that have not finished yet,but i hav not migrated back to redhat

also it i keep a backup of all the important configuration files which help me in migration reinstallation

i too havn't ben abl to figure abot more on this
there is a command
"selinuxenabled" and "selinuxdisabled"

give it a try
regards