Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm trying to mount a network share from a Linksys NAS200 to Fedora 16.

The program I am trying to run won't accept network addresses to save to. I ran it without specifying the IP address of the server and it comes up with some random IP. I specified an IP and it can't find the device.

Here are the errors:

[root@HOME ~]# mount -t cifs -v //NAS_SERVER/public/ /mnt/ -o username=user,password=pass
mount.cifs kernel mount options: ip=,unc=\\NAS_SERVER\public,,ver=1,user=user,pass=********
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[root@HOME ~]# mount -t cifs -v //NAS_SERVER/public/ /mnt/ -o username=user,password=pass,ip=
ip address override specified
mount.cifs kernel mount options: ip=,unc=\\NAS_SERVER\public,,ver=1,user=user,pass=********
Retrying with upper case share name
mount.cifs kernel mount options: ip=,unc=\\NAS_SERVER\PUBLIC,,ver=1,user=user,pass=********
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

But it does work with smbclient:

[root@HOME ~]# smbclient -L
WARNING: The security=share option is deprecated
Enter user's password: 
Domain=[HOME] OS=[Unix] Server=[Samba 3.0.22]

Sharename       Type      Comment
---------       ----      -------
IPC$            IPC       IPC Service (Network Storage)
DISK 1          Disk      
PUBLIC          Disk      
ADMIN$          IPC       IPC Service (Network Storage)
Domain=[HOME] OS=[Unix] Server=[Samba 3.0.22]

Server               Comment
---------            -------
HOME                 Samba Server Version 3.6.5-85.fc16
NAS_SERVER           Network Storage

Workgroup            Master
---------            -------
HOME                 HOME

Why can't I mount to this samba server? What do these errors mean?

share|improve this question

3 Answers 3

Troubleshoot accessing a windows XP shared folder from Fedora:

You are receiving the error:

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

1. Make sure Linux can ping the other box.

Run this command on the linux box to the IP of the windows box:

el@defiant /mnt $ ping
PING ( 56(84) bytes of data.
64 bytes from icmp_req=1 ttl=128 time=0.366 ms
--- ping statistics ---
44 packets transmitted, 44 received, 0% packet loss, time 42999ms
rtt min/avg/max/mdev = 0.178/0.227/0.366/0.038 ms

If you can't reach the box or connectivity is in and out, mount may complain.

2. Make sure a folder is actually shared on windows, follow these steps.

  1. Open the file browser to C:\.
  2. Create a new folder called public. So you now have C:\public
  3. Inside that folder, make a new text document called "testing.txt".
  4. Right click the folder C:\public and go to properties.
  5. Click the sharing tab.
  6. Make sure: "Share this folder on the network" is checked. Note the share name: 'public'.
  7. Click ok. A little hand should appear underneath the folder, meaning it is shared.

The folder 'public' is now shared and you should be able to connect to it with Linux.

3. On Linux, mount the share with 'mount':

  1. Open a console and su to root.
  2. make a directory mkdir /mnt/windows This will be where you access the shared files.

  3. run the mount command which prompts for a password:

    [root@defiant mnt]# mount -t cifs // /mnt/windows -o username=eric
    Password for eric@//  **********
    [root@defiant mnt]# 
  4. The above command prompts you for a password, enter the correct password, an incorrect one will produce an error. If you are unsure of the password, you can change the password on the windows box under Control Panel -> User Accounts.

  5. run the command cd /mnt/windows and run ls. The contents of the drive are presented:

    [root@defiant windows]# ls
    [root@defiant windows]#
  6. You have connected to the windows drive.

4. Connect to the shared drive with the konqueror or linux file browser:

  1. Open your file browser, in my case konqueror.
  2. In the file location bar, enter smb:// and press enter.
  3. You may be presented with a username and password login box. Enter the username and password of the windows box described at the top of this post.
  4. Congratulations you are connected to the shared folder.

TROUBLESHOOTING, if the above doesn't work.

Step 1: Have you tried restarting both computers

Reboot both of your computers. After that, make sure all your windows updates are done. Make sure Linux has its software updates taken care of as well. Reboot after updates.

Step 2: Review your Firewalls, ZoneAlarms, and other Security Software

A piece of software designed to protect your computer from viruses, malware or evils on the internet might be blocking your file sharing attempt. Windows firewall might be in a paranoid mode. Although it is unlikely Windows Firewall is to blame, turn it off temporally to verify it's not the problem. (don't leave it off).

Acquire a list of all the security software that might be set to paranoid mode. Windows Firewalls, 3rd party firewalls, ZoneAlarms, Antiviruses, Kaspersky, AVG, or anything else that claims to protect you from viruses/malware/evil. You will need to review these and either turn them off temporally, or open a white list through them for your IP address.

Step 3: Acquire clues from security software.

ZoneAlarm keeps a log of all folder share events and attempts, go to Overview->alerts and logs. And see a list of all your failed attempts. The same is possible for other software. In that case, it's protecting you from you.

Step 4: Suspect problems in the router or local area network itself

Maybe the router, wireless bridges, dumb hubs, or other network device has some directive shenanigan in it by blocking your shared folder connect attempt. The router or device itself might be blocking a port or has something in restrictive mode. Has anyone been fooling around with it lately? Try setting the router back to default everything and trying again.

Step 5: Make sure your local area network is simple and correct.

Are both your computers connecting to the same router? Perhaps one is connected to a crappy netgear wireless bridge and the other to a router? Simplify the network by having all computers connect to one router. Restart the routers and the internet, try again.

Step 6: Still not working. Isolate the defective unit.

It's time to herd cats and isolate the defective unit. Prove the windows box is not sharing your file by connecting to the share with a different computer. Get a friends windows laptop, or apple product and connect it to your network and see if they can access the share. If they can't, the windows box has a problem, if they can, the Linux box has the problem.

Step 7: Suspect the firewall on Linux

Take note of any special security alarm or special firewall software on Linux. Run system-config-firewall and make sure smb is checked. Check to make sure Linux is not preventing your mount. Create a smb share on another Linux box, and try to connect to that.

If none of this works. Use the nuclear option, re install both operating systems and start over at the top. This is rocket surgery.

share|improve this answer
That one did it for me. The issue in my case was caused by firewall settings that allowed ping but did not allow SMB connections on TCP port 445. –  Paul Gear Jan 28 at 6:06

Not sure just how relevant this is for your case, but I had a similar problem mounting a CIFS share on my Android phone:

# mount -t cifs // /mnt/cifs/media -o username=user,password=pass
mount: mounting // on /mnt/cifs/media failed: No such device or address

I tried removing the trailing slash and apparently it made a difference - it mounted:

# mount -t cifs // /mnt/cifs/media -o username=user,password=pass
share|improve this answer
Yeah, shares aren't exactly directories, even if desktop environments like to pretend they are. –  Eroen Sep 17 '12 at 14:19


mount -t cifs -v //NAS_SERVER/public/ /mnt/ -o username=user,password=pass,sec=ntlm

The key is sec=ntlm

share|improve this answer
That didn't give me any joy –  Paul Gear Jan 28 at 5:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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