I'm a linux admin noob (know my way around from a user standpoint) trying to get samba shares up and running, for connection via a windows XP machine. I've read through several howtos, done a bit of googling, browsing forums, asking friends, but I can't for the life of me get this to work. Everything seems like it's in line to work, so I come to you guys for help

When I attempt to connect to my share, \\(linux box ip)\(sharename), I receive the lovely windows errormsg "Windows cannot find '(share address)'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search." When I go into Network Places > View Workgroup Computers, nothing shows up as well.

Any ideas as to what I should try, or what I'm doing wrong? I've outlined (probably too much information about) what I've done below. Thanks in advance

Here's a runthrough of what I've done:

Windows (XP, SP2) stuff:

- Windows Firewall is disabled (always has been)

- 3rd party Software Firewall is disabled

- Nothing seems to be missing/disabled from administrative services (network connections, server, etc). Previously, I had disabled the majority of these unecessary services since I wasn't on a shared network, but everything should be in line now.

- I *can* connect to SWAT from my windows box

- I can ssh into the linux box


Linux (debian, 2.2.20 apparently? I thought I installed off a Woody network install...) stuff:

- I've setup a user/password on my debian linux box that matches my account on windows (sans capitalization)

- ps -aux confirms /usr/sbin/smbd -D and /usr/sbin/nmbd -D as running


Network stuff:
- I'm able to ping from windows to linux, and vice versa

- DHCP is controlled by my router

- Both computers are connected to the same hardware switch


Here's my smb.conf. Previously I had configured limited hosts, etc etc, but I've rolled back some of these settings in my troubleshooting, to get a more "open" configuration file so I can at least get SOME kind of connection before I start locking down to specific hosts, etc etc. Oh, and the *....* lines are masked valid entries for the configuration I'm attempting, in case that wasn't obvious.

Note that the share, /data/shared/ is chmod 444.


# Samba config file created using SWAT
# from 192.168.0.2 (192.168.0.2)
# Date: 2005/05/07 15:41:40

# Global parameters
[global]
workgroup = *my workgroup name*
netbios name = *unique computer name*
server string = %h server (Samba %v)
obey pam restrictions = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
invalid users = root
valid users = *my windows username*

[homes]
comment = Home Directories
create mask = 0700
directory mask = 0700

[shared]
comment = Home Directories
path = /data/shared
create mask = 0700
directory mask = 0700
guest ok = Yes

As far as swat goes, I wouldn't hold your breath. your config actually looks pretty good, have you run testparm to check for errors?

have you tried letting the server set. with samba, addressing tends to work on a broadcast / database sort of model. It's pretty backward actually. makes for good reading....

never the less, it can take up to a day to stabilize. also, You may want to ream man smb.conf regarding maser browser elections, and browse master priority. older versions of samba had a tendency to cuase master browser elections all the time, which completely screw up everything.

You may want to double-check that you've added your user to the samba databse by using the command
make sure you type the same passd as your system password.

attempting to connect by IP is a good idea. You might try connecting to the root share "\\w.x.y.z" first to see if you can connect using the protocol at all. also: have you tried to connect to th server form the server using smbclient?

tha'ts also a good idea, since it might give you more descriptive errors.