You can't map a drive. You would expect the XP machine to challenge if it
doesn't like the credentials initially passed to it. However, this is not
the case. You immediately get Access Denied.
"Roger Abell [MVP]" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> I am guessing that if they map a drive, not browse to it, but
> manually map it and are careful to supply alternate credentials
> in form <sharing-out-XP>\accountname then they will succeed.
> Since accountname would be the same as what they are at the
> time logged in with on the W2k, this is saying that the XP is not
> accepting the credentials as it is seeing them as something like
> <logged-in-W2k>\accountname
>
>
> "jrc" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > There are three 2000 machines that are not in the domain. These are the
> > machines I'm having the problem with. The users of these machines log
> into
> > the machines locally, but have the same username/password in the domain
so
> > they can access shares on the servers (eventually these machines will
join
> > the domain also, but not for a few more months).
> >
> > These users have no problems accessing anything on the network, but for
> some
> > reason they cannot access the printer share or a shared folder on the XP
> > machine in question. I have these users setup on the XP machine as
local
> > admins with the same username/password they use on their own machines
and
> on
> > the domain. But, the XP machine will not allow them to connect to it.
> >
> > The printer permissions are set to allow access to everyone, domain
users,
> > domain admins.
> >
> >
> >
> >
> > "Roger Abell [MVP]" <(E-Mail Removed)> wrote in message
> > news:#(E-Mail Removed)...
> > > Have you examined the permissions on the printer object ?
> > >
> > > Not sure what you mean by
> > > > 2000 Pro machines that are not part of the domain
> > > > get "Access Denied" when trying to connect to shared
> > > > printer on the XP machine, even though the users logging
> > > > on to these machines are listed in AD.
> > > as domain accounts cannot log into machine that is not
> > > a member of the domain.
> > >
> > > For account combinations that are not working, try first
> > > mapping a share that is hosted on the machine that has
> > > the printer, then try the printer with the share mapped.
> > > This will establish credentials first, then if printer works
> > > the printer object permissions are fine, but the initial
> > > authentication is the issue, whereas if it fails it is the
> > > printer permissions.
> > >
> > >
> > > "JRC" <(E-Mail Removed)> wrote in message
> > > news:012d01c3dd42$6d855320$(E-Mail Removed)...
> > > > Have an XP Pro machine that is part of a domain. Local
> > > > printer is shared.
> > > >
> > > > Domain users can connect to shared printer without
> > > > problem.
> > > >
> > > > 2000 Pro machines that are not part of the domain
> > > > get "Access Denied" when trying to connect to shared
> > > > printer on the XP machine, even though the users logging
> > > > on to these machines are listed in AD.
> > > >
> > > > Non-Domain users that are trying to connect to shared
> > > > printer are local administrative users on XP Pro machine
> > > > and have same username/password on XP machine with shared
> > > > printer and in AD.
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
Similar Threads
