I've discovered that, on my SuSE 10.0, 10.1 and 10.2 PCs, samba accesses my DNS servers on internet to resolve the ip address before looking locally.
This has proved no problem for me until my ISP decided to change the way it handled DNS "errors" (ie it stopped telling us customers when a lookup failed). Now samba doesn't work on my LAN unless I explicitly give it ip addresses. I can show this is the case, since samba runs quite happily if I unplug my router from the phone line. I suspect it is not a router problem, since my Windows 98 PC is completely unaffected. I've been using this to move files about, but it's not a good long-term solution. I can (and am) altering my scripts to explicitly specify ip addresses, but this too only goes so far. Clearly, I've got samba incorrectly specified somehow. What should I be doing to stop it looking in the wrong place for an ip address? -- All the best, John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba