+ 0 Votes For the sake of clarity seanferd 3 years ago "Windows machines" (or whatever) - not "PCs". PC is a (now loose) term for architecture, not a term for "MS Windows". Thing about ping is that you will never know how the server name was resolved. Try nslookup to see if DNS is resolving, or nbtstat, or whatnot. You might want to try Wireshark or some other packet capture and analysis utility to see what is happening between the Windows boxes and the server. If this is a sudden appearance of a problem, review the latest Windows Updates for possible clues. + 0 Votes WINS (?) r_widell 3 years ago I'd be most suspicious of the WINS configuration as the none of the machines need it (in this scenario), but the Windows machines will try harder to use it if it's configured. Some of the various "net" commands from a Windows CLI should help you determine where the problem lies (and the Samba docs will be a real aid here). I confess I've never tried using any of the "netsh" commands against a Samba server, so I don't know if they'll work or not. The brute force approach would be to first ensure that the OS level on the Mac and Linux workstations are all less than that of the server. You may have a workstation ignoring the "domain" aspect and setting itself up as the Master Browser due to an incorrect OS level setting. + 0 Votes Some questions r_widell 3 years ago Are the Windows machines making a wired or wireless connection? My wife's WinXP Home machine frequently loses it's mind when attached over a wireless connection, while my Ubuntu laptop keeps working fine using the same AP. Is the Samba server also acting as a PDC in a Windows Domain or is it just a Workgroup-style sharing situation? That info may help to hone in on where the errors are occurring.