[root@a1 ~]# testparm -Lv
Load smb config files from /etc/samba/smb.conf
Processing section "[mw]"
Loaded services file OK.
Server role: ROLE_DOMAIN_PDC
Press enter to see a dump of your service definitions

[global]
workgroup = MW
server string = Primary Server
passdb backend = tdbsam
log file = /var/log/samba.%m
max log size = 500
time server = Yes
domain logons = Yes
os level = 64
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
hosts allow = 192.168.169., 127.
hosts deny = 0.0.0.0/0

[mw]
path = /mw
valid users = mmm
read only = No
create mask = 0770
force create mode = 0770
security mask = 0770
force security mode = 0770
directory mask = 0770
force directory mode = 0770
force directory security mode = 0770
oplocks = No
level2 oplocks = No
[root@a1 ~]#


Group, I apologize for asking about such a beginner's problem, but I cannot figure it out and need a point in the right direction.

I built a new box using Arch linux with Samba ver. 3.2.x. and installed it on my LAN to start testing my setup. I've been reading the TOSHARG2 and Samba Guide and came up with the setup you see printed out above.
For now, my only share is "mw" and the actual path is /mw .
I go to a Win XP Pro w/SP2 client box to see if I can join the domain, but I experience the following failures:

1. Try the Network Identification Wizard to join domain MW. Could not join the domain: The network path was not found.
2. Try to join the domain using the System Properties > Computer Name (Tab) > Change Member of: Domain. But I also receive - The network path was not found
3. When I do the same as #2, but instead choose to join MW as a WorkGroup, I allowed to "join" the WorkGroup. However, when I reboot and try to access the samba server, windows says it is not accessible .... Network path was not found.

I've never had to specify a logon path before; is this what I need to do?
From what I read in the TOSHARG2, I thought a logon path was not necessary unless I was trying to create roaming profiles, etc.

I appreciate any suggestions you can give.
Thanks for listening.

Uggh!
I think I see the problem after walking away from it.

I forgot to put in the parameter netbios name = host-name-of-server

I'll test tomorrow to confirm.

No, that's not it.
I checked the smb.conf this morning and the netbios name is properly stated in the [global] section.

Solved.
Issue relating to directory ownership and user groups.
Use of chmod on the samba shares solved the problem.

There's a new issue now, but it is more appropriate for the Networking forum.