Differences between version 14 and previous revision of SambaErrorMessages.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 14 | Last edited on Monday, March 13, 2006 11:35:37 am | by ChrisLucas | Revert |
Older page: | version 13 | Last edited on Monday, March 13, 2006 11:33:06 am | by ChrisLucas | Revert |
@@ -52,13 +52,14 @@
!!When using wbinfo to test operability <i>Error looking up domain users</i> is returned plus only the <i>builtin</i> groups returned on test
I had a lot of trouble finding a solution to this problem and found that once the time was set on the system (ntpd) and the winbind / samba databases were recreated that all worked (this problem first occoured on a VM, hence why the time issue may have triggered the situation).
-The databases can be recreated by stopping
the samba and winbind services
-Backing up the samba database (just in case of course)
-Rejoining the domain
-Restart the samba and winbind services
-Reset the Samba authentication (wbinfo --set-auth-user user%password)
+The databases can be recreated by:
+*Stopping
the samba and winbind services
+*
Backing up the samba database (just in case of course)
+*
Rejoining the domain
+*
Restart the samba and winbind services
+*
Reset the Samba authentication (wbinfo --set-auth-user user%password)
-At this point all started working again. However, please note,
-A) Time is very important to Active Directory (hence ntpdate or ntpd is important)
-B) VM's dont work so well with time, hence, not so well with directories (please correct me if you have found a work around!)
+At this point all started working again. However, please note, <br>
+A) Time is very important to Active Directory (hence ntpdate or ntpd is important)<br>
+B) VM's dont work so well with time, hence, not so well with directories (please correct me if you have found a work around!)<br>