Bug 2037 - failure since update from 3.0.2a-5.1
Summary: failure since update from 3.0.2a-5.1
Status: CLOSED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: libsmbclient (show other bugs)
Version: 3.0.5
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-15 06:06 UTC by dave dewey
Modified: 2005-08-24 10:18 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dave dewey 2004-11-15 06:06:14 UTC
Running Suse Linux 9.1 on x86PC with KDE GUI.  a review of the history: with
original load of Samba 3.0.2a-5.1 the Network Browser worked perfectly.  It
would show all available networked windows PCs as expected immediately when
opened (Network Browser>Windows Network)  After update to new version of Samba
(sorry I lost the exact version number, I think it was 3.0.5 but not sure) I got
the error "Unknown error condition in stat: Network is unreachable".  Able to
Ping WINXPPCs, but no SMB functionality with command line or GUI.  Today I
updated Samba to new ver. 3.0.8-1.1.1, and now I have full command line smb
functionality back, but still get the "Unknown error condition in stat: Network
is unreachable" message in the browser as before.  But one new difference..  now
if I click on "OK" button in the error message window, then enter the resource
address I want (example "smb://winxppc/sharename") in the Konqueror address bar
window I get the "Authorization Dialog" Window.  I can then enter username & PW
and see the icons for the shared directory on the winxppc.  I can find no way to
browse the workgroup in Konqueror as I could under ver 3.0.2a-1.1.1
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-02-07 09:28:44 UTC
please retest 3.0.11 (rpms available on samba.org) and reopen 
if you find the iussue still exists.
Comment 2 Gerald (Jerry) Carter (dead mail address) 2005-08-24 10:18:16 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.