Or, save a bundle and switch it all to Debian or something. :D

Linux: "echo hello" other Linux: "Oh hi how you been?"

John W.... I am trying to move away from Windows

then why are you trying to set up samba for WINDOWS XP to talk to the linux machines

if all you need to do is move data off the old xp computer then use a usb thumb drive

The actual samba config looks ok. It has the correct interfaces assigned. Not sure what causes your issue, but for nmbd, you can do something like

When the samba configuration changes, new connections will automatically use the new config file. You don't need to restart unles you changed the netbios or workgroup. For those it is better to restart.

Try setting wins proxy to no as well.

http://oreilly.com/openbook/samba/book/ch07_03.html

If you go through that book available freely online, you can make a much more simple samba.conf.

Is winblow$ set to allow the connection and be seen?

So what is the current status?
As stated is nmbd and smbd running? These are the samba server daemons so windows PCs can connect to linux. If running correctly the linux PCs should show up in network neighbourhood. You can also use the net command in a windows CMD box to see all shares i.e.

net view
or
net view \\netbios_name

Another thing that would help is enabling netbios over TCP/IP on the windows box. Someone correct me but it could be required if not running a WINS or DNS server.

My understanding was that the windows boxes are fine. The issue is with linux boxes.

But you are correct. Port 445 is used with newer versions of windows rather than udp ports. Wins is not an requirement. It just eases joining machines on the network so all samba server don't have to go through the election process to determine the master browser. It makes the service a lot more stable.

nmbd seems to be running process 1229 but I don't understand about 1232?

ds@WA3SCM-HOME:~$
ds@WA3SCM-HOME:~$ ps -A | grep nmb
1229 ? 00:00:01 nmbd
1232 ? 00:00:00 nmbd
ds@WA3SCM-HOME:~$ service nmbd status
nmbd start/running, process 1229
ds@WA3SCM-HOME:~$

smbd seems to be running process 724
ds@WA3SCM-HOME:~$
ds@WA3SCM-HOME:~$ service smbd status
smbd start/running, process 724
ds@WA3SCM-HOME:~$
ds@WA3SCM-HOME:~$ ps -A | grep smbd
724 ? 00:00:01 smbd
913 ? 00:00:00 smbd
ds@WA3SCM-HOME:~$

Net view on windows reveals only the windows boxes

Net view \\WA3SCM-HOME (my Linux box) reveals
system error 53 has occured
the network path was not found


Windows wireless connection to router:
X client for microsoft networks
x file and print sharing for microsoft networks
x qos packet scheduler
x internet protocol tcp/ip

tcp/ip:
General
obtain an ip address automatically
use following dns server address 192.168.1.108 (linux box ip inside router)
General Advanced IP settings
ip addresss dhcp enabled
no default gateways
x autometric metric
General Advanced DNS
dns server addresses in order of use 192.168.1.108
x append primary and connection specific dns suffixes
x appent parent suffixes of the primary dns suffix
x register this connections addreses in dns
General Advanced WINS
wins address in order of use 192.168.1.108
x enable lmhosts lookup
x enable netbios over tcp/ip
General Advanced Options
tpc/ip filtering
General Advanced Options Properties
x enabel tpc/ip filtering all adapters
x permit all tcp ports
x permit all udp ports
x permit al ip protocols



ericson007 I set wins proxy to no with no change in operation.

tomorrow I will create a new simpler smb.conf

Thanks for caring.

Don't bother with changing config just yet...

Did you by any chance try

In nautilus?

smb://... is not a command in ubuntu unity
I am searching for an equivalent command.

there is, but you have to use it in Nautilus, not just the unity interface. With your file manager (nautilus) open, hold down alt. In the menu bar that appears, select File and Connect to Server. Enter you server like this: smb://ip.adddress.here/share_name

Removed - Accidental double post.

It should work like that yes, but we are also trying to make sure the name can be resolved. Leaving out the share name should also correctly display all the shares available.