Unable to view Window shares because of the default resolve order

[Matthew Nuzum]

Binary package hint: samba

When trying to browse windows shares I consistently fail. As it turns out the DNS server for my network tries to be helpful and hijacks unresolvable names.

In /etc/samba/smb.conf I had to set 'name resolve order = lmhosts wins bcast host'

Once I did this (put host last) smbclient allows me to see the share and after a reboot I can use nautilus to access shared resources.

For the record, I use opendns by choice. It provides some services that I like such as blocking adult websites, blocking phishing sites and auto-correcting mis-typed domains. However I understand that some people's ISPs do the same thing and they don't get a choice as to which dns server they use. Therefore one could make a case that the default search order should be set as mentioned above.

For example, doing a google search shows tutorial websites like this: http://lifehacker.com/software/linux-101/mount-a-windows-shared-folder-in-linux-288033.php
where they explain that to access shared resources you have to do so using the IP address of the computer. I think this reflects poorly on Ubuntu and gives it the image of it being difficult to use.

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

samba 3.0.26a-1ubuntu2.3

[Chuck Short (zulcss)]

Hi Matthew,

This seems to be like a common problem while running with Samba and OpenDNS. Are you running your own DNS server or using your ISP?

Thanks
chuck

[Matthew Nuzum (newz)]

Neither, I'm using opendns. I've told my router to use opendns and it uses dhcp to give it's (the router's) IP address to all of the hosts on the network. Then it forwards those DNS requests to opendns.

[Chuck Short (zulcss)]

Hi Matthew,

This seems to be an issue with opendns. http://www.youbitch.org/blog/2008/mar/06/opendns-a-word-of-warning/

chuck

[beniwtv (beniwtv-deactivatedaccount)]

I'm with Matthew on this. This should be fixed ASAP.

I'm using OpenDNS as well, and have the same problem. I'm was using OpenDNS in Gutsy and never had that problem. Strange...
This is not an issue with OpenDNS. Imagine all the users coming from windows expecting their shares to work with Hardy...

But I agree, it's probably not something affecting much users...

[Chuck Short (zulcss)]

You might want to have to look at this then:

http://www.opendns.com/support/article/164

Its not something we can fix easily.

chuck

[beniwtv (beniwtv-deactivatedaccount)]

Hi chuck,

The problem is, in Windows I can access the shares just fine, despite of using OpenDNS. In Gutsy, this also worked without problems.

So this is definitively a regression, and should be fixed. Besides, the fix is quite simple, as outlined in the post above.

Just my 0.02$

[Steve Melvin (jinksys)]

Once I applied the fix in the first post, all my samba woes were gone. I have a similar setup: A router that uses opendns and sets hosts dns accordingly. The opensuse box and windows boxes in the house could use the shares fine, however 8.04 couldn't browse or use shares, except by using an explicit IP address.

[Steve Melvin (jinksys)]

I'd also like to add that this is not only a prolem with OPENDNS but any DNS server that redirects bad requests. For example, my ISP is Charter Communications and they redirect all bad lookups to their "helpful" search page, so in essence all lookups are good. This confuses some apps, like samba. So this is not just an OPENDNS issue, but could be an issue for anyone who uses an ISP that redirects bad lookups.

[Jayson Reis (jaysonsantos2003)]

Hello people, to fix that, just create an account if You don't have and go to Dashboard then Advanced Settings and uncheck "Enable typo correction".
However you cannot use filters from opendns.

[Fabián Rodríguez (magicfab)]

Perhaps this should also involve Network Manager (if in a Desktop context) to warn about it when this setting is detected.

Use case 1:
Matt want to use OpenDNS. He follows easy instruction to set it up.

Later the same week he browses his network in nautilus.

Nautilus makes a DNS request that should return an error, the DNS request doesn't fail, meaning the DNS server is configured in a way that requires changing resolve order in /etc/samba/smb.conf. A warning is presented asking to confirm the change, and explaining why it's needed, or asking to contact the system admin.

Matt enters his password, the directive is changed, the samba service is restarted and expected functionality is restored.

Use case 2:
Matt want to use OpenDNS. He follows easy instruction to set it up.

Nautilus (or else) opens immediately and makes a DNS request that should return an error, the DNS request doesn't fail, meaning the DNS server is configured in a way that requires changing resolve order in /etc/samba/smb.conf. A warning is presented asking to confirm the change, and explaining why it's needed, or asking to contact the system admin.

Does that sound crazy ? I am told such DNS setups can be checked, I only use the "make request, if it doesn't fail it's breaking local DNS" analogy for illustration purposes.