Hi!
I have a pdc with samba4(resara) and ubuntu printserver (samba3) separately.What are the commands and configurations i should do to join samba3 to samba4. I would like to make the printer available to the samba4 pdc clients by doing that. Plz help me out asap!

net rpc join?

Ok! thanks for the reply!
This is what i have done so far apart from resara domaincontroller...
1.installed ubuntu print server
2. apt-get install samba smb-client
3. edited smb.conf (changes below)
a. workgroup name= domain name
b. security = domain
c. password server = domain name
4. made dns changes to resolve my domain to resolve mydomain name from printserver
5. sudo net rpc join -S mydomain -UAdministrator%pass

i get error "get_schannel_session_key: could not fetch trust account password for domain 'abc'
net_rpc_join_ok: failed to get schannel session key from server abc.xyz.com for domain abc. Error was NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Unable to join domain abc."

Do i have to do provision of samba after installing ? Do i have to change anything else in smb.conf?

Have you tried kinit first (obviously you have to change your krb5.conf).

Also, as samba4 is supposed to be a fully blown AD Server- maybe security=ads and net ads join might work.

i have been able to join after changing workgroup name = abc instead of fqdn(abc.xyz.com) in samba3 smb.conf.
But the shared printer under samba3 is not showing under the samba 4 domain from windows client. Still I could access the printer by directly specifying the printer server IP. What could be wrong ?

It shows netbios problem somewhere. What are the results of net view and nbtstat from your Windows computers?

Thanks for your replies!I really appreciate that!
It might be a netbios problem! I haven't got a chance to post answer for nbstat and netview as i already started implementing ads join as you suggested. But, i haven't enabled wins support in samba 3 at all. I thought as the printer is accessible directly when i type samba3 ip; wins support is not necessary in samba 3. Am i right ?

No, wins support is not necessary- if you only want to type the samba3 server's ip address. It should work without any problem. What error are you getting?

Sorry ! Hope you misunderstood.
My samaba 3 printserver address - 192.168.1.50
domain samba4 - 192.168.1.3
What I was trying to say was, i could access the shared printer in samba3 from a windows pc by directly specifying the Ip 192.168.1.50. But it's not showing as a shared printer under the domain 192.168.1.3. I expect the printer to be listed under the domain as i joined samba 3 to domain with "net rpc join".
By the way, all i want to do is automate printer installation and mapping to all the domain users with cups when they login to domain. Do you think its possible ? Or is there any other simple way ?

So, you do need a wins server somewhere then. These are the things to check- is the computer browser service running on the PDC? What does nbtstat and net view return - by name and by IP address for your samba server? What does net dns register return?

Hi!
Thanks for your replies so far! I have managed to add printserver to samba 4 and been able to push drivers when pointed at the shared printers. But the printer being added with linuk .ppd drivers doesn't offer all the features as same as the printer added with windows driver. For instance duplex printing is not available. So is there any guides to push windows printer driver installation from samba3 ?

Very old (and untried) documentation:
http://www.enterprisenetworkingplane...-with-CUPS.htm

Ok! That was the second main document i used along with http://www.ossramblings.com/samba_push_windows_drivers to push linux drivers. But since it is pushing postscript drivers(ppd) file which doesn't offer all the features of a windows driver i should switch to another solution.
What difference would use client driver = yes or no make ? i'm using yes at the moment...

I guess i should do something with .inf files along with wpkg but haven't got clear idea so far.

Ok. I have used the change driver method to upload windows driver.
Finally got everything to work as intended