Ok here is what i got i have tried to get this may times and no luck keeps telling me that "Permission Denied" so i might need some help..

this is the line i put in my fstab

//192.168.1.100/Documents/ /mnt/Vault cifs auto,guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0


now i have tried this too

//192.168.1.100/Documents/ /mnt/Vault cifs credentials=/home/timmy/.smbpassword,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0

and set the file up with the password and user..

I followed this guide here and had no luck but it look like this guide was for ubuntu 7.10 i run kubuntu 8.04 so it might be deferent i don't know.

i'm ok with linux no guru by any means but i can get around gui and term.. but if i ask you to explain a little more sorry i'm learning as i go

I have netbios install samba too..

also i have read a few other guides and did some things like this..
smbclient //Vault/Documents
and got this
smb: \>

also got this command smbclient -L //192.168.1.100
this was the out put
Domain=[VAULT] OS=[Unix] Server=[Samba 3.0.25b]

Sharename Type Comment
--------- ---- -------
Photos Disk Default_Photos
Music Disk Default_Music
Videos Disk Default_Videos
Backup Disk Default_Backup
Documents Disk Default_Documents
IPC$ IPC IPC Service (HPMediaVault Server)
Domain=[VAULT] OS=[Unix] Server=[Samba 3.0.25b]

Server Comment
--------- -------

Workgroup Master
--------- -------
WORKGROUP


I think this was just to test and see if it was visible on the network..


Any and all help is greatly appreciated thanks....

You might have better luck if you use an interactive application like Dolphin or Konqueror in filemanager mode or smb4k. The idea that I have in mind is that you just browse the network and connect using any of those application just like you would connect to a network share in Windows using Explorer.

Otherwise the line that had the credentials is the closest to a working system. I would replace the credentials with the actual username and password if this is a private system at home. If this is in work then play with the syntax in the credentials file.

This is a script that I use to mount my Iomega NAS via Samba. This way I don't have to put the confidential information in /etc/fstab.
Naturally I have changed the specifics.

I have set up the Iomega NAS with a username and password so I don't rely on a guest account. nasuser is the account on the NAS. user01 is the user on the computer.

So you just have a script and run that to mount it every time and just say the heck with the fstab hmm ok i'mm give that a go thanks....

It does mount it but i still don't have access hmmm.. there is the admin user for the nas and a "photo user" which should i use? Does my user for kubuntu need some rights or added to a group?

and
I think these are related and I've had this kind of problem with Samba although it was using Samba as a server. Here are a couple of ideas that I have successfully used to fix authentication problems. Note: I use all of these techniques all of the time.

- My NAS belongs to its own WORKGROUP, not an NTLM domain or Active Directory domain.

- I put the IP and name of the NAS in the lmhosts file and in the hosts file on the Linux computers.
(/etc/hosts, /etc/samba/lmhosts)
The /etc/hosts file entry looks like this:
The /etc/samba/lmhosts file entry looks like this:
Naturally that means that I have to map a specific IP address to the hardware address of the NAS in my DHCP server/router/gateway.

- My Iomega has very comprehensive user account management. I did a quick search of HP Media Vault but I gave up before I found how extensive that appliance's user account management is. You should look into this to see if you can assign user rights to various shares. For example I have disabled the guest account on my Iomega and I have three different user accounts. One user account has read-only access to the public share, another has read-write access to the public share, and the third has no access to the public share but has full access to its own private share. Look into this kind of feature for your NAS.

http://search.hp.com/query.html?lang...as&la=en&cc=us

Of all of the ideas above I think that putting the IP and name of the NAS into your Linux computer's lmhosts file and hosts file has the greatest likelihood of addressing the permission problem. That is because Windows authentication relies on reverse IP lookup (RIP). Having the NAS's software address and name in the lmhosts file helps this process. (Anyone reading this who knows for a fact that I am mistaken about RIP please correct me. I am always refining my understanding of how stuff works so don't be shy.) Anyway, I have found that having an entry for the NAS in the lmhosts file fixes authentication problems. Of that I'm sure because I've seen it. My theory of why it works is from observation and talking with colleagues, not from books.

ok i can make the files i have a question about this in your first line you have "192.168.1.5 iomega01.my.house iomega01"
what is iomega.01.my.house for do i just put Vault.my.house? Vault is the name of my nas.

And all of this may be caused by my router? it is quite old had it for 6 years or more it don't even have UPNP from what i can tell...

any whoot i'm going to give it a go...

thanks for all the help...

The iomega01 is the IP host name of the NAS. It is also the NetBIOS name of the NAS. Both the IP name and the NetBIOS name are configured on the NAS. The my.house part is an IP domain in my house that I create simply by including it in all of the hosts files on my LAN. If my LAN had a DNS server then my.house would be defined there but since my LAN is small I just use the hosts files for name to IP address lookup.

Just tried a test and it worked kind of...
I opened the dir with the vault /mnt/Vault and tried to make a dir it worked then in that dir i tried to make a file.txt with the words test in it worked? what is going on here? i don't know but i will get it...grrrr