****** Moderator, please delete this post. I'm puting it in the general forum. Thanks. *******************************************

That's what I get when I try to ' ./smbclient //JAC/D: '.
I've searched Google.
I've searched these forums.
I am a newb, and I still have no answer.
*****************************************************************************
Here is smb.conf :

[global]
wins support = yes
os level = 65
local master = yes
preferred master = yes
domain master = yes
workgroup = mshome
fstype = FAT
smb passwd file = /etc/smbpasswd
printing = cups
dns proxy = no
security = share
encrypt passwords = yes
null passwords = yes
#remote announce = 192.168.0.101/MSHOME
guest account = BABYGIRL
valid users = BABYGIRL,JAC
hosts allow = 192.168.0.
server string = Samba Server %v
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
netbios name = JAC
log file = /var/log/samba/log.%m
load printers = yes

printcap name = lpstat
max log size = 50

# [printers]
# comment = All Printers
# path = /var/spool/samba
# browseable = no
# guest ok = yes
# writable = no
# printable = yes
# create mode = 0700

[D:]
browseable = yes
path = /D:
guest ok = yes
read only = no
valid users = JAC,BABYGIRL
create mode = 775
directory mode = 775
#write list = <user1>
#read list = <user2>

[E:]
path = /E:
browseable = yes
guest ok = yes
read only = no
valid users = JAC,BABYGIRL
create mode = 775
directory mode = 775
#write list = <user1>
#read list = <user2>
*****************************************************************************
Here is the output of ' ./smbclient -NL JAC ' :

root@JAC:/usr/local/samba/bin# ./smbclient -NL JAC
added interface ip=192.168.0.100 bcast=192.168.0.255 nmask=255.255.255.0
Domain=[MSHOME] OS=[Unix] Server=[Samba 2.2.8a]

......... Sharename ..... Type ..... Comment
......... ----------------- ..... ------- ..... -----------------
......... D: ....................... Disk
......... E: ....................... Disk
......... IPC$ .................. IPC ...... IPC Service (Samba Server 2.2.8a)
......... ADMIN$ ............ Disk ..... IPC Service (Samba Server 2.2.8a)

......... Server ................ Comment
......... ------------- ............ ---------------
........ BABYGIRL ......... Crick
........ JAC ...................... Samba Server 2.2.8a

........ Workgroup ............. Master
........ ---------------- ............ ----------
......... MSHOME ............... JAC

*****************************************************************************
I am trying to troubleshoot a problem with Windows XP not being able to navigate 'D:' or 'E:' on the samba server.
Windows gives me an error code 53 - "The network path was not found", when I try to ' net use Z: \\jac\d: ' .
When I try ' net view \\jac ' , Windows sees the shares just fine.
And as you would guess, 'My Network Places' can see the server and shares, but cannot navigate them.

My starting point is to try to navigate these shares on the server itself. But as you can see I am not successful.

Please help.

BTW : How the hell do I keep the spaces preserved when I post stuff. I appologize for the above screen shot, I realize it's not easy to read. Just ignore the periods which I used for spacing.

JC

Change the path=xx to the path on the server. You can't use D: or E:. You need to use the /home/data or something like that. Linux uses directory names for partitions. Unlike Windows where each partition is C, D and so on. So if you want to share the directory /home/data you would have to use path=/home/data. You also have to set local file permissions. Do a chmod 777 /home/data. This will give read/write permissions for everbody. This is, shall we say a little unsecure but it will get you going. Then you have to add the users locually. Do a useradd xxxx at the command line. If you want to add a password for that user you can, but you don't have too(this is a little unsecure too). I would add a passwd for the user by using passwd xxx at the command line. Then you need to add the user to samba. Do a smbpasswd -a xxx at the command line. It will ask you for a passwd for the user.

The fstype = FAT in your global section is not a valid param. Or at least I do not think so. Do a testparm at the command line to see.

You can go to my website listed below. There is a little samba how-to there.

BTW, I don't want to piss off the moderators by replying here, as I did repost this in the General forum, but I have a reply from tangle, so I am responding.

