By now we had running samba as PDC and fileserver for about 20
NT4-clients with roaming profiles.
Now we start migrating NT4-clients to XP-clients and as I found out
roaming userprofiles between XP and NT4 is not possible (NT4->XP
works, but not vice versa).
So I just thought about cloning all the profiles (docs and mails are
not in the profiles so only bookmarks, adressbook and backgroundpics
hasve to be maintained twice by roaming users) to get an NT4-branch
and a XP-branch and setup a second domain and run a different samba
for it that binds to a virtual interface that is in the same subnet.
(same subnet would be great cause we use dhcp and introducing a new
subnet will cry for troubles)
my questions :
* What troubles do I have to expect ?
* Will this cause lot of master-challenging traffic on the net ?
* should both sambas act as WINS-server ? (dont think so)
* will the machines in the nt4-domain (that have all the printers)
propagate their shares to the xp-domain ?
* why cant I use 'bind interfaces only' in such a config ? (the second
smbd will refuse to start then cause 'adress already in use')
* does it matter if I use the sama passwd-files for both sambas
* any other idea to solve the profile-issue ?
thnx a lot,
peter
my current config:
lets say:
nt4-pdc : eth0 : 192.168.1.1/24 : smb.nt4.conf
xp-pdc : eth0:0 : 192.168.1.2/24 : smb.xp.conf
smb.nt4.conf
[global]
bind interfaces only = no
interfaces = 127.0.0.1/32 192.168.1.0/24
socket address = 192.168.1.1
netbios name = server
name resolve order = host
wins proxy = yes
wins support = yes
workgroup = domain
domain logons = Yes
lock directory = /usr/local/samba/var/locks
pid directory = /usr/local/samba/var/locks
os level = 255
preferred master = Yes
logon drive = o:
logon home = \\server\%U
logon path = \\server\profiles\%U
logon script = startup.bat
security = user
smb.xp.conf
[global]
bind interfaces only = no
interfaces = 127.0.0.1/32 192.168.1.0/24
socket address = 192.168.1.2
netbios name = server_xp
name resolve order = host
wins proxy = yes
wins support = yes
workgroup = domain_xp
domain logons = Yes
lock directory = /usr/local/samba/var/locks_xp
pid directory = /usr/local/samba/var/locks_xp
os level = 255
preferred master = Yes
logon drive = o:
logon home = \\server_xp\%U
logon path = \\server_xp\profiles\%U
logon script = startup.bat
security = user
--
mag. peter pilsl
IT-Consulting
tel: +43-699-1-3574035
fax: +43-699-4-3574035
pilsl@goldfisch.at
http://www.goldfisch.at
pilsl@goldfisch.at wrote:> By now we had running samba as PDC and fileserver for about 20 > NT4-clients with roaming profiles. > > Now we start migrating NT4-clients to XP-clients and as I found out > roaming userprofiles between XP and NT4 is not possible (NT4->XP > works, but not vice versa). >> (trimmed)> * any other idea to solve the profile-issue ? >The easiest way is for the server to store profiles for different versions of Windows in different directories. You only need one PDC. Include the following line in smb.conf: logon path = \\server\profile\%a\%U The %a expands to WfWg, Win95, WinNT, Win2K or WinXP depending on the version of Windows users are connecting from. WinXP was added in Samba 2.2.8, before that it was identified as Win2K. Just create the WinNT and WinXP directories in the profile the directory, move the user profiles to WinNT and copy them to WinXP. I saw one person report that WinXP was identified as Win2K but I am not sure if they were using an older version of Samba or if there is a bug. I have been using this approach with Windows NT and Windows 2000 for some time now. I should be installing my first XP client tomorrow. Nick