Can't share a drive with a windows computer on the network

Asked by John Zimmer

Using Samba or just creating a share of an external drive will not work at all for me. The most i get from a windows computer on my home network is an invalid user error. Most of the time the drive and /or folder shows up but I can not access it, then sometimes it don't. I've tried and followed all the advice I've found to no end. I just want to share a whole external drive on my home network, with the other computers running Windows 7, and have all the permissions to create, delete, move, and so on. I want just a simple explanation on how to do this this in any way someone can.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu samba Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

You are sharing the partition on the drive, not the drive itself.

If you run:

smbtree; lsb_release -a; uname -a; dpkg -l | grep samba

What is output ?

Revision history for this message
John Zimmer (johnz387) said :
#2

On 05/10/2012 12:00 PM, actionparsnip wrote:
> smbtree; lsb_release -a; uname -a; dpkg -l | grep samba
I don't get a reply, copy it and put it in term, at least I think I did,
and nothing happens, just does a search.

Revision history for this message
John Zimmer (johnz387) said :
#3

Wanting to share the whole drive, it is an external USB drive.

Revision history for this message
John Zimmer (johnz387) said :
#4

On 05/10/2012 12:00 PM, actionparsnip wrote:
> Your question #196768 on samba in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/samba/+question/196768
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> You are sharing the partition on the drive, not the drive itself.
>
> If you run:
>
> smbtree; lsb_release -a; uname -a; dpkg -l | grep samba
>
> What is output ?
>
Thought I was in term, not! This is the output:
john@ubuntu:~$ smbtree; lsb_release -a; uname -a; dpkg -l | grep samba
Enter john's password:
MYGROUP
     \\UBUNTU ubuntu server (Samba, Ubuntu)
         \\UBUNTU\Eastman-Kodak-Company-KODAK-ESP-Office-2150-Series
Eastman Kodak Company KODAK ESP Office 2150 Series
         \\UBUNTU\IPC$ IPC Service (ubuntu server (Samba,
Ubuntu))
         \\UBUNTU\Public
KODAKAIO
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Linux ubuntu 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
ii samba
2:3.6.3-2ubuntu2.1 SMB/CIFS file, print, and login
server for Unix
ii samba-common
2:3.6.3-2ubuntu2.1 common files used by both the
Samba server and client
ii samba-common-bin
2:3.6.3-2ubuntu2.1 common files used by both the
Samba server and client
ii samba-doc
2:3.6.3-2ubuntu2.1 Samba documentation
ii samba-doc-pdf
2:3.6.3-2ubuntu2.1 Samba documentation in PDF format
ii system-config-samba
1.2.63-0ubuntu5 GUI for managing samba shares
and users
john@ubuntu:~$

Revision history for this message
John Zimmer (johnz387) said :
#5

Ok, now I can see the shared directories on my windows computer, but my wife can not on her windows computer. Setup up a Samba user name and put in the Windows name and pass just like I did for mine. Both Windows computers are running Windows 7, both set up the same on the home network. Her computer keeps telling her that she does not have athority to the shares, contact system administer. So, any ideas on the part, at least I can get to the shared directoies on my Windows computer.

Revision history for this message
John Zimmer (johnz387) said :
#6

I can't get the darn thing to work right. I own the directories and external drives, therefore my wife can't access them, even though she is an administrator too. Some body out there just tell me how in simple text how I can have the external drives public to everyone, not just me.

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.