id summary reporter owner description type status priority milestone component version resolution keywords cc 145 Problems with SAMBA server 1.1.0 David McKenna Herwig Bauernfeind " Thanks for all you have done with SAMBA! Today was a rainy day, so I stayed home and spent some time trying the recent versions of SAMBA server you have released. My setup: SAMBA Domain Server running eCS 1.2MR, Client running eCS 2.0GA, Client running WinXP SP3, Client (Laptop) dual boot eCS 2.0 and WinXP. I have SAMBA 1.0.4 installed and configured for my setup. Everything works. I installed 1.0.5 (from the WPI) and I was able to use everything as before. All clients logon (I use IBM LAN Logon on eCS), see the shares and I can use the utilities as well as SWAT. I made a copy of smb.conf, then installed 1.1.0 from the WPI. After installation, I added all of the same users as before (there are 6, including 2 machines). I tried to start SWAT, but I got an 'Internal Server Error' (using Apache 2.2.16). I switched to SSCC and added the Domain name, then restarted. The Windows clients could logon and see shares (after joining the domain), but not the eCS clients - the logon would fail and the dialog for name, password and domain would reappear. I then copied the old smb.conf (which worked before with 1.0.5) over the new one and restarted SAMBA, but still only the Windows clients could logon. I then un-installed 1.1.0 (using WarpIn) and deleted all remnants of files and directories of SAMBA, then rebooted. Next I installed 1.1.0 fresh, but after install still could not use SWAT (Internal Server Error), so again used SSCC to change domain name, then added users as before. Still, only the Windows clients could logon. Adding the saved smb.conf did not help here either. I decided to give up and un-installed 1.1.0, then re-installed 1.0.5, then added users and domain. Once again everything worked fine. My knowledge of the internals of SAMBA is sketchy at best, but it seems smb.conf only contains those entries that are not 'default'. Perhaps 'defaults' have changed in version 1.1.0 so I need to add something to get the eCS clients to logon? I will continue to scrutinize defaults for 1.0.5 and 1.1.0 - maybe something will jump out... Still a mystery why SWAT won't work though... " defect closed major Samba Server for eCS (OS/2) 1.1.0 Samba Server GUI Tools Server 3.3.x fixed