Displaying 3 results from an estimated 3 matches for "edsadddm".
2004 Oct 12
2
ADS valid users can't map share
Everything looks fine to me...
net ads info :
# net ads info
LDAP server: 199.42.192.103
LDAP server name: uscosddm001
Realm: EDSADDDM.DDM.APM.BPM.EDS.COM
Bind Path: dc=EDSADDDM,dc=DDM,dc=APM,dc=BPM,dc=EDS,dc=COM
LDAP port: 389
Server time: Tue, 12 Oct 2004 08:22:59 PST
KDC server: 199.42.192.103
Server time offset: 0
wbinfo -u :
# wbinfo -u | grep imguser
EDSADDDM+imguser
smb.conf :
# cat smb.conf
[global]
workgroup...
2005 Mar 04
1
Kerberos Tickets gone after reboot
Has anyone had experience with MIT Kerberos tickets not valid after server
reboot?
After server reboot I have to do a 'kinit' to get a new ticket, re-join the
AD domain, and restart samba. Then all is fine until I have to reboot the
server again.. Same thing again and again.
My time is synced, Kerberos tickets are good for 500d.
2004 Oct 08
0
username map for ADS groups
...*'
********************************************************************************************************
I know of a user that is in the "ADSDOM\Domain Users" group, called
imguser... if I do
getent passwd | grep imguser
I get
ADSDOM+imguser:x:60001:80000:imguser Imaging
User:/home/EDSADDDM/imguser:/bin/false
so, that user is in group 80000, so I do
getent group 80000
and get
EDSADDDM+Domain Users:x:80000:
Now... If I map the space share from a Windows XP client, I get the
following lines in log.smbd:
[2004/10/08 15:16:54, 2] smbd/sesssetup.c:setup_new_vc_session(608)
setup_new_vc...