Issues mounting a remote Windows share using CIFS over a Cisco VPN

funcrusher · 06-06-2013, 08:43 AM

Hi all,

I'm trying to connect a client running Ubuntu 13.04 to a network share hosted by a file server which has recently been upgraded from Windows Server 2003 to 2012. Currently I am able to mount the remote share while connected to the LAN using:

Code:

sudo mount -t cifs //myserver.mydomain.co.uk/myshare /media/myshare/ -o user=myself,domain=myworkgroup,pass=**********

However, I'm having trouble mounting the share via a Cisco (IPsec/Xauth) VPN. Prior to the server upgrade I had no problem with this, but now I get the following message:

Code:

mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

dmesg | tail gives me [ 1975.651346] CIFS VFS: cifs_mount failed w/return code = -112

The host is most definitely not down - I am still able to connect to the same share over the VPN using smbclient:

Code:

smbclient //myserver.mydomain.co.uk/myshare -U myself -W myworkgroup
Enter myself's password: 
session request to MYSERVER.MYDOMAIN failed (Called name not present)
Domain=[MYWORKGROUP] OS=[Windows Server 2012 Standard 9200] Server=[Windows Server 2012 Standard 6.2]
smb: \>

I'm not sure of the significance of the "session request to MYSERVER.MYDOMAIN failed (Called name not present)" error, since I'm still able to browse the directory structure.

Any suggestions for what to try next?

jefro · 06-07-2013, 03:58 PM

This may help. http://forums.fedoraforum.org/showth...=271326&page=3

funcrusher · 06-07-2013, 07:37 PM

Hi jefro, as far as I can tell nothing in that thread really seems to address my specific problem. All of the stuff about configuring smb.conf is not relevant to me, since mount.cifs totally ignores smb.conf. As for the rest:

Quote:

For Windows to be very happy, you need to supply the following things:
Server IP address
Shared directory
Domain/Workgroup
username
password

I have supplied all of these things (as far as I can possibly tell) correctly. I can resolve the IP address of the server when connected to the VPN, and I can substitute it for the tcp name of the server and get the exact same output for the `mount -t cifs...` and `smbclient` calls. If I am entering one of the parameters above incorrectly then surely I wouldn't be able to mount the share while I'm not connected via the VPN (or browse the contents using smbclient while I am connecting via the VPN)?