On 11/2/07, Anonomouse <[EMAIL PROTECTED]> wrote: > I suspect that your ISP is verizon. I started having this very problem > around the same time that you made your initial post. Anyway, I have > identified part of the problem and have begun to work on a resolution.
Why yes, it is. > This appears to be a flaw in the design of Samba, as Windows does not appear > to have this issue. However, there seems to be a workaround. Add the > following line to the [Global] section of your smb.conf: > > name resolve order = bcast > > This directs Samba to resolve IP address only by broadcasting requests > across your subnet and should resolve your issue. > > Let me know if you have success. Once the cache timed out (I tested once with the original config, to make sure the problem still existed), this worked like a charm. You rock! I, and my weekly backups, thank you. -- Michael A. Marsh http://www.umiacs.umd.edu/~mmarsh http://mamarsh.blogspot.com http://36pints.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
