Hi all,

I am new to linux an just started a job working with a samba server with XP clients. The guy who left the job left me a mess with little secrets he did to do things. One of these is this: I get a new laptop for a client, I join it to the domain and everything runs fine then after a few days the home drive from the samba server on the XP machine starts to vanish. It isnt the batch file for the XP machine already tried a new one there. DNS and WINS all set up and good to go not there either. Funny thing is on the XP machine all the other drives show up just not their home drive. Im out of ideas and so new to the Linux that there might be something I dont know about. Any help would be great and much needed. I have to say after working with WINDOWS for 8 years Linux is a breath of fresh air, I love it I just need time to get to know it better.

Once the home drive goes - does the client get an error?
Can you get the home drive back by unmapping then remapping the home drive?
Can they access the home drive through a UNC via explorer?
Are you doing LDAP/MS Exchange type stuff?

What you really need is samba logs to see what the server is seeing.
Set sambas log level to something like 10 and see what the logs have to say when one of these "lost home" machines tries to access one.

Yes the drive can be mapped via "my comp map drive" the server lets it be mapped and while mapped everything works fine.Its when you log off and logon again that it is gone. The DOS box pops up as everything loads you see all the other drives mapping out but the home drive is not mapping. No exchange or anything like that running just a simple file server. So I go to "run" and do \\servername\netlogon and click the batch file of the user it runs and bingo drive loads however it tells me that "system error 1314 has occurred I dont know what that is? But everything then works fine until you logoff and login again. When adding the new laptops I do gpedit.msc = prevent roam profile from prop to server and make proxy set per machine rather than per user. Then go to regedit =netlogon=parameters=requiressignorseal set to 0 from 1. From my little knowledge base this should make things work good within the domain, but I have run into this problem. Thanks for the reply to help waiting to see what you think it is.

Hello,
post your smb.conf file here.
Also do one thing suppose home drive is map as h: on windows then from windows xp go to command prompt and try command "start h:"


Pushpraj