Printer Access Denied after joining domain, shared files OK

[cwells 0]

I am migrating workstations from an old NT 4.0 domain to a new Server 2003 domain. An explicit two-way trust relationship exists between both domains. After joining a Windows 2000 workstation to the new domain, I receive an Event 534 security failure ("user has not been granted the requested logon type") upon attempting to access shared printers on either domain. Access is denied to the shared printers even with a administrative logon. I can still access shared files on both domains without problems, though. Permissions on the shared printers appear to be set appropriately. I was able to access printers on both domains before leaving the old domain and joining the new one; all the trouble started when I joined the workstation to the new domain. All workstations and servers are kept up-to-date on patches.

 

Suggestions and diagnostic recommendations would be greatly appreciated. I am particularly perplexed that I am able to access shared files on both domains but not the shared printers.

 

Regards,

 

Patrick

[sapiens74 0]

Does this only do this on one particualr workstation?

 

or all of them that join the new domain?

 

Secondly make sure the computer accounts have been added to the new domain, and also check the eefective permissions tab to see if those resources have been explicity denied for some reason

[cwells 0]

I haven't tried to duplicate the problem on other new domain members yet; this was the first workstation that I joined to the new domain. Attempting to duplicate the problem on another workstation is my next step (as soon as the roads thaw out, anyway).

 

The workstation account has been added to the new domain. I have been checking every permissions tab that I can dig up for possible issues, but have not come across anything suspicious looking yet.

 

Patrick

[duhmez 0]

Are the clients pulling from config.pol file or ntconfig.pol file?

 

If so this is an unsupported and broken was and will cause issues, duno if it will cause this issue, but it's something to check. (.pol files pulled from netlogon on nt clients is not supported in active directory environment, even in mixed mode.)