On Thu, Apr 27, 2006 at 06:41:43AM +0200, Christian Perrier wrote: > Quoting Steve Langasek ([EMAIL PROTECTED]):
> > I disagree with this assessment. If the server is browseable by Windows > > clients without error, and it can't be browsed by Samba, I see no reason to > > think this is not a Samba bug. > Hmm, well, I seem to remember cases where such browsing problems had > various external causes, some of which being completely outside of > samba's scope. > Actually, this is quite accumulated experience: browsing problems on > Windows networks are usually caused by broken Windows machines > setups...which maybe does not apply in that case. In this instance, the submitter was quite specific that the problem related to virtual servers on a Windows machine, and showed an error message that could only result from successful resolution (browsing) of a server name followed by a failure upon attempting to connect to it. If other windows clients are able to make a connection to the machine "sroserve" without getting such an error, then this definitely looks like a samba-specific bug. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
