Something strange has happened to my Samba server and I'm wondering if anyone out there the can add some insite. My Linux system running Samba is usually up 24x7. Last Friday (4/18) when I left work I could access it from my Windows PC just fine. This morning (Monday 4/21) I could not access the Samba server shares. On the Samba system, using KDE System Guard, both smbd-classic and nmbd, both of which are usually running, where not running. I restarted the system but still no smbd and nmbd. I then went to check the Yast Run level editor, just to see if Samba is still configured to run on levels 2, 3 and 4. I saw and entry for smbfs but nothing else. It's been a while since I checked the Run Level editor so I'm not sure what the entry for the Samba server looks like (smbd??). I then thought to check Yast's install and remove software and encountered a Dependency conflict which mentioned mailx and smtp-deamon. This system has been running fine for months, although under a very light load, only two users use it. Also, Samba is not check, as if it is not installed! This seems very strange to me. What happened? I do need to note that I installed some questionable memory in the server two weeks ago. This Samba server is kind of a test system. The memory in question appeared to have caused some problems in another Lunix system but has been running ok in this Samba system for two weeks (although under a very light load). Could this be caused by a memory problem? Any suggestions or insight? Thanks, Matt