Let's face it, samba is nice, but it's like fitting a square peg in a nice round hole. There are bound to be gaps. Explicit enumeration in a mixed environment is always a good thing, especially when it comes to authentication.
On Tue, Oct 13, 2009 at 11:20 AM, Joseph L. Casale < [email protected]> wrote: > Sh!t, > You may have been right J > I think the error was misleading, I checked the logs for errors specific to > this server and surprise, it was still trying to auth against AD even though > Samba is set up to auth to AD first then local unix accounts. > > Whatever the reason for it working as expected at the cli during an > interactive session and not through the scheduled task is a mystery, but I > added the ServerName\ to the username and rescheduled it to now and it > worked… > > > > Thanks Jonathan! > jlc > > > > *From:* Jonathan Link [mailto:[email protected]] > *Sent:* Tuesday, October 13, 2009 8:28 AM > *To:* NT System Admin Issues > *Subject:* Re: SQL Agent Job issue > > > > Use domain\user for the username? > > On Tue, Oct 13, 2009 at 10:14 AM, Joseph L. Casale < > [email protected]> wrote: > > I have a job defined with several steps, one is a batch file that maps a > drive on a Samba server. To setup the IPC session so the UNC exists, I start > the script with: > > > > rem Setup IPC$ > > net use \\Server /USER:user_name password > > > > But I get an error in the log: > > “A specified logon session does not exist. It may already have been > terminated.” > > > > Any ideas, obviously this works at the cli, just not when the job is run as > scheduled. > > > > Thanks! > jlc > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
