OpenVPN can not access shared drives on network












1














I am having trouble accessing our shared network drives when I am connected through the VPN.

When I am physically in the office and connected, I have no problems at all. On everyone's computers, the drives are mapped liked \ServerName.

Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine.



The server with the shared files is a running Microsoft Server 2008 R2, and the OpenVPN server is on Ubuntu 18.04.



Why can I not use \ServerName to connect to the shared drives when going through the VPN?



I do have access to the OpenVPN server if I need to change anything. Any help is greatly appreciated.



Client config file



client
proto udp
remote xxx.xxx.xxx.xxx 1194
dev tun
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
verify-x509-name server_S0sFBDyPTuNCNvKX name
auth SHA256
auth-nocache
cipher AES-128-GCM
tls-client
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
setenv opt block-outside-dns # Prevent Windows 10 DNS leak
verb 3
<ca>

</ca>
<cert>

</cert>
<key>

</key>
<tls-crypt>

</tls-crypt>


OpenVPN server.conf



port 1194
proto udp
dev tun
user nobody
group nogroup
persist-key
persist-tun
keepalive 10 120
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "dhcp-option WINS 10.0.0.75"
push "dhcp-option DNS 10.0.0.1"
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"
push "redirect-gateway def1 bypass-dhcp"
dh none
ecdh-curve prime256v1
tls-crypt tls-crypt.key 0
crl-verify crl.pem
ca ca.crt
cert server_S0sFBDyPTuNCNvKX.crt
key server_S0sFBDyPTuNCNvKX.key
auth SHA256
cipher AES-128-GCM
ncp-ciphers AES-128-GCM
tls-server
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
status /var/log/openvpn/status.log
verb 3









share|improve this question
























  • Is it possible that \ServerName is not known by your home computer?
    – Hastur
    Dec 21 '18 at 18:14










  • It should be, I have a laptop that travels with me and \ServerNameshare has already been mapped.
    – laxer
    Dec 21 '18 at 18:18










  • Did you notice the line push "dhcp-option DNS 10.0.0.75" and that when you say "Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine."... ? maybe it is an hint.
    – Hastur
    Dec 21 '18 at 22:13










  • yes, that was me trying to see if that would help. It did not do anything. I did change that line to be push "dhcp-option WINS 10.0.0.75" and when I connected it work, but when I disconnected, and then try to reconnect. It no longer works and I get an error saying 'Microsoft Windows Network: The network path was not found"
    – laxer
    Dec 21 '18 at 22:36










  • Laxer it is difficult to understand from remote. You changed DNS into WINS in the file server.conf. Period. Then you restart the server (as e.g. sudo service ...)? Reboot machine? Reboot the drive? Only try to connect to the shared drive? Try to connect with an already established connection? With a new one? How you tried, with \ServerName, with 10.0.0.75 ? When it worked when not? What said the configuration file when it worked? When not? :-) For you it is easy to understand what happened, you were there... for the readers less...
    – Hastur
    Dec 22 '18 at 10:56


















1














I am having trouble accessing our shared network drives when I am connected through the VPN.

When I am physically in the office and connected, I have no problems at all. On everyone's computers, the drives are mapped liked \ServerName.

Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine.



The server with the shared files is a running Microsoft Server 2008 R2, and the OpenVPN server is on Ubuntu 18.04.



Why can I not use \ServerName to connect to the shared drives when going through the VPN?



I do have access to the OpenVPN server if I need to change anything. Any help is greatly appreciated.



Client config file



client
proto udp
remote xxx.xxx.xxx.xxx 1194
dev tun
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
verify-x509-name server_S0sFBDyPTuNCNvKX name
auth SHA256
auth-nocache
cipher AES-128-GCM
tls-client
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
setenv opt block-outside-dns # Prevent Windows 10 DNS leak
verb 3
<ca>

</ca>
<cert>

</cert>
<key>

</key>
<tls-crypt>

</tls-crypt>


OpenVPN server.conf



port 1194
proto udp
dev tun
user nobody
group nogroup
persist-key
persist-tun
keepalive 10 120
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "dhcp-option WINS 10.0.0.75"
push "dhcp-option DNS 10.0.0.1"
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"
push "redirect-gateway def1 bypass-dhcp"
dh none
ecdh-curve prime256v1
tls-crypt tls-crypt.key 0
crl-verify crl.pem
ca ca.crt
cert server_S0sFBDyPTuNCNvKX.crt
key server_S0sFBDyPTuNCNvKX.key
auth SHA256
cipher AES-128-GCM
ncp-ciphers AES-128-GCM
tls-server
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
status /var/log/openvpn/status.log
verb 3









