Cannot access Windows machines by Name over PPTP VPN but can access ip address
I have a PPTP VPN Incoming Network Connection setup on a windows 8.1 machine which is where I have all my computers setup on a local intranet (say machine X, Y and Z)
I VPN into the Windows 8.1 machine from my Windows 7 machine using the microsoft VPN software. Works fine, I can access the internet resolve all internet DNS' etc. I see my ISP's DNS assigned to my Windows 7 VPN adapter along with a remote local intranet 192.168.x.x IP address.
Now I can ping the Windows 8.1 machine by NAME and IP ADDRESS. But I cannot Ping/Resolve ANY other machine on the remote local intranet by NAME (x, Y or Z), ONLY by IP ADDRESS.
Why can't I resolve a machine name on my remote network via the VPN connection? I don't have a Domain server or WINS server setup. I've tried disabling the firewall on both sides, no difference. I've tried using the remote machine as the DNS server (forced) but it doesn't work either. I've tried settings the remote network router (running tomato + dnsmasq) as the DNS for the windows 7 vpn adapter, still doesn't work.
The only thing I can think of is that the VPN doesn't allow NetBIOS to work. Any thoughts here.
windows vpn dns netbios
asked Mar 10 '15 at 20:07
rboy
255138
add a comment |
I have a PPTP VPN Incoming Network Connection setup on a windows 8.1 machine which is where I have all my computers setup on a local intranet (say machine X, Y and Z)
I VPN into the Windows 8.1 machine from my Windows 7 machine using the microsoft VPN software. Works fine, I can access the internet resolve all internet DNS' etc. I see my ISP's DNS assigned to my Windows 7 VPN adapter along with a remote local intranet 192.168.x.x IP address.
Now I can ping the Windows 8.1 machine by NAME and IP ADDRESS. But I cannot Ping/Resolve ANY other machine on the remote local intranet by NAME (x, Y or Z), ONLY by IP ADDRESS.
Why can't I resolve a machine name on my remote network via the VPN connection? I don't have a Domain server or WINS server setup. I've tried disabling the firewall on both sides, no difference. I've tried using the remote machine as the DNS server (forced) but it doesn't work either. I've tried settings the remote network router (running tomato + dnsmasq) as the DNS for the windows 7 vpn adapter, still doesn't work.
The only thing I can think of is that the VPN doesn't allow NetBIOS to work. Any thoughts here.
windows vpn dns netbios
asked Mar 10 '15 at 20:07
rboy
255138
add a comment |
I have a PPTP VPN Incoming Network Connection setup on a windows 8.1 machine which is where I have all my computers setup on a local intranet (say machine X, Y and Z)
I VPN into the Windows 8.1 machine from my Windows 7 machine using the microsoft VPN software. Works fine, I can access the internet resolve all internet DNS' etc. I see my ISP's DNS assigned to my Windows 7 VPN adapter along with a remote local intranet 192.168.x.x IP address.
Now I can ping the Windows 8.1 machine by NAME and IP ADDRESS. But I cannot Ping/Resolve ANY other machine on the remote local intranet by NAME (x, Y or Z), ONLY by IP ADDRESS.
Why can't I resolve a machine name on my remote network via the VPN connection? I don't have a Domain server or WINS server setup. I've tried disabling the firewall on both sides, no difference. I've tried using the remote machine as the DNS server (forced) but it doesn't work either. I've tried settings the remote network router (running tomato + dnsmasq) as the DNS for the windows 7 vpn adapter, still doesn't work.
The only thing I can think of is that the VPN doesn't allow NetBIOS to work. Any thoughts here.
windows vpn dns netbios
asked Mar 10 '15 at 20:07
rboy
255138
I have a PPTP VPN Incoming Network Connection setup on a windows 8.1 machine which is where I have all my computers setup on a local intranet (say machine X, Y and Z)
I VPN into the Windows 8.1 machine from my Windows 7 machine using the microsoft VPN software. Works fine, I can access the internet resolve all internet DNS' etc. I see my ISP's DNS assigned to my Windows 7 VPN adapter along with a remote local intranet 192.168.x.x IP address.
Now I can ping the Windows 8.1 machine by NAME and IP ADDRESS. But I cannot Ping/Resolve ANY other machine on the remote local intranet by NAME (x, Y or Z), ONLY by IP ADDRESS.
Why can't I resolve a machine name on my remote network via the VPN connection? I don't have a Domain server or WINS server setup. I've tried disabling the firewall on both sides, no difference. I've tried using the remote machine as the DNS server (forced) but it doesn't work either. I've tried settings the remote network router (running tomato + dnsmasq) as the DNS for the windows 7 vpn adapter, still doesn't work.
The only thing I can think of is that the VPN doesn't allow NetBIOS to work. Any thoughts here.
windows vpn dns netbios
windows vpn dns netbios
asked Mar 10 '15 at 20:07
rboy
255138
asked Mar 10 '15 at 20:07
rboy
255138
asked Mar 10 '15 at 20:07
rboy
255138
asked Mar 10 '15 at 20:07
rboy
255138
asked Mar 10 '15 at 20:07
rboy
255138
255138
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Okay I finally found website that answers my question - but if ANYONE has any alternate ideas please post here.
According to this website:
https://kb.meraki.com/knowledge_base/resolving-netbios-names-over-client-vpn
It is NOT possible to resolve NetBIOS names over a VPN. Quoting:
NetBIOS name resolution is a layer-2 broadcast based name discovery protocol. Layer-2 broadcasts do not traverse layer-3 boundaries such as the Client VPN interface on an MX.
The only way to use NetBIOS over a VPN is to setup a WINS server. Quoting:
WINS is service that provides centralized name resolution of NetBIOS hostnames. NetBIOS clients register their hostnames on the WINS server and other NetBIOS clients query the WINS server to resolve NetBIOS names.
To allow hosts that utilize NetBIOS names to find network resources over Client VPN, specify the IP address of a WINS server in the Client VPN configuration. This is done using the WINS setting on the Configure > Client VPN page.
answered Mar 11 '15 at 6:15
rboy
255138
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
add a comment |
When you setup a VPN connection, there are 2 methods you can use.
Make all internet traffic go over the vpn, which makes everything work, but as a result, both your internet and the internet on the VPN side is used for single data.
Use only directed traffic to go over the vpn, the rest over your normal vpn. Uses much less resources on the VPN side, but as a sidenote, things like DNS don't work properly.
If you go to the VPN connection on the client side, edit it, go to the network tab, double click the IPv4, then check Use remote gateway it will make it work like 1. Uncheck = 2.
Best practice for VPN connections is to use IP address, not the Hostname. Or not use VPN but remote desktop.
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
1
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
add a comment |
With the Windows server VPN, on the client side, putting the same class address ip on the network card resolve the issue, DNS and NETBIOS is ok
answered Dec 12 at 4:12
user972199
1
add a comment |
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%2f887941%2fcannot-access-windows-machines-by-name-over-pptp-vpn-but-can-access-ip-address%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Okay I finally found website that answers my question - but if ANYONE has any alternate ideas please post here.
According to this website:
https://kb.meraki.com/knowledge_base/resolving-netbios-names-over-client-vpn
It is NOT possible to resolve NetBIOS names over a VPN. Quoting:
NetBIOS name resolution is a layer-2 broadcast based name discovery protocol. Layer-2 broadcasts do not traverse layer-3 boundaries such as the Client VPN interface on an MX.
The only way to use NetBIOS over a VPN is to setup a WINS server. Quoting:
WINS is service that provides centralized name resolution of NetBIOS hostnames. NetBIOS clients register their hostnames on the WINS server and other NetBIOS clients query the WINS server to resolve NetBIOS names.
To allow hosts that utilize NetBIOS names to find network resources over Client VPN, specify the IP address of a WINS server in the Client VPN configuration. This is done using the WINS setting on the Configure > Client VPN page.
answered Mar 11 '15 at 6:15
rboy
255138
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
add a comment |
Okay I finally found website that answers my question - but if ANYONE has any alternate ideas please post here.
According to this website:
https://kb.meraki.com/knowledge_base/resolving-netbios-names-over-client-vpn
It is NOT possible to resolve NetBIOS names over a VPN. Quoting:
NetBIOS name resolution is a layer-2 broadcast based name discovery protocol. Layer-2 broadcasts do not traverse layer-3 boundaries such as the Client VPN interface on an MX.
The only way to use NetBIOS over a VPN is to setup a WINS server. Quoting:
WINS is service that provides centralized name resolution of NetBIOS hostnames. NetBIOS clients register their hostnames on the WINS server and other NetBIOS clients query the WINS server to resolve NetBIOS names.
To allow hosts that utilize NetBIOS names to find network resources over Client VPN, specify the IP address of a WINS server in the Client VPN configuration. This is done using the WINS setting on the Configure > Client VPN page.
answered Mar 11 '15 at 6:15
rboy
255138
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
add a comment |
Okay I finally found website that answers my question - but if ANYONE has any alternate ideas please post here.
According to this website:
https://kb.meraki.com/knowledge_base/resolving-netbios-names-over-client-vpn
It is NOT possible to resolve NetBIOS names over a VPN. Quoting:
NetBIOS name resolution is a layer-2 broadcast based name discovery protocol. Layer-2 broadcasts do not traverse layer-3 boundaries such as the Client VPN interface on an MX.
The only way to use NetBIOS over a VPN is to setup a WINS server. Quoting:
WINS is service that provides centralized name resolution of NetBIOS hostnames. NetBIOS clients register their hostnames on the WINS server and other NetBIOS clients query the WINS server to resolve NetBIOS names.
To allow hosts that utilize NetBIOS names to find network resources over Client VPN, specify the IP address of a WINS server in the Client VPN configuration. This is done using the WINS setting on the Configure > Client VPN page.
answered Mar 11 '15 at 6:15
rboy
255138
Okay I finally found website that answers my question - but if ANYONE has any alternate ideas please post here.
According to this website:
https://kb.meraki.com/knowledge_base/resolving-netbios-names-over-client-vpn
It is NOT possible to resolve NetBIOS names over a VPN. Quoting:
NetBIOS name resolution is a layer-2 broadcast based name discovery protocol. Layer-2 broadcasts do not traverse layer-3 boundaries such as the Client VPN interface on an MX.
The only way to use NetBIOS over a VPN is to setup a WINS server. Quoting:
WINS is service that provides centralized name resolution of NetBIOS hostnames. NetBIOS clients register their hostnames on the WINS server and other NetBIOS clients query the WINS server to resolve NetBIOS names.
To allow hosts that utilize NetBIOS names to find network resources over Client VPN, specify the IP address of a WINS server in the Client VPN configuration. This is done using the WINS setting on the Configure > Client VPN page.
answered Mar 11 '15 at 6:15
rboy
255138
answered Mar 11 '15 at 6:15
rboy
255138
answered Mar 11 '15 at 6:15
rboy
255138
answered Mar 11 '15 at 6:15
rboy
255138
255138
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
add a comment |
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
The only solution I found was a use a different VPN software that allows for Broadcast packet forwarding or use a DNS server that also registers the name of the local machines on the network and use that DNS server for the remote clients
– rboy
Mar 11 '15 at 8:17
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
Setting manually WINS server worked for me. thanks
– Riccardo
May 21 '17 at 16:41
add a comment |
When you setup a VPN connection, there are 2 methods you can use.
Make all internet traffic go over the vpn, which makes everything work, but as a result, both your internet and the internet on the VPN side is used for single data.
Use only directed traffic to go over the vpn, the rest over your normal vpn. Uses much less resources on the VPN side, but as a sidenote, things like DNS don't work properly.
If you go to the VPN connection on the client side, edit it, go to the network tab, double click the IPv4, then check Use remote gateway it will make it work like 1. Uncheck = 2.
Best practice for VPN connections is to use IP address, not the Hostname. Or not use VPN but remote desktop.
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
1
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
add a comment |
When you setup a VPN connection, there are 2 methods you can use.
Make all internet traffic go over the vpn, which makes everything work, but as a result, both your internet and the internet on the VPN side is used for single data.
Use only directed traffic to go over the vpn, the rest over your normal vpn. Uses much less resources on the VPN side, but as a sidenote, things like DNS don't work properly.
If you go to the VPN connection on the client side, edit it, go to the network tab, double click the IPv4, then check Use remote gateway it will make it work like 1. Uncheck = 2.
Best practice for VPN connections is to use IP address, not the Hostname. Or not use VPN but remote desktop.
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
1
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
add a comment |
When you setup a VPN connection, there are 2 methods you can use.
Make all internet traffic go over the vpn, which makes everything work, but as a result, both your internet and the internet on the VPN side is used for single data.
Use only directed traffic to go over the vpn, the rest over your normal vpn. Uses much less resources on the VPN side, but as a sidenote, things like DNS don't work properly.
If you go to the VPN connection on the client side, edit it, go to the network tab, double click the IPv4, then check Use remote gateway it will make it work like 1. Uncheck = 2.
Best practice for VPN connections is to use IP address, not the Hostname. Or not use VPN but remote desktop.
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
When you setup a VPN connection, there are 2 methods you can use.
Make all internet traffic go over the vpn, which makes everything work, but as a result, both your internet and the internet on the VPN side is used for single data.
Use only directed traffic to go over the vpn, the rest over your normal vpn. Uses much less resources on the VPN side, but as a sidenote, things like DNS don't work properly.
If you go to the VPN connection on the client side, edit it, go to the network tab, double click the IPv4, then check Use remote gateway it will make it work like 1. Uncheck = 2.
Best practice for VPN connections is to use IP address, not the Hostname. Or not use VPN but remote desktop.
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
answered Mar 10 '15 at 21:00
LPChip
35.2k54984
35.2k54984
1
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
add a comment |
1
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
1
1
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
That doesn't address the question - I know what you're saying and I'm using a single channel directed VPN, but I've tried both. The issue is that it won't resolve computer names on the remote network. I want to be able to see all the computer on my remote LAN through network places and that isn't happening
– rboy
Mar 11 '15 at 6:10
add a comment |
With the Windows server VPN, on the client side, putting the same class address ip on the network card resolve the issue, DNS and NETBIOS is ok
answered Dec 12 at 4:12
user972199
1
add a comment |
With the Windows server VPN, on the client side, putting the same class address ip on the network card resolve the issue, DNS and NETBIOS is ok
answered Dec 12 at 4:12
user972199
1
add a comment |
With the Windows server VPN, on the client side, putting the same class address ip on the network card resolve the issue, DNS and NETBIOS is ok
answered Dec 12 at 4:12
user972199
1
With the Windows server VPN, on the client side, putting the same class address ip on the network card resolve the issue, DNS and NETBIOS is ok
answered Dec 12 at 4:12
user972199
1
answered Dec 12 at 4:12
user972199
1
answered Dec 12 at 4:12
user972199
1
answered Dec 12 at 4:12
user972199
1
1
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f887941%2fcannot-access-windows-machines-by-name-over-pptp-vpn-but-can-access-ip-address%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
