If you have trouble accessing a machine, are you able to access it from
a windows command line with
net use \\SERVERNAME
or
net use \\SERVERIP
I had upgraded one of my servers from 3.0.x to 3.4.x. I probably missed
something in the compile. Normally an XP/Win7 client should be ab
Did you update the schema on the ldap? Maybe you should. Im right know
doing it. I don't know how many changes are in the schema between 3.0.33
and 3.5.x. Im migrating from 3.0.24 to 3.2.X and if I don't upgrade the
schema the "password must change time" dosen't work.
What do you mean about the dc
The new DC has a new time. We do use LDAP. Which SID are you
referring to? The local SID is new on the new DC, but the domain sids
are the same.
On Tue, Mar 22, 2011 at 10:23 PM, wrote:
> The same happend to me.
> But I didn't have the time to analize the problem. I solve it by changing
> the
The same happend to me.
But I didn't have the time to analize the problem. I solve it by changing
the name of the server. Same ip, but new name and everything works now.
It would be great to know if there is another workaround.
Did you keep the sid of the pdc after the change?
Did you use ldap?
Greetings,
I just did a major upgrade to our Samba infrastructure.
I previously had a domain controller and share running 3.0.33 (on one
box, one samba instance)
I set up a new domain controller running 3.5.8, made that the PDC for
our domain, and changed the (now former) domain controller runni