I appreciate the reply, however, what I am trying to do is use two FAT32 drives with my setup. They contain alot of data that I have accumulated over the past couple of years on my Windows platform. Also - I believe that ' D: ' and ' E: ' are valid names for those drives, because that is what I called them during the Slackware setup. That is also how they show up on my desktop ( with the names D: and E: ).

As you can see by the screen shot above, './smbclient ' returns those values as well, so how could they not be valid ? ( look under "Share Name " and "Type". You will see " D: , E:" for the share names, and "disk" for the type )

Also - under "My Network Places" on the Windows box, they show up with the names " D: " and " E: " , the only problem is that when I click on them to open them, I get the error, which I found out with the command ' net use' at a command prompt, is error code 53.

If I am wrong, then correct me.

Are you saying that the ' : ' part of the drive name is not legal ? Because from what I have read, you can name them whatever you want.

I will try renaming the drives to ' D ' and ' E ' without the colons, and see what happens.

One more thing - ' fstype = FAT ' should definitely be legal as it came straight from a book that I have, and ' ./testparm ' returns no errors. I just wish that the book that I have could get me through this problem. It's not really for beginners, so it doesn't cover much on the problems that a newbie might run into.

JC

I was just fighting with the same thing, the error description has nothing to do with the actual issue.

antares tmp # smbclient \\\\XDESPAIR\\HateYou -U antares -d 3 -I 129.21.134.58
Initialising global parameters
params.cm_process() - Processing configuration file "/etc/samba/smb.conf"
added interface ip=129.21.134.9 bcast=129.21.134.127 nmask=255.255.255.128
Client started (version 2.2.8a).
Connecting to 129.21.134.58 at port 139
Password:
Domain=[XDESPAIR] OS=[Unix] Server=[Samba 2.2.8]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

And when you try to connect from windows it gives you these
weird errors about "network not found". It's a mess, and probably should be filed as a bug, since these errors are horrible.

What I ended up doing is changing the log level in /etc/samba/smb.conf

# Set the log (verbosity) level (0 <= log level <= 10)

log level = 3

Then, I went in and saw that I was getting permission denied messages from the server's point of view. Since samba maps the user name from windows to an actual user on the linux machine, I went into the linux box as the user I was logging in with from windows, and tried to access the share as that user. As it turns out, I didn't have local permission, which prevented me from gaining access to the resource.

The worst way to fix it is to chmod 777 /folder the whole share, but it's a horrible security issue.

Instead, make a new group with
groupadd groupnamehere

and then go to the resource that you want to share, and issue a chgrp groupnamehere /folder

then make sure the group has permission to access that share
chmod g+rwx /folder

Finally, you need to add your user to that group, and you do so by:
usermod -G groupnamehere username

Then, try to access that share from that user, and not from your root account. If you can access those files as the user, odds are your samba share will start to work a lot better.

Good luck.

excellent post! good documentation of diagnostic process.
thanks dnatural18.

I am having the same problem that lostboy had
smbclient -L localhost
Password:
Anonymous login successful
Domain=[underverse] OS=[Unix] Server=[Samba 2.2.11]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

I know again it is a permissions issue as when i look in log.smbd, I have
[2004/09/03 13:29:01, 0] smbd/service.c:make_connection(599)
underverse (127.0.0.1) Can't change directory to /root/tmp (Permission denied)

Sounds simple enough, but the problem is that I don't know why it is trying to access /root/tmp

my smb.conf is below

-----------------smb.conf-------------------
[global]
workgroup = BELKIN
encrypt passwords = yes
wins support = yes
browseable = yes



[test]
comment = For testing only, please
path = /usr/local/samba/tmp
read only = no
guest ok = yes
browseable=yes


[homes]
comment = Home Directories
browseable = yes
writable = yes
valid users = %S
-----------------------------------------------------

I know this is what the /root/tmp is the problem (it's obvious from the log file ain't it). I also actually (shiver shiver) made the /root/tmp world readable and executable (to open the directory)
It worked fine as long as that /root/tmp was world readable.

I need to know why is smbd trying to look in /root/tmp

Compilation installation was done with defaults