search for: oldhom

...ap-proxy:/bin/sh It returns the uid that was entered on the Unix Attributes tab of my Win2003 w/SFU AD entry. So it looks like domain users are being mapped identically, on both machines. Yet trying to mount a share from workhorse onto Dual-Booter fails: (on Dual-Booter) # smbmount //workhorse/OldHome /OldHome -o username=DACRIB+turgon Password: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) So I did a "echo 1 > /proc/fs/cifs/cifsFYI" and tried again, and then saw this, in syslog: /build/buildd/linux-2.6.32/fs/cifs/cifsfs.c: Dev...

clients on the domain. But I can not mount shares from the other Samba server; I always get "Permission denied". $ sudo mount -t cifs //workhorse/OldHome /mnt/OldHome -o username=DACRIB+turgon --verbose Password: mount.cifs kernel mount options: unc=//workhorse\OldHome,ver=1,rw,username=DACRIB+turgon,ip=10.0.0.20,pass=******** mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) The user DACRIB+turgon is...

Honestly, it's enough to make you scream. :-( I can't seem to mount a samba share: $ mount -t smbfs //workhorse/OldHome /network -o username=DACRIB+turgon,password=xxxxxx mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) (I'm logging into this laptop as the domain user DACRIB+turgon, domain = DACRIB. That part works perfectly.) I have the share name right, and I...

...enable privileges = Yes restrict anonymous = 2 wide links = no [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers [OldHome] comment = The Old Home Folder read only = No path = /OldHome

...writable = Yes enable privileges = Yes restrict anonymous = 2 [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers [OldHome] comment = The Old Home Folder read only = No path = /OldHome

.../data/samba # smbclient -L oink Password: Domain=[CORP1] OS=[Unix] Server=[Samba 3.0.7] Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers Share software Disk Software for Samba computers oldhomes Disk Novell Home Directories DATA Disk ENGR Disk IPC$ IPC IPC Service (Samba 3.0.7) ADMIN$ IPC IPC Service (Samba 3.0.7) root Disk Home Directories

...nvalid users = root read only = No create mask = 0700 directory mask = 0775 hide dot files = No wide links = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No browsable = No [print$] comment = Printer Drivers path = /var/lib/samba/printers [OldHome] comment = The Old Home Folder path = /OldHome Thanks for any help.

So I ended up doing a net ads leave which removed the machine account from Active directory. Now I am trying to re-add it, but it seems to still be hanging around in Kerberos ... root at workhorse:/etc# klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal: administrator at DACRIB.LOCAL Valid starting Expires Service principal 04/24/10 17:25:50 04/25/10 03:25:55

Once again, I am trying to add a machine to my Win2003 AD (that has Services for Unix installed). I am using Xubuntu 9.10, and samba 3.4.0. I set up Kerberos, and am getting a ticket. I have successfully joined the domain. # net ads join -U administrator Enter administrator's password: Using short domain name -- DACRIB Joined 'DUAL-BOOTER' to realm 'DaCrib.local' wbinfo -u

Hi there, As you know, $HOME is generally located at "/home/$username" by default. I would like to re-locate all users' $HOME directories to something like "/export/home/$username" without having a hassle/trouble. Initially, I've thought of just copying them to the new directory (under /export/home/xxx), but guessed it might trouble for the normal use (I'm pretty

Is there a document with instructions for this? I've had smartd warnings that a hard disk in my server is sick, so I am installing a new drive (in addition to the old). I was thinking of copying the old root partition with sudo cp -a -P /* /mnt/hd (after mounting the prospective new root partition). Then I'd have to modify the new /etc/fstab . Is that a sensible approach? -- Timothy