How to force WINS name resolution point to virtual Hamachi IP's?Get windows to resolve domain less names via...
What should you do if you miss a job interview (deliberately)?
why `nmap 192.168.1.97` returns less services than `nmap 127.0.0.1`?
Which one is correct as adjective “protruding” or “protruded”?
Is a bound state a stationary state?
Did arcade monitors have same pixel aspect ratio as TV sets?
Loading commands from file
What is the evidence for the "tyranny of the majority problem" in a direct democracy context?
Why do compilers behave differently when static_cast(ing) a function to void*?
Calculating Wattage for Resistor in High Frequency Application?
GraphicsGrid with a Label for each Column and Row
Argument list too long when zipping large list of certain files in a folder
What should you do when eye contact makes your subordinate uncomfortable?
In Qur'an 7:161, why is "say the word of humility" translated in various ways?
Is it improper etiquette to ask your opponent what his/her rating is before the game?
Strong empirical falsification of quantum mechanics based on vacuum energy density
Why did the EU agree to delay the Brexit deadline?
Multiplicative persistence
On a tidally locked planet, would time be quantized?
It grows, but water kills it
The IT department bottlenecks progress. How should I handle this?
Why Shazam when there is already Superman?
How to indicate a cut out for a product window
Fear of getting stuck on one programming language / technology that is not used in my country
Is there a single word describing earning money through any means?
How to force WINS name resolution point to virtual Hamachi IP's?
Get windows to resolve domain less names via dhcpwill name resolution fail if WINS server falls down?OpenVPN and DNS. How to?Windows 2003 DNS Server Can't Resolve Specific URLName resolution in an IPv6 network without a DNS serverWINS Server interfering with DNS?Domain computer cannot resolve internal hostnames, but nslookup canPinging server replies back with incorrect IP addressHow to find all hostnames (even laptops that aren't currently on the network) on a network?WINS server for inter-VLAN NetBIOS resolution
Our salesforces are using their laptop either on the LAN or on the road. They connect to the office with hamachi (gateway mode).
When outside, laptops could ping office servers using the virtual IP given by hamachi (10.40...) but not using their windows name. Windows names are resolved to local IP (192.168...).
There is no problem to ping and connect to printers and linux based NAS, so I think it's WINS related.
Laptops are rebooted before attempting to connect form outside. Does this flush wins cache ?
I think laptop sends a wins query that is answered by one of the computers on LAN which give the name table it has (with 192.167... IPs).
How to solve this issue ?
I've tried to flush wins cache using both netbt and ipconfig /flushdns, with no luck.
domain-name-system wins hamachi
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Our salesforces are using their laptop either on the LAN or on the road. They connect to the office with hamachi (gateway mode).
When outside, laptops could ping office servers using the virtual IP given by hamachi (10.40...) but not using their windows name. Windows names are resolved to local IP (192.168...).
There is no problem to ping and connect to printers and linux based NAS, so I think it's WINS related.
Laptops are rebooted before attempting to connect form outside. Does this flush wins cache ?
I think laptop sends a wins query that is answered by one of the computers on LAN which give the name table it has (with 192.167... IPs).
How to solve this issue ?
I've tried to flush wins cache using both netbt and ipconfig /flushdns, with no luck.
domain-name-system wins hamachi
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Our salesforces are using their laptop either on the LAN or on the road. They connect to the office with hamachi (gateway mode).
When outside, laptops could ping office servers using the virtual IP given by hamachi (10.40...) but not using their windows name. Windows names are resolved to local IP (192.168...).
There is no problem to ping and connect to printers and linux based NAS, so I think it's WINS related.
Laptops are rebooted before attempting to connect form outside. Does this flush wins cache ?
I think laptop sends a wins query that is answered by one of the computers on LAN which give the name table it has (with 192.167... IPs).
How to solve this issue ?
I've tried to flush wins cache using both netbt and ipconfig /flushdns, with no luck.
domain-name-system wins hamachi
Our salesforces are using their laptop either on the LAN or on the road. They connect to the office with hamachi (gateway mode).
When outside, laptops could ping office servers using the virtual IP given by hamachi (10.40...) but not using their windows name. Windows names are resolved to local IP (192.168...).
There is no problem to ping and connect to printers and linux based NAS, so I think it's WINS related.
Laptops are rebooted before attempting to connect form outside. Does this flush wins cache ?
I think laptop sends a wins query that is answered by one of the computers on LAN which give the name table it has (with 192.167... IPs).
How to solve this issue ?
I've tried to flush wins cache using both netbt and ipconfig /flushdns, with no luck.
domain-name-system wins hamachi
domain-name-system wins hamachi
asked Oct 10 '13 at 7:38
bokanbokan
152212
152212
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Why on earth are you using WINS in a modern environment (and one with Linux in it!), and Hamachi in a professional one? You are asking for disaster.
My advice to you would be to dispose of WINS post-haste (even before Hamachi). Do not rely on it. Use DNS, with authenticated dynamic updates.
To make your environment coherent, set your DNS suffixes appropriately in DHCP so that there isn't a distinction between a "windows name" (really you mean netbios name) and a DNS name.
Following this, do not multihome all your servers onto the VPN, if that's what you're doing (I'm not sure from your question). Instead, route your LAN at the VPN hosts' default gateway, and route your VPN at the LAN hosts' default gateway. Then, when hosts get the correct IP for a host from DNS (which they can cache unto eternity if they like), they will be able to communicate with it.
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f545051%2fhow-to-force-wins-name-resolution-point-to-virtual-hamachi-ips%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Why on earth are you using WINS in a modern environment (and one with Linux in it!), and Hamachi in a professional one? You are asking for disaster.
My advice to you would be to dispose of WINS post-haste (even before Hamachi). Do not rely on it. Use DNS, with authenticated dynamic updates.
To make your environment coherent, set your DNS suffixes appropriately in DHCP so that there isn't a distinction between a "windows name" (really you mean netbios name) and a DNS name.
Following this, do not multihome all your servers onto the VPN, if that's what you're doing (I'm not sure from your question). Instead, route your LAN at the VPN hosts' default gateway, and route your VPN at the LAN hosts' default gateway. Then, when hosts get the correct IP for a host from DNS (which they can cache unto eternity if they like), they will be able to communicate with it.
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
add a comment |
Why on earth are you using WINS in a modern environment (and one with Linux in it!), and Hamachi in a professional one? You are asking for disaster.
My advice to you would be to dispose of WINS post-haste (even before Hamachi). Do not rely on it. Use DNS, with authenticated dynamic updates.
To make your environment coherent, set your DNS suffixes appropriately in DHCP so that there isn't a distinction between a "windows name" (really you mean netbios name) and a DNS name.
Following this, do not multihome all your servers onto the VPN, if that's what you're doing (I'm not sure from your question). Instead, route your LAN at the VPN hosts' default gateway, and route your VPN at the LAN hosts' default gateway. Then, when hosts get the correct IP for a host from DNS (which they can cache unto eternity if they like), they will be able to communicate with it.
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
add a comment |
Why on earth are you using WINS in a modern environment (and one with Linux in it!), and Hamachi in a professional one? You are asking for disaster.
My advice to you would be to dispose of WINS post-haste (even before Hamachi). Do not rely on it. Use DNS, with authenticated dynamic updates.
To make your environment coherent, set your DNS suffixes appropriately in DHCP so that there isn't a distinction between a "windows name" (really you mean netbios name) and a DNS name.
Following this, do not multihome all your servers onto the VPN, if that's what you're doing (I'm not sure from your question). Instead, route your LAN at the VPN hosts' default gateway, and route your VPN at the LAN hosts' default gateway. Then, when hosts get the correct IP for a host from DNS (which they can cache unto eternity if they like), they will be able to communicate with it.
Why on earth are you using WINS in a modern environment (and one with Linux in it!), and Hamachi in a professional one? You are asking for disaster.
My advice to you would be to dispose of WINS post-haste (even before Hamachi). Do not rely on it. Use DNS, with authenticated dynamic updates.
To make your environment coherent, set your DNS suffixes appropriately in DHCP so that there isn't a distinction between a "windows name" (really you mean netbios name) and a DNS name.
Following this, do not multihome all your servers onto the VPN, if that's what you're doing (I'm not sure from your question). Instead, route your LAN at the VPN hosts' default gateway, and route your VPN at the LAN hosts' default gateway. Then, when hosts get the correct IP for a host from DNS (which they can cache unto eternity if they like), they will be able to communicate with it.
answered Oct 10 '13 at 7:47
Falcon MomotFalcon Momot
22.7k104879
22.7k104879
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
add a comment |
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
By WINS, I mean Windows 7 default name resolution, I must be wrong. Can you please tell me wich protocol is used by default to resolve names on Windows 7 ?
– bokan
Oct 10 '13 at 8:03
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
Typically, it will use DNS preferentially, along its search path of default suffixes, and failing that, NBNS/WINS (which is a legacy protocol). If you are using NBNS at all, it is because DNS isn't working, basically. Check out what's happening using nslookup on one of the nonworking clients, and possibly traceroute too.
– Falcon Momot
Oct 10 '13 at 8:42
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
And don't forget about LLMNR.
– joeqwerty
Oct 10 '13 at 15:30
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f545051%2fhow-to-force-wins-name-resolution-point-to-virtual-hamachi-ips%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