share|improve this question
























  • Is it possible that \ServerName is not known by your home computer?
    – Hastur
    Dec 21 '18 at 18:14










  • It should be, I have a laptop that travels with me and \ServerNameshare has already been mapped.
    – laxer
    Dec 21 '18 at 18:18










  • Did you notice the line push "dhcp-option DNS 10.0.0.75" and that when you say "Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine."... ? maybe it is an hint.
    – Hastur
    Dec 21 '18 at 22:13










  • yes, that was me trying to see if that would help. It did not do anything. I did change that line to be push "dhcp-option WINS 10.0.0.75" and when I connected it work, but when I disconnected, and then try to reconnect. It no longer works and I get an error saying 'Microsoft Windows Network: The network path was not found"
    – laxer
    Dec 21 '18 at 22:36










  • Laxer it is difficult to understand from remote. You changed DNS into WINS in the file server.conf. Period. Then you restart the server (as e.g. sudo service ...)? Reboot machine? Reboot the drive? Only try to connect to the shared drive? Try to connect with an already established connection? With a new one? How you tried, with \ServerName, with 10.0.0.75 ? When it worked when not? What said the configuration file when it worked? When not? :-) For you it is easy to understand what happened, you were there... for the readers less...
    – Hastur
    Dec 22 '18 at 10:56
















1












1








1







I am having trouble accessing our shared network drives when I am connected through the VPN.

When I am physically in the office and connected, I have no problems at all. On everyone's computers, the drives are mapped liked \ServerName.

Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine.



The server with the shared files is a running Microsoft Server 2008 R2, and the OpenVPN server is on Ubuntu 18.04.



Why can I not use \ServerName to connect to the shared drives when going through the VPN?



I do have access to the OpenVPN server if I need to change anything. Any help is greatly appreciated.



Client config file



client
proto udp
remote xxx.xxx.xxx.xxx 1194
dev tun
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
verify-x509-name server_S0sFBDyPTuNCNvKX name
auth SHA256
auth-nocache
cipher AES-128-GCM
tls-client
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
setenv opt block-outside-dns # Prevent Windows 10 DNS leak
verb 3
<ca>

</ca>
<cert>

</cert>
<key>

</key>
<tls-crypt>

</tls-crypt>


OpenVPN server.conf



port 1194
proto udp
dev tun
user nobody
group nogroup
persist-key
persist-tun
keepalive 10 120
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "dhcp-option WINS 10.0.0.75"
push "dhcp-option DNS 10.0.0.1"
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"
push "redirect-gateway def1 bypass-dhcp"
dh none
ecdh-curve prime256v1
tls-crypt tls-crypt.key 0
crl-verify crl.pem
ca ca.crt
cert server_S0sFBDyPTuNCNvKX.crt
key server_S0sFBDyPTuNCNvKX.key
auth SHA256
cipher AES-128-GCM
ncp-ciphers AES-128-GCM
tls-server
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
status /var/log/openvpn/status.log
verb 3









share|improve this question















I am having trouble accessing our shared network drives when I am connected through the VPN.

When I am physically in the office and connected, I have no problems at all. On everyone's computers, the drives are mapped liked \ServerName.

Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine.



The server with the shared files is a running Microsoft Server 2008 R2, and the OpenVPN server is on Ubuntu 18.04.



Why can I not use \ServerName to connect to the shared drives when going through the VPN?



I do have access to the OpenVPN server if I need to change anything. Any help is greatly appreciated.



Client config file



client
proto udp
remote xxx.xxx.xxx.xxx 1194
dev tun
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
verify-x509-name server_S0sFBDyPTuNCNvKX name
auth SHA256
auth-nocache
cipher AES-128-GCM
tls-client
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
setenv opt block-outside-dns # Prevent Windows 10 DNS leak
verb 3
<ca>

</ca>
<cert>

</cert>
<key>

</key>
<tls-crypt>

</tls-crypt>


OpenVPN server.conf



port 1194
proto udp
dev tun
user nobody
group nogroup
persist-key
persist-tun
keepalive 10 120
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "dhcp-option WINS 10.0.0.75"
push "dhcp-option DNS 10.0.0.1"
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"
push "redirect-gateway def1 bypass-dhcp"
dh none
ecdh-curve prime256v1
tls-crypt tls-crypt.key 0
crl-verify crl.pem
ca ca.crt
cert server_S0sFBDyPTuNCNvKX.crt
key server_S0sFBDyPTuNCNvKX.key
auth SHA256
cipher AES-128-GCM
ncp-ciphers AES-128-GCM
tls-server
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
status /var/log/openvpn/status.log
verb 3






networking ubuntu vpn openvpn windows-server-2008-r2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 21 '18 at 22:41

























asked Dec 21 '18 at 18:05









laxer

63




