Bug 483917 - samba fails to publish shares
samba fails to publish shares
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: samba (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Simo Sorce
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-04 03:56 EST by morgan read
Modified: 2009-02-05 08:50 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-02-05 08:50:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
smb.conf (9.81 KB, application/octet-stream)
2009-02-04 03:56 EST, morgan read
no flags Details

  None (edit)
Description morgan read 2009-02-04 03:56:49 EST
Created attachment 330837 [details]
smb.conf

Description of problem:
Set up shares of home directories and they are not displayed in gnome "Windows Network" yet shares from other machines are; selecting "Places > Connect to Server... > Windows share" and entering requisite information mounts those same directories not displayed.

Version-Release number of selected component (if applicable):
samba-3.2.7-0.25.fc10.i386

How reproducible:
Set up shares

Steps to Reproduce:
1. Set up shares
2. Attempt to browse shares via gnome "Windows Network"
3. Unable to do so
  
Actual results:
Shares NOT visible in gnome "Windows Network"

Expected results:
Shares visible in gnome "Windows Network"

Additional info:
smb.conf attached
Comment 1 Simo Sorce 2009-02-04 09:01:39 EST
Please verify the firewall is setup to allow the "samba client" rule.
Comment 2 morgan read 2009-02-04 21:35:42 EST
Yup,
Open Samba Client 137/udp 138/udp
system-config-firewall.py 1.2.13
Thanks
Comment 3 morgan read 2009-02-04 22:01:05 EST
Seems to have appeared now...

Perhaps resolution to this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=483923
solves this bug?
.
.
.

Note You need to log in before you can comment on or make changes to this bug.