Bug 113091 - Can't access network computer from windows client
Summary: Can't access network computer from windows client
Alias: None
Product: Fedora
Classification: Fedora
Component: samba   
(Show other bugs)
Version: 1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-08 13:57 UTC by Need Real Name
Modified: 2014-08-31 23:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-24 20:24:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2004-01-08 13:57:46 UTC
Description of problem:
Network computers disapper from my network windows. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Dennis DeDonatis 2004-05-05 14:57:54 UTC
I'm assuming this is the same issue I saw.

For some reason, Windows 98 and Windows XP computers (the only two 
tested) could no longer access the Fedora Core 1 SMB server a few 
days after the update from Red Hat 9.  I upgraded to samba-3.0.2-
7.FC1 immediately following the install, so I did not test with the 
orignial FC1 version.  The FC1 linux SMB server is set to be the WINS 
server for the network.  Changing dns proxy = yes from no "fixed" it. 
Every computer on this small network is in the /etc/hosts file.
Upgrading to samba-3.0.3-1.i386.rpm from Samba.org didn't make any 
difference (dns proxy = no means no access to the SMB server).

Comment 2 Marius Andreiana 2005-11-03 10:19:02 UTC
Is this still an issue with recent samba version / FC4?

Comment 3 John Thacker 2006-04-24 20:24:12 UTC
FC1 is now the responsibility of Fedora Legacy.  Since this is not
a security bug, and the reporter has not responded by a long time to
a request for updated info, closing.  If the problem occurs in
FC5, please feel free to reopen.

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