I have an NT 4.0 wkstn with an account on an NT domain. The user needs to access shared files on a unix box which runs Samba. The NT user is valid in the smb.conf file as below: # Global parameters [global] workgroup = SERV-UNIX server string = miserv media info server max log size = 50 dns proxy = No hosts allow = 100.1. 172.17. 127. [homes] comment = Home Directories read only = No browseable = No [intranet] comment = HTML directories path = /user1/apache/htdocs valid users = pa04 read only = No [itdoc] comment = IT documentation path = /user1/apache/itdoc valid users = pa04 read only = No [ftpanon] comment = Data for anonymous ftp path = /user1/ftpanon/pub valid users = pa04 read only = No Occasionally I can access the drive without entering a password. I then map the drive accordingly but upon rebooting it asks for a username and password then denies access anyway even though I accessed it before without name or password. I have enabled plain test password in the registry as per microsoft site. Should I add anything more to the smb.conf file to or do I need to change something else in NT. (This seems to happen to some of our Windows 98 workstations as well). Thanks for any help

i cant see that you have made a log file for the useres were it will show that they have loged in all so you sould add domain master = yes domain logon = yes .. But any way in this file i explained to you earlyer you can see what goes wrong my guess is that it can't finde the password file were it holds all the passwords for the useres that logon to your domain and when it can't fined this file it's simply denies access to the domain server... Also you should be carefull with making a FTP server because a FTP server is like a superhigh way for a hacker, because even thoe you have specified the directory for the ftp folder i'ts possibel for a hacker to create a new folder and there by getting access to your hole system especialy if the anomumos account for the FTP server is still active and you havent altered it in altering i mean cutting of the arms and legs of this account so the only thing one can do is logon.... But back to the problem with the samba logon i have a similar problem with that as well and have taken the liberty of copying your samba script to compare it against my own to see if i missed out any thing