Re: Log in as user before the account in functional

Well it all sounds confusing
-- Again, I'm probably doing a bad job of explaining it. Hard to be concise
& descriptive simultaneously without boring / losing the reader in an
abundance of detail...

it does seem like everything is working
-- Yes! It absolutely is working fine now & I apologize if I didn't make
that clear in my original posting.

You're just asking to get a reason why it works like that?
-- YES! That is EXACTLY what I am asking!!!!!!!

Have you asked Konica?
-- Konica has never heard of this 'trick'. As a matter of fact, they are
now going to make a call to several other clients who are experiencing the
same problem I had and ask them to do the same thing (log in to a PC as the
user account that was created specifically for the copier / scanner) in hopes
that this is all that is required to get those folks up & running!

"AllenM" wrote:

Well it all sounds confusing but it does seem like everything is working.
You're just asking to get a reason why it works like that? Why it does that
I have no clue. Have you asked Konica?

"Lori" <Lori@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B644F0BD-CA82-49FA-9B04-4BE6868D03AB@xxxxxxxxxxxxxxxx
once you've logged onto a pc with the konica user account any other user
account thereafter from any other workstation works fine?
-- You have it backwards. Any EXISTING user account worked EXCEPT for the
newly created 'konica' AD user account. AFTER I logged onto a PC with the
'konica' user account then that worked too. It's as if logging onto a PC
with that new user account triggered some sort of validation /
authentication
within AD to prove it's an acceptable / legit user account.

"AllenM" wrote:

So to recap and get a better understanding. When you say "That's when I
remembered the trick of logging in to a PC as the new AD user (in this
case
'konica') before trying to use it."

So given that information once you've logged onto a pc with the konica
user
account any other user account thereafter from any other workstation
works
fine?



"Lori" <Lori@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6A1B9A48-E2ED-4E0B-9118-81500FE464E9@xxxxxxxxxxxxxxxx
1. Is this Konica connected to a desktop or to the server directly?
-- Neither. It is a device on the network configured with a TCPIP Port
then
added to the server (the same server running AD & the same server with
the
shared network folder).

2. Is it "shared".
-- Yes. And we could print TO it as a network printer even when we
couldn't
scan FROM it to a shared network folder.

3. Static Microsoft TCPIP port configured?
-- Yes.

4. Is it required to have a user account to access the scanner?
-- Yes.
If so can you also input other AD accounts?
-- Yes & that was done during the initial troubleshooting. When we
used a
different / old account we were able to scan to the network. That's
when
I
remembered the trick of logging in to a PC as the new AD user (in this
case
'konica') before trying to use it.


"AllenM" wrote:

A couple of questions.

1. Is this Konica connected to a desktop or to the server directly?
2. Is it "shared".
3. Static Microsoft TCPIP port configured?
4. Is it required to have a user account to access the scanner? If so
can
you also input other AD accounts?



"Lori" <Lori@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4E4B17FA-E030-46C6-A280-11DB9655C7F7@xxxxxxxxxxxxxxxx
AllenM & Phillip -

Thanks so much for taking time to post... but I must have / am doing
a
bad
job at explaining the situation.

"Now that the profile exists can you log in the old way and see if
it
works
"normally" now."
-- There was no "old way" to log in. The brand new AD User account
(konica
\ pw \ domain) settings were input into the scanning software. The
Konica
was set to save the scanned files to a network share. It kept
failing
UNTIL
I logged in to a PC (any 'ol PC would do) AS the new user 'konica'.
Then
all
the scanned files were dropped in to the shared network folder - no
problem.

Sidnote: This isn't isolated to Konica as I mentioned in my initla
post.
It
happened once before in a completely different scenario... and I
remember
that the solution (found online) was to log in to a PC (again, any
'ol
PC)
AS
the new user which would then allow that account to be used by the
application. And I KNOW the solution included the REASON for this.
But I
can't find my notes / remember the details...

"Phillip Windell" wrote:

I think you might want to call Konica and see what they think. It
is
actually the Konica and its embedded OS & software that are the
biggest
"unknown" here, and they would know it better than anyone. If it
has
some
odd way to handling authnetication that would be the root of the
problem.
It also may require a local user profile that matches the account
to
be
able
to function correctly. Now that the profile exists can you log in
the
old
way and see if it works "normally" now.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or
Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Lori" <Lori@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A2D1F8DC-3FB6-48BA-896F-18127BE6C0DA@xxxxxxxxxxxxxxxx
Permissions were set correctly on the folder to which the scanned
files
were
being sent.

And yes, I did successfully get them to save to the folder (as
per
my
line
"After that, everything transferred from the Konica to the
network
without
a
problem.") but only AFTER I logged in to a COMPUTER on the
network
AS
the
user 'konica'.

My question is: What is the 'magic' behind logging in to a
computer
AS
the
new user before it can be used as valid credentials for another
application?

"AllenM" wrote:

Seems to be an NTFS permissions issue as to where it is your
trying
to
save
the scanned files to. You said you were "trying" to add the MF
printer
to
the network. does this imply you successfukly did so or not?


"Lori" <Lori@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C808FF0F-80A0-4D5B-9AB3-7AF94D34175B@xxxxxxxxxxxxxxxx
I was trying to add our Konica copier to the network in order
to
use
it
as
a
scanner & printer. The scanning portion of the software
required
a
network
account so I created an Act Dir User for it called 'konica'.
Even
though
all
the settings within the scanning were correct (login,
password,
domain,
IPs,
etc.) I couldn't get it to save scanned files to the network
UNTIL I
logged
in to a PC AS the user 'konica'. After that, everything
transferred
from
the
Konica to the network without a problem.

I had a similar scenario once before... but can't remember the
details.
The
short of it was that I had to log in to a PC as the user in
order
for
the
application to work with that user account.

I'm sure there's a explanation as to why this is - can someone
clue
me
in!?
Thanks so much for your time!















.