Re: [Samba] New samba server
sgm...@mail.bloomfield.k12.mo.us писал(а) в своём письме Thu, 30 Jul 2009 08:46:50 +0700: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes Well, I am getting ready to take the other server offline and put the new one in place. I am planning on just removing all my machines from the domain and adding them back in to get everything to work, though I would prefer not to do this. I am just not sure where else to look. Thought I would post one last time. I figure that most of this comes from me not knowing a lot about ldap and how samba interacts with it. I am still learning. The passwords on the new server are different than the old. Does that have any affect on it? Do the passwords have to be the same when it comes to the new machine being added
Re: [Samba] New samba server
Serdge V. Pechenko wrote: sgm...@mail.bloomfield.k12.mo.us ÐÉÓÁÌ(Á) × Ó×Ï£Í ÐÉÓØÍÅ Thu, 30 Jul 2009 08:46:50 +0700: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes Well, I am getting ready to take the other server offline and put the new one in place. I am planning on just removing all my machines from the domain and adding them back in to get everything to work, though I would prefer not to do this. I am just not sure where else to look. Thought I would post one last time. I figure that most of this comes from me not knowing a lot about ldap and how samba interacts with it. I am still learning. The passwords on the new server are different than the old. Does that have any affect on it? Do the passwords have to be the same when it comes to the new machine being added in? I did not think that would matter, but maybe it does. If it does then that would mean taht the XP machines somehow saved the password that was used when the machine joined the domain. Thanks for
Re: [Samba] New samba server
sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes Well, I am getting ready to take the other server offline and put the new one in place. I am planning on just removing all my machines from the domain and adding them back in to get everything to work, though I would prefer not to do this. I am just not sure where else to look. Thought I would post one last time. I figure that most of this comes from me not knowing a lot about ldap and how samba interacts with it. I am still learning. The passwords on the new server are different than the old. Does that have any affect on it? Do the passwords have to be the same when it comes to the new machine being added in? I did not think that would matter, but maybe it does. If it does then that would mean taht the XP machines somehow saved the password that was used when the machine joined the domain. Thanks for any info.
Re: [Samba] New samba server
sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes Well, I am getting ready to take the other server offline and put the new one in place. I am planning on just removing all my machines from the domain and adding them back in to get everything to work, though I would prefer not to do this. I am just not sure where else to look. Thought I would post one last time. I figure that most of this comes from me not knowing a lot about ldap and how samba interacts with it. I am still learning. The passwords on the new server are different than the old. Does that have any affect on it? Do the passwords have to be the same when it comes to the new machine being added in? I did not think that would matter, but maybe it does. If it does then that would mean taht the XP machines somehow saved the password that was used when the machine joined the domain.
Re: [Samba] New samba server
sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes Well, I am getting ready to take the other server offline and put the new one in place. I am planning on just removing all my machines from the domain and adding them back in to get everything to work, though I would prefer not to do this. I am just not sure where else to look. Thought I would post one last time. I figure that most of this comes from me not knowing a lot about ldap and how samba interacts with it. I am still learning. The passwords on the new server are different than the old. Does that have any affect on it? Do the passwords have to be the same when it comes to the new machine being added in? I did not think that would matter, but maybe it does. If it does then that would mean taht the XP machines somehow saved the password that was used when the machine joined the
Re: [Samba] New samba server
sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes -- Scott Mayo - System Administrator Bloomfield Schools PH: 573-568-5669 FA: 573-568-4565 Question: Because it reverses the logical flow of conversation. Answer: Why is putting a reply at the top of the message frowned upon? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] New samba server
Have you migrated the user data to the new ldap server? Unless Samba knows about the users, they won't be able to log in. On Tue, Jul 14, 2009 at 1:28 PM, sgm...@mail.bloomfield.k12.mo.us wrote: sgm...@mail.bloomfield.k12.mo.us wrote: I did not get this finished last summer, so decided to just wait and do it this summer. I have setup my new samba server and was trying to get some things tweaked to the way that I want them. I thought that I had asked this before and that I could do it, but it seems that it does not work. My new server is running as a domain server just like the old. It has the same domain name and I change the the SID using net setlocalsid to the same sid number as my old server. This new server is in a test environment right now. I was hoping that my old machines could just log into this server without having to get out of the domain and then rejoin it, but that does not work. It tells me that the domain is not there until I get out of the old one and then rejoin the new one. Is that how it has to work? I was hoping I would not have to do that if I left the domain name the same and set the SID on the new server. I just want to make sure I am not missing something before I go around to all 400 computers on campus and have them removed and rejoined to the domain. Mr. Terpstra gave me a bit of help. I had done nothing to set my domainsid, but after doing the following: net getlocalsid net getdomainsid The values are the same on both the old and the new samba server. This new server will take the place of my old one. Right now it is on a network with nothing else on it besides one of my old windows clients. If I remove one of my old clients from the domain and then re-add it, then it logs in just fine. If I take an old client from my current network and put it on this new network and try to login to the new samba server then it gives me the typical: Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear contact your System Administrator for assistance. The name of the Windows machine is business18 so I did an 'smbldap-adduser -w business18$' to make sure the machine account was added in to the directory, but the error was the same. I even changed the uid of the machine account to match the old one in case that was coming into play. Here is my samba config in case someone sees something that I don't. Which is quite possible since I forget more than I learn it seems. :) I'll be reading on the How-To to see if I can pick anything else up. [global] workgroup = BES server string = Samba Server Version %v netbios name = SCHOOL interfaces = lo eth0 hosts allow = 127. 10.0. 19 2.168.0. localhost ldap passwd sync = Yes ldap admin dn = cn=Manager,dc=school,dc=bloomfield.k12.mo.us ldap suffix = dc=school1,dc=bloomfield.k12.mo.us ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u ldap delete dn = Yes add group script = /usr/sbin/smbldap-groupadd -p %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u Dos charset = 850 Unix charset = ISO8859-1 log file = /var/log/samba/log.%m max log size = 50 security = user passdb backend = ldapsam:ldap://127.0.0.1 domain master = yes domain logons = yes local master = yes os level = 65 preferred master = yes wins support = yes dns proxy = no load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes -- Scott Mayo - System Administrator Bloomfield Schools PH: 573-568-5669 FA: 573-568-4565 Question: Because it reverses the logical flow of conversation. Answer: Why is putting a reply at the top of the message frowned upon? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] New samba server
Ryan Bair wrote: Have you migrated the user data to the new ldap server? Unless Samba knows about the users, they won't be able to log in. No. I was wanting to start off clean. I have a perl script that I wrote that will add the users in at one time. I just created one user and one machine account right now to test with. Mr. Terpstra suggested using slapcat and slapadd. I could do that, but I am actually planning on changing usernames. I use to truncate them at 8 characters, but I plan on quitting that. I am going with firstinitial.lastname. I'll look at slapcat. Maybe I can just export the machines and not the users. I am still a bit stumped on why this does not work though if I have added the machine into the ldap directory. Does Windows actually store some information about the domain also that could be causing the problem? I have a feeling that this upgrade is going to be a pain in the butt when the teachers get back. Especially with the name changes, because that means when they login, a new profile is going to be created and all of their documents will be in the other profile. I have warned and warned them to keep things backed up, and not just leave them on the computer so... -- Scott Mayo - System Administrator Bloomfield Schools PH: 573-568-5669 FA: 573-568-4565 Question: Because it reverses the logical flow of conversation. Answer: Why is putting a reply at the top of the message frowned upon? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
RE: [Samba] New Samba Server
3ware makes great controllers, but you will be limited to the pci bus bandwidth for the raid arrays. instead of 8x40 I would look for the best cost/size ratio. I think 120GB hard drives can be found for around $100.00 (us) I'd put 3 in a raid5 array for performance. Take care, Seth 727-919-1598 [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Rowe Sent: Wednesday, June 18, 2003 12:20 AM To: [EMAIL PROTECTED] Subject: [Samba] New Samba Server I'm currently looking at hardware specs for a samba server, its' job will be to hold general office files, cad / solidworks files along with approximately 40 outlook PST files that will be opened off the server. Here are the current specs I'm looking at.. AMD 2600XP Asus A7N8X Deluxe nVidia Serial ATA 2 x 512 MB PC2700 DDR 333 = 1024MB ASUS S520/Generic 52X CD-ROM (OEM) ASUS GrForce4 MX440-8X 64MB DDR D-Link DGE-550T 32/64-Bit PCI-Bus Copper (RJ45) 3Ware Escalade 7500-8 8 x 40gb ata-100 7200.7 drives 3Ware Escalade 7500-4 4 x 40gb ata-100 7200.7 drives The 7500-8 will be holding the office and cad / solid works files and the 7500-4 will be holding the PST files (I thought it was best to keep them on a separate controller cards.) Will this do a reasonable job in keeping up with a gigabit network? And is running PST files off the server like this a feasible option?? Any suggestions on hardware improvements would be appreciated as without the hardware to test with I'm purchasing quite blindly here :| Thanks Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] New Samba Server
On Wednesday, June 18, Seth Hollen wrote: 3ware makes great controllers, but you will be limited to the pci bus bandwidth for the raid arrays. instead of 8x40 I would look for the best cost/size ratio. I think 120GB hard drives can be found for around $100.00 (us) I'd put 3 in a raid5 array for performance. Hi Seth and Tim: One other comment - the Escalade 7500 series cards are PCI-X cards (64-bit) if you can afford the motherboard that has these slots, having that extra bandwidth will be a big performance boost. I'm using the 7500-4LP and 4x120GB Western Digital drives in my backup server right now - it's a sweet setup! :-) Later, -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] New Samba Server
I've been lead to believe that the more drives on the raid 5 the faster the output, as I don't want the hard drive setup as the bottleneck... The cost between having 3 x 100gb drives and 8 x 40gb drives isn't a huge issue... -Original Message- From: Seth Hollen Sent: Thursday, 19 June 2003 1:46 a.m. 3ware makes great controllers, but you will be limited to the pci bus bandwidth for the raid arrays. instead of 8x40 I would look for the best cost/size ratio. I think 120GB hard drives can be found for around $100.00 (us) I'd put 3 in a raid5 array for performance. -Original Message- Sent: Wednesday, June 18, 2003 12:20 AM To: [EMAIL PROTECTED] Subject: [Samba] New Samba Server I'm currently looking at hardware specs for a samba server, its' job will be to hold general office files, cad / solidworks files along with approximately 40 outlook PST files that will be opened off the server. Here are the current specs I'm looking at.. AMD 2600XP Asus A7N8X Deluxe nVidia Serial ATA 2 x 512 MB PC2700 DDR 333 = 1024MB ASUS S520/Generic 52X CD-ROM (OEM) ASUS GrForce4 MX440-8X 64MB DDR D-Link DGE-550T 32/64-Bit PCI-Bus Copper (RJ45) 3Ware Escalade 7500-8 8 x 40gb ata-100 7200.7 drives 3Ware Escalade 7500-4 4 x 40gb ata-100 7200.7 drives The 7500-8 will be holding the office and cad / solid works files and the 7500-4 will be holding the PST files (I thought it was best to keep them on a separate controller cards.) Will this do a reasonable job in keeping up with a gigabit network? And is running PST files off the server like this a feasible option?? Any suggestions on hardware improvements would be appreciated as without the hardware to test with I'm purchasing quite blindly here :| Thanks Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
