Re: [Samba] Abnormal Windows behaviour with Samba
Chris Smith-16 wrote: I believe modern Windows versions use DNS first, then WINS. IMO, a modern Samba network should have both WINS and DNS resolution for all systems. I really agree about the WINS part - that's why I prefer enabling this functionality in Samba. It seems that it resolves a lot of issues in general. However what do you mean by DNS? Do you believe that I have to install Bind on my server and create zone files for each terminal? If this is the case, what would be a sample configuration for each zone? I have only installed Bind for real domains.. Can I create zones without TLDs (i.e. just PC-01)? If a fake TLD is needed, do I have to call the server's share using this TLD (i.e. \\server.tld\share\whatever)? Explain this please, as it's a little confusing to me... Chris Smith-16 wrote: Use ipconfig /all on the clients to make sure they are configured as you believe. Check your WINS database and see if all the systems are properly registered. Check the nmbd logs for possible clues (such as making sure your server is the local master browser). Check the smbd logs for possible clues (network issues, etc.). Check (by temporarily disabling) that some AV software on the clients isn't causing an issue (automatic updates for one can take a lot of system time at boot). I will do so in the afternoon and I will post the results. Chris Smith-16 wrote: Also when using user and group names in smb.conf it's a good idea (and mandatory in some cases) to fully qualify the names as DOMAINNAME\username or DOMAINNAME\groupname, ex: X-NET\x-admin, X-NET\erebus, etc. Is this also the case if Samba is not configured as a PDC, but just as a workgroup server? I don't use a domain in my configuration. Thank you very much for your response, I really appreciate it. Best regards, Konstantinos -- View this message in context: http://www.nabble.com/Abnormal-Windows-behaviour-with-Samba-tf3821648.html#a10892296 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Abnormal Windows behaviour with Samba
James Lockie wrote: Do they both allow system folders to be on the network though? Yes, I can confirm that I have accomplish doing so on both XP Home and XP Pro (SP1 and above). There is no difference between the two on this issue, they both allow that change either by registry setting or even using the Tweak UI for XP (downloadable from the Microsoft Powertoys homepage). So the issue I believe that it has to do with the name resolving (WINS, NetBIOS, DNS?). Correct me if I am wrong, but Windows use by default the NetBIOS over TCP/IP (that is the default setting in TCP/IP properties I suppose). When using WINS, shouldn't they know each computer's name for good at the boot time? -- View this message in context: http://www.nabble.com/Abnormal-Windows-behaviour-with-Samba-tf3821648.html#a10876746 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Abnormal Windows behaviour with Samba
Gary Dale wrote: A question I would have is can you track down exactly when the problem occurs? You said it doesn't happen all of the time. Are there certain conditions that you can identify about when the problem occurs? Does it happen only on certain account, machines, when the server or network is busy...? Thank you for the response. No, really, there are no certain conditions that this problem occurs (or I am unable to find any relation between different factors that may affect this). After trying all possible solutions (like using WINS support in Samba, using registry hacks on Windows side to have a synchronous boot and so on), I 've thought that this problem might occur because of network or server traffic/load. However this is not true. The server is a double Xeon with 1024 MB RAM and two SATAII 500 GB HDs (Ubuntu server installed). However it has very low traffic in general and on it only Samba, DHCPd, proxy and socks servers are installed (with little use of all of them actually). I am pretty sure now, that the problem has to do with the way Windows does name resolves. And I need a little help on this from you guys. From what I know, Windows uses by default NetBIOS over TCP/IP (which is the default option by the way). So I have the following questions: 1) If NetBIOS is working well between Samba and XP, why I had the same problem a year ago in another similar installation? The problem then disappeared when I used WINS support (which didn't solved the same problem on this new installation now). 2) When using WINS, Windows are trying to find the NetBIOS name first and if they fail they then ask the WINS server? What is the exact sequence of the name resolving in Windows? 3) I know that there is a way to change that name resolving method on Linux. Is there a way to change it on Windows too? I.e. to ask first the WINS, then DNS, then LMHOSTS etc. 4) A friend of mine told me that WINS is no longer supported (or even working?) after Windows 2000 (and of course in XP). He said it has been totally replaced by DNS now. Maybe using a local DNS server would be the final solution to all this? Is this right and logical? Thank you all in advance for your help, Konstantinos -- View this message in context: http://www.nabble.com/Abnormal-Windows-behaviour-with-Samba-tf3821648.html#a10876927 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Abnormal Windows behaviour with Samba
James Lockie wrote: The solution to a critical situation is to pay someone for support. Don't be ironic please. Nobody of my colleagues know how to find a workaround on this. So I am pretty sure that even if I paid them, the result would be the same. If you can help me, I am grateful. If you need money to do so, just let me know. Regards, -- View this message in context: http://www.nabble.com/Abnormal-Windows-behaviour-with-Samba-tf3821648.html#a10876930 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Abnormal Windows behaviour with Samba
tanstaafl_bh wrote: Whether it is the cause of this problem or not, these are no longer necessary - and indeed, it is recommended to NOT use them, in modern l=kernels (2.6+)... So the correct would be only TCP_NODELAY which is the default, right? Apart from that (which was already tested and gave exact the same results) do you have any other suggestion to make? I don't know what to do and the situation is critical... Thank you all in advance, -- View this message in context: http://www.nabble.com/Abnormal-Windows-behaviour-with-Samba-tf3821648.html#a10826175 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Abnormal Windows behaviour with Samba
Hello all, I am using Samba v3.0.24 on an Ubuntu Server system as a fileserver for 30 pcs. Samba is working nice but I face a problem that I can't tell if it is because of Samba or Windows. Let me explain: On the Windows terminals (XP SP2) I have changed the special folders settings in registry, so as to redirect them to samba shares instead of local folders. Among the folders I have changed is the desktop folder, the start menu and the startup folder, which now point to i.e. \\server\share\folder. I have also setup a WINS server in Samba, I have configured my dhcpd to distribute the WINS ip to the clients, I have added Netbios on Windows and I have even added the samba's ip and hostname to the Windows' HOSTS file manually. The problem is that when Windows boot, the don't find the samba share to read the special folders' contents from there. This problem occur some times, not always. The server always work good, and even if Windows fail to read the special 'network' folders, if I kill explorer.exe and re-run it, it succeeds on reading them with no problem. A friend of mine told me that I have also to setup the SyncForeground policy in Windows, so as to delay Windows on boot and have a synchronous network reading. I did so, but it didn't do the trick as well... The only 'abnormal' thing in my Samba's configuration is this line: socket options = IPTOS_LOWDELAY TCP_NODELAY SO_RCVBUF=4096 SO_SNDBUF=4096 ...which I use for tuning purposes. However, even if I leave the default (TCP_NODELAY) I have exactly the same abnormal behaviour, so I don't think that this is to blame. Do you have any suggestion to make (either in Samba's configuration or a tweak on the Windows side) so as to overcome this problem? Thank you very much in advance, Konstantinos P.S. Here is my Samba configuration: [global] unix charset = ISO-8859-7 workgroup = X-NET server string = %h fileserver browseable = No interfaces = 192.168.1.0/255.255.255.0, 127.0.0.1 bind interfaces only = Yes update encrypted = Yes null passwords = Yes passdb backend = smbpasswd:/etc/samba/smbpasswd passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . syslog = 0 log file = /var/log/samba/log.%m smb ports = 139 max xmit = 65535 time server = Yes deadtime = 15 socket options = IPTOS_LOWDELAY TCP_NODELAY SO_RCVBUF=4096 SO_SNDBUF=4096 load printers = No show add printer wizard = No preferred master = Yes domain master = Yes wins support = Yes ldap ssl = no panic action = /usr/share/samba/panic-action %d invalid users = root hosts allow = 192.168.1.0/255.255.255.0, 127.0.0.1 hosts deny = ALL [x-net] comment = X-Net Essentials path = /s3/x-net valid users = x-admin, x-net, erebus admin users = x-admin, erebus read list = x-net write list = x-admin, erebus -- View this message in context: http://www.nabble.com/Abnormal-Windows-behaviour-with-Samba-tf3821648.html#a10819479 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
