| 6 | | == The installer asks me for a password of the "root" account. I don't want a "root" account. Can I savely ignore that? == |
| | 6 | == Installation and configuration == |
| | 7 | ---- |
| | 8 | === When I try to run Samba, nmbd.exe runs, but smbd.exe stops immediately. What's wrong here? === |
| | 9 | That usually means that the guest account has not been setup properly. Go to the command line and run usermod.cmd without any parameter. This will tell you what's wrong.[[BR]][[BR]] |
| | 10 | ''Note: The warning about the unknown root shell can savely be ignored. |
| | 11 | ---- |
| | 12 | === The installer asks me for a password of the "root" account. I don't want a "root" account. Can I savely ignore that? === |
| 12 | | == I want to try Samba Server for eCS(OS/2), but I have installed NetBIOS over TCP/IP and I do not want to screw this machine. Anything I can do for a quick and painless test? == |
| | 18 | === I see a completely erratic behaviour, when I try to add users to groups - I always get NT_ACCESS_DENIED errors, although credentials should be sufficient. Sometimes the user appears magically after the next operation. What is wrong here? === |
| | 19 | The problem is located in the group file and in the (now deprecated) addusertogroup.cmd and deluserfromgroup.cmd scripts. The userlist '''MUST''' be terminated by a comma. Examples of the group file syntax floating around neglect this issue, and the scripts mentioned above do not provide the comma either (use the smbusers package published [http://members.aon.at/herwig.bauernfeind/samba/index.html here ] to deal with users and groups ).[[BR]][[BR]] |
| | 20 | Each line of your group file should look like this: |
| | 21 | {{{ |
| | 22 | ntadmin:*:3019:root,paul,herwig,master,administrator, |
| | 23 | }}} |
| | 24 | |
| | 25 | ''Note: For real Unix it seems that it does not matter whether the trailing comma is added or not. The OS/2 implementation in klibc however depends upon this trailing comma in order to work properly.''[[BR]] |
| | 26 | ---- |
| | 27 | === Does Samba really need this libc063x.dll, I have libc063.dll anyway? I want to get rid of one of these two files! This is the DLL hell! === |
| | 28 | Samba comes with an enhanced version of [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] named libc063x.dll. In order to run Samba successfully you must have this file, the standard [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] does not work for Samba. The two DLLs are not interchangeable and you cannot just rename one or the other. Please note that you also must not rename libc063x.dll to [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] in order to use the enhanced DLL with other applications. This will not work either.[[BR]][[BR]] |
| | 29 | ''Note: Samba version 3.0.30 and later come with libc064x.dll. So libc063x.dll is obsolete and can savely be removed from your system. You must '''NOT''' delete [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] however! |
| | 30 | |
| | 31 | ---- |
| | 32 | == Prerequisites == |
| | 33 | ---- |
| | 34 | === I want to try Samba Server for eCS(OS/2), but I have installed NetBIOS over TCP/IP and I do not want to screw this machine. Anything I can do for a quick and painless test? === |
| 31 | | == The current utilities packaged with Samba server for eCS (OS/2) only have a limited feature set. How can I configure all the other features without messing with commandline utilities? == |
| | 53 | === How should my protocol bindings look like in MPTS? === |
| | 54 | You must not have installed NetBIOS over TCP/IP. Samba server uses the same ports and thus cannot run at the same time as NetBIOS over TCP/IP. This is no bug and no limitation of the OS/2 version, this just the way Samba works.[[BR]] |
| | 55 | |
| | 56 | The most simple protocol binding in MPTS would look like the following (in case no Virtual Machine solution such as VirtualPC, SVISTA or !VirtualBox is installed):[[BR]] |
| | 57 | |
| | 58 | {{{ |
| | 59 | Intel(R) Pro 1000 network connection....... (for example) |
| | 60 | 0 - IBM TCP/IP |
| | 61 | }}} |
| | 62 | ---- |
| | 63 | == Feature set == |
| | 64 | ---- |
| | 65 | === The current utilities packaged with Samba server for eCS (OS/2) only have a limited feature set. How can I configure all the other features without messing with commandline utilities? === |
| 53 | | ---- |
| 54 | | == I see a completely erratic behaviour, when I try to add users to groups - I always get NT_ACCESS_DENIED errors, although credentials should be sufficient. Sometimes the user appears magically after the next operation. What is wrong here? == |
| 55 | | The problem is located in the group file and in the (now deprecated) addusertogroup.cmd and deluserfromgroup.cmd scripts. The userlist '''MUST''' be terminated by a comma. Examples of the group file syntax floating around neglect this issue, and the scripts mentioned above do not provide the comma either (use the smbusers package published [http://members.aon.at/herwig.bauernfeind/samba/index.html here ] to deal with users and groups ).[[BR]][[BR]] |
| 56 | | Each line of your group file should look like this: |
| 57 | | {{{ |
| 58 | | ntadmin:*:3019:root,paul,herwig,master,administrator, |
| 59 | | }}} |
| 60 | | |
| 61 | | ''Note: For real Unix it seems that it does not matter whether the trailing comma is added or not. The OS/2 implementation in klibc however depends upon this trailing comma in order to work properly.''[[BR]] |
| 62 | | ---- |
| 63 | | == How should my protocol bindings look like in MPTS? == |
| 64 | | You must not have installed NetBIOS over TCP/IP. Samba server uses the same ports and thus cannot run at the same time as NetBIOS over TCP/IP. This is no bug and no limitation of the OS/2 version, this just the way Samba works.[[BR]] |
| 65 | | |
| 66 | | The most simple protocol binding in MPTS would look like the following (in case no Virtual Machine solution such as VirtualPC, SVISTA or !VirtualBox is installed):[[BR]] |
| 67 | | |
| 68 | | {{{ |
| 69 | | Intel(R) Pro 1000 network connection....... (for example) |
| 70 | | 0 - IBM TCP/IP |
| 71 | | }}} |
| 74 | | == Does Samba really need this libc063x.dll, I have libc063.dll anyway? I want to get rid of one of these two files! This is the DLL hell! == |
| 75 | | Samba comes with an enhanced version of [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] named libc063x.dll. In order to run Samba successfully you must have this file, the standard [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] does not work for Samba. The two DLLs are not interchangeable and you cannot just rename one or the other. Please note that you also must not rename libc063x.dll to [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] in order to use the enhanced DLL with other applications. This will not work either.[[BR]][[BR]] |
| 76 | | ''Note: Samba version 3.0.30 and later come with libc064x.dll. So libc063x.dll is obsolete and can savely be removed from your system. You must '''NOT''' delete [ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi libc063.dll] however! |
| 77 | | ---- |
| 78 | | == What is faster, Samba Server for eCS (OS/2), IBM Peer, LAN Server or !WarpServer for eBusiness? == |
| 79 | | The Samba Server provides a much better performance than all the older IBM products on a given hardware. The Samba Client is slower than the IBM LAN Requester. Speedwise the order of possible combination is the following: |
| 80 | | 1. Samba Server plus IBM LAN Requester (fastest) |
| 81 | | 2. Samba Server plus Samba Client |
| 82 | | 3. IBM Peer/LAN Server/WSeB plus IBM LAN Requester (slowest) |
| 83 | | |
| 84 | | ''Note: The combination IBM Peer/LAN Server/WSeB plus Samba Client is untested. It is probably the slowest and least stable combination anyway.''[[BR]][[BR]] |
| 85 | | ''Note: Recent experiments showed that Samba Server for eCS(OS/2) behaves extremely asymmetric when it comes to compare read and write speeds. While read speed is very fast (typically 16.000 to 26.000 KB/sec.), write speed is very slow (typically 150 KB/sec.). The problem is the very same that directly leads to [http://svn.netlabs.org/samba/ticket/69 Ticket #69] and [http://svn.netlabs.org/samba/ticket/71 Ticket #71]. This problem has existed for every Samba build (tested back to version 3.0.25pre1). With [http://svn.netlabs.org/samba/changeset/170 Revision 170] Samba now writes with speeds of around 11.000 Kb/sec.[[BR]] |
| 86 | | ---- |
| 87 | | == What about stability? Is Samba for eCS (OS/2) stable enough to run my company's network? == |
| 88 | | There are several case studies where Samba Server for eCS (OS/2) is already used in a real life office environment successfully for approximately a year, without real problems. Nevertheless Samba still has quirks and in its current status is more difficult to handle than the older IBM products (which definitely also have quirks and limitations, especially when it comes to newer Windows clients).[[BR]] |
| 89 | | ---- |
| 90 | | == Which OS/2 components are replaced by Samba? == |
| | 89 | === Which OS/2 components are replaced by Samba? === |
| 116 | | == Marcel Müller wrote: == |
| | 115 | == Miscanellous == |
| | 116 | ---- |
| | 117 | === What is faster, Samba Server for eCS (OS/2), IBM Peer, LAN Server or !WarpServer for eBusiness? === |
| | 118 | The Samba Server provides a much better performance than all the older IBM products on a given hardware. The Samba Client is slower than the IBM LAN Requester. Speedwise the order of possible combination is the following: |
| | 119 | 1. Samba Server plus IBM LAN Requester (fastest) |
| | 120 | 2. Samba Server plus Samba Client |
| | 121 | 3. IBM Peer/LAN Server/WSeB plus IBM LAN Requester (slowest) |
| | 122 | |
| | 123 | ''Note: The combination IBM Peer/LAN Server/WSeB plus Samba Client is untested. It is probably the slowest and least stable combination anyway.''[[BR]][[BR]] |
| | 124 | ''Note: Recent experiments showed that Samba Server for eCS(OS/2) behaves extremely asymmetric when it comes to compare read and write speeds. While read speed is very fast (typically 16.000 to 26.000 KB/sec.), write speed is very slow (typically 150 KB/sec.). The problem is the very same that directly leads to [http://svn.netlabs.org/samba/ticket/69 Ticket #69] and [http://svn.netlabs.org/samba/ticket/71 Ticket #71]. This problem has existed for every Samba build (tested back to version 3.0.25pre1). With [http://svn.netlabs.org/samba/changeset/170 Revision 170] Samba now writes with speeds of around 11.000 Kb/sec.[[BR]] |
| | 125 | ---- |
| | 126 | === What about stability? Is Samba for eCS (OS/2) stable enough to run my company's network? === |
| | 127 | There are several case studies where Samba Server for eCS (OS/2) is already used in a real life office environment successfully for approximately a year, without real problems. Nevertheless Samba still has quirks and in its current status is more difficult to handle than the older IBM products (which definitely also have quirks and limitations, especially when it comes to newer Windows clients).[[BR]] |
| | 128 | |
| | 129 | ---- |
| | 130 | === Marcel Müller wrote: === |
