3

I'm having an issue mounting a shared NAS drive that is hosted on a Windows 2000 server. This is a drive that I'm certain I have access to, and I frequently access it from a Windows 7 machine and a Windows Server 2008 machine. Now, I'm attempting to mount this drive from a RHEL7 machine, but I'm having some issues.

What I've done:

mkdir /mnt/neededFolder
mount -t cifs //DNS.forMyDrive.stuff/neededFolder /mnt/neededFolder -o username=myUserId,password=myPassword,domain=myDomain

What I expected: I expected to be able to access the folder at /mnt/neededFolder

What actually happened: The error I'm receiving (partially shown in the subject line here) is

mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

What the log says:

dmesg output:

[1712257.661259] CIFS VFS: Error connecting to socket. Aborting operation.
[1712257.662098] CIFS VFS: cifs_mount failed w/return code = -115

We can all see that there is a connection issue, that is obvious. I know both machines are connected to the network. What can I try next to get this drive mounted?

EDIT: It may be worth noting that I am able to ping the DNS name and the raw IP of the remote location that I am trying to mount.

1

The issue ended up being that the route to the NAS was missing. Once the route was added, I was able to mount the drive with ease.

route add-net x.x.x.x netmask x.x.x.x gw x.x.x.x

Hopefully this helps someone else in the future!

  • So you're saying this was a network error? Initially you wrote that you could ping both the IP and the DNS name, how did that work if the routing was wrong? – ketil Jan 14 at 16:53
  • @ketil, you know looking back at this question, that does seem interesting. I can't remember now exactly, because it was months ago, but it's possible that I was pinging from my local machine (this question was for a server) and just stating that I can ping the address, so it was clear that server with the drive was online. – Joshua Schlichting Jan 15 at 1:06
0

Well, I had the same problem after I got windows 10 update 1809. The windows firewall was blocking the access. There is a predefined rule for inbound SMB conections that was not activated for private network.

Funny thing: It seems to be activated for public networks....

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.