Help setting up Samba

From: Richard Bell (rbell01824_at_earthlink.net)
Date: 05/19/04 

Date: Wed, 19 May 2004 14:51:56 GMT

I'm installing a Fedora Core 1 based machine into an existing network
of Windows machines. The network configuration includes a number of
Win 95, Win 98, Win NT, Win 2000, and Win XP machines. Many of the
machines come and go depending on current projects. The existing
machines are all connected to a LinkSys Router configured as a DHCP
server that, in turn, provides access to the Internet for all the
machines. The network does not use either a WINS or DNS server,
instead depending on broadcast name resolution.

I installed Fedora from a DVD that came with "The Complete Reference,
Red Hat Enterprise Linux & Fedora Edition", Osborne, RIchard Petersen
and Ibrahim Haddad. The install went cleanly with no apparent events.

>From the new Fedora machine, F1, I can access the Internet via
Mozilla, ping various Internet sites by name, etc. All seems well
relative to the Internet. From F1 I'm able to
ping the existing Win machines by IP address, I can not ping them by
name (get an "unknown host" error message). Additionally, when I do a
"net view" from the Win machines, I do not see F1, the Fedora machine.
I am, however, able to ping it from any of the Win machines by IP.
The Linksys DHCP active IP table shows all the machine names,
including the Fedora F1 machine, and their IPs. I understand that this
is expected behavior and thus believe that all is fundamentally well
with the network configuration.

I've installed Samba 3.0.2-7 and configured it with a test share as
follows (smb.conf):

[global]
    workgroup = cindy
    server string = Fedora 1 WS
    password server = None
    security = SHARE
[test]
    comment = For testing only, please
    path = /usr/local/samba/tmp
    writeable = yes
    guest ok = yes

I restart the Samba server using the redhat tool. The directory exist
and has two test files cleverly named 'one' and 'two'.

Subsequently, I can see the Fedora F1 machine on the network on WinXP
and Win98 machines from either 'net view' or by browsing out of
explorer. When I attempt to access the share on XP with explorer I
get an error "\\F1 is not accessible." I get similar errors on the
Win98 machines.

On all the machines I've created a login account with the same name
and password.

This is all new ground for me, and I'm unsure how to proceed. Based
on what I've read, I think that at this point I should be able to see
and access the 'test' share. Can anyone point me toward what I've
done wrong or provide any clues for diagnosing the problem?

Thanks.

R

Relevant Pages

  • Re: OSD restore phase problem
    ... Is it possible that the machines aren't getting a DHCP address fast enough? ... Often this can represent a network configuration issue (on Cisco switches, ... >> will report it can not connect to the installation package on the ...
    (microsoft.public.sms.tools)
  • Re: OT: Network bandwidth monitor
    ... One of the machines is using all the ... network policy and policing the firewall is beyond my hands. ... something and using our bandwidth. ... Should I install iftop and run it on the fedora box? ...
    (Fedora)
  • Re: OT: Network bandwidth monitor
    ... I have a network of 20 hosts and all of them are windows machines ... bandwidth and seem to be uploading something. ... Should I install iftop and run it on the fedora box? ...
    (Fedora)
  • trends in fedora
    ... I've just installed Fedora 9 on my laptop, and unfortunately a few things are getting worse in Fedora. ... Network management has always been awkward on Fedora and with Fedora 9 it's getting much worse. ... I used it to log into other F8 machines locked away in difficult to get at racks. ...
    (Fedora)
  • Re: trends in fedora
    ... I've just installed Fedora 9 on my laptop, ... Network management has always been awkward on Fedora and with Fedora 9 it's ... How am I going to remotely administer my machines? ... GDM was functional, well behaved and stable in Fedora 8. ...
    (Fedora)