search for: s10629

...\007masociete\000"; option wpad "\n"; ------------- but I do not see how dhcp could impose windows pc to use another domain to connect? When I add a machine to the domain I go through the machine's bone and change the "Member of" setting as in this picture: https://s10629.pcdn.co/wp-content/pictures/2009/11/joindomainwindows7.png Philippe. > > Rowland > >

...name the domain, every instance of 'samdom', 'example' and 'com' will get changed to match your new name. Rowland > When I add a machine to the domain I go through the machine's bone > and change the "Member of" setting as in this picture: > https://s10629.pcdn.co/wp-content/pictures/2009/11/joindomainwindows7.png > That is joining the domain, but if your clients get their DNS domain via DHCP and you rename the domain, everything should match and you probably wont have to rejoin, but I don't really know. Rowland

Hello, I realize the preparation of the migration from samba 3 to samba 4. For the moment the test platform is functional at 80%. I realize a problem. At the implementation of samba 3 in NT mode (more than 10 years ago) I chose netbios name dom.masociete and the same DNS domain name. With the migration the domain dns becomes "dom" and according to my first researches I will quickly

...migration of samba 3 to 4 with the original configuration and then to migrate a samba domain 4 to another domain samba 4? > >> When I add a machine to the domain I go through the machine's bone >> and change the "Member of" setting as in this picture: >> https://s10629.pcdn.co/wp-content/pictures/2009/11/joindomainwindows7.png >> > That is joining the domain, but if your clients get their DNS domain > via DHCP and you rename the domain, everything should match and you > probably wont have to rejoin, but I don't really know. > > Rowland O...