63












  • Is it possible that \ServerName is not known by your home computer?
    – Hastur
    Dec 21 '18 at 18:14










  • It should be, I have a laptop that travels with me and \ServerNameshare has already been mapped.
    – laxer
    Dec 21 '18 at 18:18










  • Did you notice the line push "dhcp-option DNS 10.0.0.75" and that when you say "Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine."... ? maybe it is an hint.
    – Hastur
    Dec 21 '18 at 22:13










  • yes, that was me trying to see if that would help. It did not do anything. I did change that line to be push "dhcp-option WINS 10.0.0.75" and when I connected it work, but when I disconnected, and then try to reconnect. It no longer works and I get an error saying 'Microsoft Windows Network: The network path was not found"
    – laxer
    Dec 21 '18 at 22:36










  • Laxer it is difficult to understand from remote. You changed DNS into WINS in the file server.conf. Period. Then you restart the server (as e.g. sudo service ...)? Reboot machine? Reboot the drive? Only try to connect to the shared drive? Try to connect with an already established connection? With a new one? How you tried, with \ServerName, with 10.0.0.75 ? When it worked when not? What said the configuration file when it worked? When not? :-) For you it is easy to understand what happened, you were there... for the readers less...
    – Hastur
    Dec 22 '18 at 10:56




















  • Is it possible that \ServerName is not known by your home computer?
    – Hastur
    Dec 21 '18 at 18:14










  • It should be, I have a laptop that travels with me and \ServerNameshare has already been mapped.
    – laxer
    Dec 21 '18 at 18:18










  • Did you notice the line push "dhcp-option DNS 10.0.0.75" and that when you say "Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine."... ? maybe it is an hint.
    – Hastur
    Dec 21 '18 at 22:13










  • yes, that was me trying to see if that would help. It did not do anything. I did change that line to be push "dhcp-option WINS 10.0.0.75" and when I connected it work, but when I disconnected, and then try to reconnect. It no longer works and I get an error saying 'Microsoft Windows Network: The network path was not found"
    – laxer
    Dec 21 '18 at 22:36










  • Laxer it is difficult to understand from remote. You changed DNS into WINS in the file server.conf. Period. Then you restart the server (as e.g. sudo service ...)? Reboot machine? Reboot the drive? Only try to connect to the shared drive? Try to connect with an already established connection? With a new one? How you tried, with \ServerName, with 10.0.0.75 ? When it worked when not? What said the configuration file when it worked? When not? :-) For you it is easy to understand what happened, you were there... for the readers less...
    – Hastur
    Dec 22 '18 at 10:56


















Is it possible that \ServerName is not known by your home computer?
– Hastur
Dec 21 '18 at 18:14




Is it possible that \ServerName is not known by your home computer?
– Hastur
Dec 21 '18 at 18:14












It should be, I have a laptop that travels with me and \ServerNameshare has already been mapped.
– laxer
Dec 21 '18 at 18:18




It should be, I have a laptop that travels with me and \ServerNameshare has already been mapped.
– laxer
Dec 21 '18 at 18:18












Did you notice the line push "dhcp-option DNS 10.0.0.75" and that when you say "Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine."... ? maybe it is an hint.
– Hastur
Dec 21 '18 at 22:13




Did you notice the line push "dhcp-option DNS 10.0.0.75" and that when you say "Also when I say \10.0.0.75 when connected to the VPN and I type in a username and password it works just fine."... ? maybe it is an hint.
– Hastur
Dec 21 '18 at 22:13












yes, that was me trying to see if that would help. It did not do anything. I did change that line to be push "dhcp-option WINS 10.0.0.75" and when I connected it work, but when I disconnected, and then try to reconnect. It no longer works and I get an error saying 'Microsoft Windows Network: The network path was not found"
– laxer
Dec 21 '18 at 22:36




yes, that was me trying to see if that would help. It did not do anything. I did change that line to be push "dhcp-option WINS 10.0.0.75" and when I connected it work, but when I disconnected, and then try to reconnect. It no longer works and I get an error saying 'Microsoft Windows Network: The network path was not found"
– laxer
Dec 21 '18 at 22:36












Laxer it is difficult to understand from remote. You changed DNS into WINS in the file server.conf. Period. Then you restart the server (as e.g. sudo service ...)? Reboot machine? Reboot the drive? Only try to connect to the shared drive? Try to connect with an already established connection? With a new one? How you tried, with \ServerName, with 10.0.0.75 ? When it worked when not? What said the configuration file when it worked? When not? :-) For you it is easy to understand what happened, you were there... for the readers less...
– Hastur
Dec 22 '18 at 10:56






Laxer it is difficult to understand from remote. You changed DNS into WINS in the file server.conf. Period. Then you restart the server (as e.g. sudo service ...)? Reboot machine? Reboot the drive? Only try to connect to the shared drive? Try to connect with an already established connection? With a new one? How you tried, with \ServerName, with 10.0.0.75 ? When it worked when not? What said the configuration file when it worked? When not? :-) For you it is easy to understand what happened, you were there... for the readers less...
– Hastur
Dec 22 '18 at 10:56












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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386739%2fopenvpn-can-not-access-shared-drives-on-network%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
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1386739%2fopenvpn-can-not-access-shared-drives-on-network%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido