I am running samba 3.0.28 on linux servers using ADS security, without any problem. However when I added a vista workstation to the mix, it simply cannot connect to my printers. I can connect to my data/ or disk shares again without any problem from both 64bit vista, and 32 bit vista. When I try to access my printers though I get "Windows cannot connect to the printer, Operation could not be completed (error 0x0000000d) I have looked at everything, tried numerous drivers, settings, and so on, but this error is not documented anywhere for this condition. Any ideas? Thanks boutapr@chevron.com
Hello, does the problem also occur, when you add a new printer and assign a driver to it? When you try to connect to the printer - do it as "normal" user, so the printer is not automaticly published in the AD. If yes, please try to set "default devmode = No" in the smb.conf and see, what happens. I simply can't reproduce it, though you're the second one who reports it. So - if possible - could you provide a network trace from the connection attempt, the ntprinters.tdb, ntdrivers.tdb and a list of the installed drivers? Let's see, what's so special in your installation ;-) Greets, Martin Boutan, Paul R. schrieb:> I am running samba 3.0.28 on linux servers using ADS security, without > any problem. > > > > However when I added a vista workstation to the mix, it simply cannot > connect to my printers. I can connect to my data/ or disk shares again > without any problem from both 64bit vista, and 32 bit vista. > > > > When I try to access my printers though I get "Windows cannot connect > to the printer, Operation could not be completed (error 0x0000000d) > > > > I have looked at everything, tried numerous drivers, settings, and so > on, but this error is not documented anywhere for this condition. Any > ideas? > > > > Thanks > > > > boutapr@chevron.com >
Hi Paul, what exactly appears to work? Disable the "default devmode", or the publish in the ADS? Previously we had an issue with registry entries. And there are some alignment issues. 0x0d error means "The data is invalid", so I suspect either a device mode alignment problem or even the devicemode data. But I may be wrong. It might also rely to, wether the printer is published in ADS or not. So, if it works at the moment and the issue occurs again later, it would be helpful, if you could tell, what exactly you have done (whoo, hope you understand my english). Bye, Martin Boutan, Paul R. schrieb:> Martin, > > That appears to have worked !!!! yahoooo.... I'll look it up and see > why... I will reserve total success for after I have tried every option, > deleted all the drivers, and tried it again... > > But on the up side, I've asked a few folks to try it and it has worked. > So THANK YOU !!! > > Paul Boutan >[...]> > -----Original Message----- > From: Martin Zielinski [mailto:mz@seh.de] > Sent: Tuesday, April 15, 2008 10:30 AM > To: Boutan, Paul R. > Cc: samba@samba.org > Subject: Re: [Samba] Vista problem, with ADS samba