I have a Linux server running Ubuntu Lucid that will eventually be used as an FTP server, with Samba installed so that the files on it can be accessed by machines on our Windows network. It works well from every machine but one, our Windows Server 2003 domain controller. Punching \\machinename into Explorer on the Win2k3 DC box causes the following error dialog box to instantly appear:
Windows cannot find '\\machinename'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search.
Every other Windows machine on this network can browse the Ubuntu server no problems.
I don't think it's a DNS problem as the Windows box is able to connect to FTP on the Ubuntu server by name just fine, and the DNS server has both A and PTR records for the Ubuntu server.
I tried looking through the Event Viewer logs on the Windows machine and could not see any relevant events. There are two logs in /var/log/samba/ for the Windows machine, one with its name and the other with its IP address. They are both empty.
Other relevant details:
- I'm almost a complete newb when it comes to Linux, so please assume I know nothing.
- The Ubuntu server is not joined to any domain.
- The DC does not have any trouble browsing the shares of other Windows servers. There are no other servers here running any *nix variety.
- The same error appears when trying via IP (i.e.
\\<ip>)
Any help with this would be greatly appreciated 🙂
Update
I have increased the Samba logging level to try and sort out what's going on. In amongst the hundreds of lines I noticed that the DC is attempting to authenticate using the name of the account I'm logged in with, which I would expect, but when that fails it's not asking me for a different account like I would normally expect of Windows. I used the Stored Usernames and Passwords Control Panel applet to enter a username and password, which the DC appears to try using, but it still fails. I wonder if this problem could have something to do with the tighter security settings on the DC as compared to the other domain joined machines?
Update 2
I have now noticed that other 2003 machines that are not DCs have trouble accessing the server too – they produce the same error message. The small number of XP machines have no trouble, and the Vista/7 machines I've tried have no trouble, but servers running 2003 are all unable to connect to the Ubuntu server.
Best Answer
Community poke!
Depending on the encryption/authentication options you have selected, I'd guess it could be one of:
LMCompatibilityLevel http://technet.microsoft.com/en-us/library/cc960646.aspx
or Send Unencrypted Passwords http://technet.microsoft.com/en-us/library/cc782276(WS.10).aspx
or as it's a DC, Network Client: Sign Communications settings
Compare these settings between working/nonworking machines, see what you get?