I'm trying to add a linux share to the local windows network

I've set up my smb.conf file and the server name appears in my local usergroup on all machines on the Lan.

I have an NT4 server (which the intranet is presently hosted) on which I've been testing the local network to see that I could share with the linux machine, which I can with no probs. I click on the name and a password/username box appears and I login to the share. Yippeee!

Returning to my XP Pro, Win 2000 and NT4 workstations, I notice that, although the linux server (called lizardserver) is listed in my local network, clicking on or trying to map to to it gives me the following error messages:

XP Pro:
'\\Lizardserver is not accesible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The Network path was not found'

98: '\\Lizardserver is not accessible. The network path could not be found'

2000: '\\Lizardserver is not accessible. The network path could not be found'

I am logging into the windows network with the same details
and admin rights.

Any clues as where I'm going wrong. My Config file is basic as I'm a complete networks newbie.

Here's my file - Can anyone help?---------

# global parameters

[global]

workgroup = portslade_cc
netbios name = lizardserver
server string = Sambatastic on the Lizardserver
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd


[homes]
read only = no
browseable = no

[pcc]
path = /pcc
browseable = yes
public = yes
read only = no

[apps]
path = /data/everyone
browseable = yes
valid users = @admins, root
write list = @admins, root

"Authenticating other Samba Servers"
In a system that has a number of servers you only need one password database. The machines that don't have their own ask the PDC to check for them. The following lines in smb.conf are typical, 'password server' points to the PDC, samba machine or an NT, that has the password list :

# Samba 2.0.7
# partial smb.conf on turkey
#
[global]
...
security = domain
workgroup = dAgobAh
password server = 192.168.20.222 ; magpie (samba PDC)
encrypt passwords = yes
...

The samba server in question will have to 'join the domain', that requires the PDC to have a machine account for it. This is no different to the machine account requirements to allow an NTworkstation to join the domain. For example, if we want a linux samba server called 'turkey' to ask our PDC called 'magpie' to do its authentication then 'magpie' will need an entry in its smbpasswd (assuming it's also samba) that starts with 'turkey$'. After the machine account for 'turkey' has been created on 'magpie' and the above entries have been added to 'turkey's' smb.conf, reload smb on 'turkey'
(root)# service smb restart

Note: the servers without the password list still need an account for each user, this means a line in /etc/passwd. If the server is only being used to offer Samba type file or print shares then the /etc/passwd line does not need a password. If the shares being offered are not user specific, ie a common (read only ?) area or perhaps just printing then the /etc/passwd does not need a home directory. A typical line in /etc/passwd for a server that allows domain users to connect to the samba shares but does not offer a home share ('cos it's on the PDC) and does not allow logon to the unix prompt would be like this:
obi-wan:x:542:100bi-wan kenobi:/dev/null:/bin/false

Errrr, okay - sort of...

I need to add the lines:

security = domain
password server = 192.168.20.222 ; magpie (samba PDC)

to my global settings replacing the IP address with that of my password server followed by the ';' and then the name of my linux server - yes?

Also: do I keep the : smb passwd file = /etc/samba/smbpasswd
line or not?

Perhaps you could update the global setting in my config file to show me what you mean.

Also, there is only one linux server - and that is the one I'm trying to get my Win network to get access to.

Have tried changes but to no avail. Same messages. I'm quite stumped on this one. Any clues to why the share should work fine on NT4 Server, and not on any user machines?