HodgeHi

I appreciate the help.

Unfortunately i don't have a credit card to donate :-(

OK, so i am at the point where i need to install and configure PyKota onto my Ubuntu Linux box. So where do i start? I have looked on the PyKota website and it says i need to pay to get the package. But there is a download on the subversion repository. What do i need to do to install the PyKota software. The steps in the install guide says to use dpkg -i but i don't know what the filename is? I thought this was going to be a little easier than this but it is certainly a job for someone with a little more knowledge of how Linux works and not really for the adventurous types as they would perhaps give up and go home

I may hold out for a little as i will be re-building my domains over the 6 week period so its all fresh and new again. Thanks for the help. It didn't make a difference with my print queues any way as i was still asked to authorise when i had an administrator ticket. Buts thats another thread :-)

Try again. Here's what i have:

@Geoff thats what i thought. Heres what i have in mine:

I can't find my Everyone group in Active directory users and computers? I have done a search and it doesn't show. But it is in the list of groups for print security so it must be somewhere. Where does it reside usually?

My Setup is like this at the moment: AD is configured as the PDC. This holds the kerberos realm. OD is connected to the AD and is part of the kerberised realm hosted by the AD. It is used to host the home profiles and also manage the OS X users. Linux is also connected to the AD and uses the AD Kerberos realm. This allows users from the AD to print to the queues without authentication. The AD users print to the print queue that is connected to the Ubuntu Server OD users print to the queue on the ubuntu server.

Yes. They are bound to the AD as well. My AD users are logging in fine onto the client i have set up. The OD server is also set up and configured like the AD-OD integration paper. I have just found this though What would i need to change to get this to work in my domain if my realm was CRONEHILLS.SANDWELL.SCH.UK Would it be similar to the Cups.conf file in the guide? I am slowly looking to make things simpler again. If i can edit this config file to suit then it may just get things going for me the way i would like them to be. Hope someone can save my day. PS. We need a superhero emoticon

OK. I will change the command. Anyone else know why my OS X are requesting authentication when they really shouldn't need to? Thanks.

I'm only trying to get a fully integrated system working between Windows and OS X. I have set up a Print Queue on the Ad to print to the Linux print server and it prints fine with no authentication needed. I have also set up a print queue on the OS X side and printed from there but it still asks for authentication. It should already have been pre-authenticated as it should be running kerberos authentication from the AD but seems to still require a user to type in their name and password in OS X. Here is how i set up my print queue on os x:

This is where i get lost. You see i have been following Ric_ guide on the installation. He suggests extracting the cups drivers into /usr/share/cups/drivers and then chown -R admin:admin /etc/samba/drivers. If what you say is the case then i can copy or even move the file to the samba location. I may just do that anyway. PS thanks for all the help guys. Please bear with me, i think i'm nearly there.

Thanks. I just run the command like so: mark@ubuntu:~$ locate /etc/samba/drivers mark@ubuntu:~$ sudo ls /etc/samba dhcp.conf gdbcommands smb.conf smb.conf~ smbpasswd It returned me to the command prompt. I listed the directory and there wasn't anything there. Am i using it incorrectly? I presume i am.

I don't know what files should be there as i have never done this before. I assumed that the drivers folder would be there. Can i point filename to the folder/directory name instead?

Ok. I tried the group an duser numbers and it accepted the command but it returned: mark@ubuntu:~$ sudo chown -R 10000:10017 /etc/samba/drivers/ [sudo] password for mark: chown: cannot access `/etc/samba/drivers/': No such file or directory What is supposed to be in the /samba/drivers folder as mine is missing? Have i forgot to install a package when installing SAMBA?

Would this be their GUIDS?

This also comes back with invalid group. chown -R administrator:administrator /etc/samba/drivers/ chown: `administrator:administrator': invalid group

Well i would of thought so too but when i try to chown -R adminsitrator:"domain admins" /etc/samba/drivers it comes back with a failure saying invalid group.

I run this and it returns: getent group | grep "domain admins" domain admins:x:10017:stopit,admin,kshilton,administrator

Yeah, i think it works OK: wbinfo -g | grep "domain admins" domain admins

and here is my smb.conf: [global] idmap gid = 10000-40000 obey pam restrictions = yes dns proxy = no netbios name = UBUNTU printing = cups invalid users = root idmap uid = 10000-20000 workgroup = CRONEHILLS os level = 20 printcap name = cups security = ads max log size = 1000 winbind separator = \ log file = /var/log/samba/log.%m load printers = yes socket options = TCP_NODELAY encrypt passwords = true public = yes realm = CRONEHILLS.SANDWELL.SCH.UK winbind use default domain = yes wins proxy = no server string = Cups Server winbind enum users = yes password server = * winbind gid = 10000-20000 winbind enum groups = yes syslog = 0 preferred master = no panic action = /usr/share/samba/panic-action %d [printers] printable = yes writable = no path = /var/spool/samba comment = All Printers public = yes create mode = 0700 printer admin = @"domain admins" [print$] comment = Printer Drivers path = /etc/samba/drivers browseable = yes read only = no guest ok = yes write list = administrator, @"domain admins"

Here is my nsswitch file: # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: winbind compat group: winbind compat shadow: compat hosts: files dns mdns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis

I replaced my nsswitch with the one you posted in that stickied thread I mentioned. If its in there which I'm sure you would have done then yes it will be in mine too :-)

I have since run a command found in the installation guide thread at the top of the *nix section: getent group | grep "Domain Admins" This did not return anything. Now I'm stumped as to why as the group definitely exists. I continued reading and found ICTNUT had the same issue as i have now where wbinfo -g could not find the domain admins group either. But it does not state what he did to resolve the issue.

OK i have moved on from the drivers thanks to Geoff. I have now got to the point that if i try to change the ownership on the /etc/samba/drivers to the administrator:"domain admins". i get an error returned which says chown: `administrator:domain admins': invalid group I don't know why. When i run the wbinfo -g the groups are returned as does the getent group command. I can obtain a ticket using kinit administrator and i can list them with klist. What could be the problem? Could it be something to do with the winbind error i have. When i run the testparm i get a winbind seperator error. The winbind error seems to do with the slash being seen as an escape character and thus removing the carriage return and placing the next line on the same line as the separator option.