Windows-7 cannot resolve a Samba share via the .local domain name (but can resolve for TCP/IP)
I have a Linux Samba server and a Windows-7 computer running on a local network. I installed Avahi on the server and Apple's Bonjour (version 2) on the Windows computer.
The Windows computer can resolve the server's address myserver.local for TCP/IP communication, such as ping or ssh connections. But it's not able to see or find the the server in the list of shares. Also typing \myserver.localshare doesn't find it. Using it with the IP address as in \1.2.3.4share works. So apparently the problem is when converting the name to its address for the purpose of working with shares.
I tried to test it with nslookup myserver.local, it prints
Server: <my provider's DNS server name>
Address: <my provider's DNS server address>
and fails with Non-existent domain.
Does this point in the right direction? Is it possible to somehow add resolving the .local domain when working with this kind of services? Or what else could I do to debug the issue?
windows-7 networking samba bonjour zeroconf
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
add a comment |
I have a Linux Samba server and a Windows-7 computer running on a local network. I installed Avahi on the server and Apple's Bonjour (version 2) on the Windows computer.
The Windows computer can resolve the server's address myserver.local for TCP/IP communication, such as ping or ssh connections. But it's not able to see or find the the server in the list of shares. Also typing \myserver.localshare doesn't find it. Using it with the IP address as in \1.2.3.4share works. So apparently the problem is when converting the name to its address for the purpose of working with shares.
I tried to test it with nslookup myserver.local, it prints
Server: <my provider's DNS server name>
Address: <my provider's DNS server address>
and fails with Non-existent domain.
Does this point in the right direction? Is it possible to somehow add resolving the .local domain when working with this kind of services? Or what else could I do to debug the issue?
windows-7 networking samba bonjour zeroconf
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
I'd look at the Windows side hosts file and look for syntax and misconfiguration in that file.
– linuxdev2013
Dec 27 '18 at 20:18
If you open Windows Explorer and type in the UNC path, \myserver.local, do you see the share listed there? If not, you have a misconfiguration on the SAMBA side or in your authentication mechanisms. Your statement that it works via IP but not via DNS name smacks of Kerberos issues--but that assumes you're using Kerberos in the first place and are requiring it in your SAMBA config. On Windows, when Kerberos fails or is not used, NTLM is tried. Kerberos requires DNS so you may be seeing Kerberos rejection using hostname where NTLM is working via IP -- a packet capture would be definitive.
– thepip3r
Dec 27 '18 at 22:11
add a comment |
I have a Linux Samba server and a Windows-7 computer running on a local network. I installed Avahi on the server and Apple's Bonjour (version 2) on the Windows computer.
The Windows computer can resolve the server's address myserver.local for TCP/IP communication, such as ping or ssh connections. But it's not able to see or find the the server in the list of shares. Also typing \myserver.localshare doesn't find it. Using it with the IP address as in \1.2.3.4share works. So apparently the problem is when converting the name to its address for the purpose of working with shares.
I tried to test it with nslookup myserver.local, it prints
Server: <my provider's DNS server name>
Address: <my provider's DNS server address>
and fails with Non-existent domain.
Does this point in the right direction? Is it possible to somehow add resolving the .local domain when working with this kind of services? Or what else could I do to debug the issue?
windows-7 networking samba bonjour zeroconf
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
I have a Linux Samba server and a Windows-7 computer running on a local network. I installed Avahi on the server and Apple's Bonjour (version 2) on the Windows computer.
The Windows computer can resolve the server's address myserver.local for TCP/IP communication, such as ping or ssh connections. But it's not able to see or find the the server in the list of shares. Also typing \myserver.localshare doesn't find it. Using it with the IP address as in \1.2.3.4share works. So apparently the problem is when converting the name to its address for the purpose of working with shares.
I tried to test it with nslookup myserver.local, it prints
Server: <my provider's DNS server name>
Address: <my provider's DNS server address>
and fails with Non-existent domain.
Does this point in the right direction? Is it possible to somehow add resolving the .local domain when working with this kind of services? Or what else could I do to debug the issue?
windows-7 networking samba bonjour zeroconf
windows-7 networking samba bonjour zeroconf
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
asked Dec 27 '18 at 19:53
Petr PudlákPetr Pudlák
95741534
95741534
I'd look at the Windows side hosts file and look for syntax and misconfiguration in that file.
– linuxdev2013
Dec 27 '18 at 20:18
If you open Windows Explorer and type in the UNC path, \myserver.local, do you see the share listed there? If not, you have a misconfiguration on the SAMBA side or in your authentication mechanisms. Your statement that it works via IP but not via DNS name smacks of Kerberos issues--but that assumes you're using Kerberos in the first place and are requiring it in your SAMBA config. On Windows, when Kerberos fails or is not used, NTLM is tried. Kerberos requires DNS so you may be seeing Kerberos rejection using hostname where NTLM is working via IP -- a packet capture would be definitive.
– thepip3r
Dec 27 '18 at 22:11
add a comment |
I'd look at the Windows side hosts file and look for syntax and misconfiguration in that file.
– linuxdev2013
Dec 27 '18 at 20:18
If you open Windows Explorer and type in the UNC path, \myserver.local, do you see the share listed there? If not, you have a misconfiguration on the SAMBA side or in your authentication mechanisms. Your statement that it works via IP but not via DNS name smacks of Kerberos issues--but that assumes you're using Kerberos in the first place and are requiring it in your SAMBA config. On Windows, when Kerberos fails or is not used, NTLM is tried. Kerberos requires DNS so you may be seeing Kerberos rejection using hostname where NTLM is working via IP -- a packet capture would be definitive.
– thepip3r
Dec 27 '18 at 22:11
I'd look at the Windows side hosts file and look for syntax and misconfiguration in that file.
– linuxdev2013
Dec 27 '18 at 20:18
I'd look at the Windows side hosts file and look for syntax and misconfiguration in that file.
– linuxdev2013
Dec 27 '18 at 20:18
If you open Windows Explorer and type in the UNC path, \myserver.local, do you see the share listed there? If not, you have a misconfiguration on the SAMBA side or in your authentication mechanisms. Your statement that it works via IP but not via DNS name smacks of Kerberos issues--but that assumes you're using Kerberos in the first place and are requiring it in your SAMBA config. On Windows, when Kerberos fails or is not used, NTLM is tried. Kerberos requires DNS so you may be seeing Kerberos rejection using hostname where NTLM is working via IP -- a packet capture would be definitive.
– thepip3r
Dec 27 '18 at 22:11
If you open Windows Explorer and type in the UNC path, \myserver.local, do you see the share listed there? If not, you have a misconfiguration on the SAMBA side or in your authentication mechanisms. Your statement that it works via IP but not via DNS name smacks of Kerberos issues--but that assumes you're using Kerberos in the first place and are requiring it in your SAMBA config. On Windows, when Kerberos fails or is not used, NTLM is tried. Kerberos requires DNS so you may be seeing Kerberos rejection using hostname where NTLM is working via IP -- a packet capture would be definitive.
– thepip3r
Dec 27 '18 at 22:11
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388223%2fwindows-7-cannot-resolve-a-samba-share-via-the-local-domain-name-but-can-resol%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388223%2fwindows-7-cannot-resolve-a-samba-share-via-the-local-domain-name-but-can-resol%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'd look at the Windows side hosts file and look for syntax and misconfiguration in that file.
– linuxdev2013
Dec 27 '18 at 20:18
If you open Windows Explorer and type in the UNC path, \myserver.local, do you see the share listed there? If not, you have a misconfiguration on the SAMBA side or in your authentication mechanisms. Your statement that it works via IP but not via DNS name smacks of Kerberos issues--but that assumes you're using Kerberos in the first place and are requiring it in your SAMBA config. On Windows, when Kerberos fails or is not used, NTLM is tried. Kerberos requires DNS so you may be seeing Kerberos rejection using hostname where NTLM is working via IP -- a packet capture would be definitive.
– thepip3r
Dec 27 '18 at 22:11