Steve Langasek <[EMAIL PROTECTED]> writes: > 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.
That's what I thought, even if someone does consider the Windows box mis-configured (but I expect it was done following Microsoft doc and I'm surprised if such Windows virtual (web) servers are actually that rare). It was obviously a waste of time to report it to Debian and I doubt there's any point keeping it open at this stage. I no longer work there and don't know whether the problem occurs with the current smbclient, though I might be able to get someone to check. Shouldn't such reports be forwarded `upstream' if Debian maintainers can't deal with them? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
