Mounting NAS share: Bad Address

Posted by Korben on Server Fault See other posts from Server Fault or by Korben
Published on 2012-04-13T11:10:30Z Indexed on 2012/04/13 11:32 UTC
Read the original article Hit count: 1718

Filed under:
|
|
|
|

I've faced to the problem that can't solve. Hope you can help me with it.

I have a storage QNAP TS-459U, with it's own Linux, and 'massive1' folder shared, which I need to mount to my Debian server. They are connected by regular patch cord. Debian server has two network interfaces - eth0 and eth1. eth0 is for Internet, eth1 is for QNAP.

So, I'm saying this:

mount -t cifs //169.254.100.100/massive1/ /mnt/storage -o user=admin ,

where 169.254.100.100 is an IP of QNAP's interface. The result I get (after entering password):

mount error(14): Bad address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Tried: mount.cifs, smbmount, with '/' at the end of the network share and without it, and many other variations of that command. And always its: mount error(14): Bad address

Funny thing is when I was in Data Center, I had connected my netbook to QNAP by the same scheme (with Fedora 16 on it), and it connected without any problems, I could read/write files on the QNAP's NAS share!

So I'm really stuck with the Debian. I can't undrestand where's the difference with Fedora, making this error. Yeah, I've used Google. Couldn't find any useful info.

Ping to the QNAP's IP is working, I can log into QNAP's Linux by ssh, telnet on 139's port is working.

This is network interface configuration I use in Debian:

IP: 169.254.100.1 Netmask: 255.255.0.0

The only diffence in connecting to Fedora and Debian is that in Fedora I've added gateway - 169.254.100.129, but ping to this IP is not working, so I think it's not necessary at all.

P.S.

~# cat /etc/debian_version wheezy/sid

~# uname -a Linux host 2.6.32-5-openvz-amd64 #1 SMP Mon Mar 7 22:25:57 UTC 2011 x86_64 GNU/Linux

~# smbtree

WORKGROUP
        \\HOST                         host server
                \\HOST\IPC$            IPC Service (host server)
                \\HOST\print$          Printer Drivers

NAS
        \\MASSIVE1                      NAS Server
                \\MASSIVE1\IPC$                 IPC Service (NAS Server)
                \\MASSIVE1\massive1
                \\MASSIVE1\Network Recycle Bin 1        [RAID5 Disk Volume: Drive 1 2 3 4]
                \\MASSIVE1\Public               System default share
                \\MASSIVE1\Usb                  System default share
                \\MASSIVE1\Web                  System default share
                \\MASSIVE1\Recordings           System default share
                \\MASSIVE1\Download             System default share
                \\MASSIVE1\Multimedia           System default share

Please, help me with solving this strange issue.

Thanks before.

© Server Fault or respective owner

Related posts about debian

Related posts about mount

  • 12.10 update breaks NFS mount

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I've just upgraded to the latest 12.10 beta. Rebooted twice. The problem is with the NFS folders not mounting, here's a verbose log. # mount -v myserver:/nfs_shared/tools /tools/ mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Mon Oct 1 11:42:28 2012 mount… >>> More

  • Mount SMB / AFP 13.10

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I cannot seem to get Ubuntu to mount a mac share via SMB or AFP. I've tried the following... AFP: apt-get install afpfs-ng-utils mount_afp afp://user:password@localip/share /mnt/share Error given: "Could not connect, never got a reponse to getstatus, Connection timed out". Which is odd as I can… >>> More

  • Mount Return Code for CIFS mount

    as seen on Server Fault - Search for 'Server Fault'
    When I run the following command (as root or via sudo) from a bash script I get an exit status (or return code in mount man page parlance) of 1: mount -v -t cifs //nasbox/volume /tmpdir/ --verbose -o credentials=/root/cifsid & /tmp/mylog It outputs the following into the myflog file: parsing… >>> More

  • Disable raid member check upon mount to mount damaged nvidia raid1 member

    as seen on Server Fault - Search for 'Server Fault'
    Hi, A friend of mine destroyed his Nvidia RAID1 array somehow and in trying to fix it, he ended up with a non-working array. Because of the RAID metadata, the actual disk data was stored at an offset from the beginning. I was able to identify this offset with dd and a hexeditor and then I used losetup… >>> More

  • Network shares do not mount.

    as seen on Super User - Search for 'Super User'
    My network shares were mounting fine yesterday.. suddenly they are not. They were mounting fine for the last two weeks or however long since I added them. When I run sudo mount -a I get the following error: topsy@monolyth:~$ sudo mount -a mount error(12): Cannot allocate memory Refer to the mount… >>> More