Have workstation with XP SP2 installed. When a non-admin users power's up
the machine from cold-start and attempts to login, the file share is not
accessible - getting "\\FileServ\Users\<username>\<folder> is not accessible.
You may not have permission to use this network resource. Access is denied.
Network path was not found."

Basically, person has permission on the \\FileServ\ server.

From the \\FileServ\Users\<username>\PCDesktop - there is a subfolder that
is used to populate the desktop icons for user. It's way we handle this for
agency and has no issue for over 200 users. I can login this person on
another workstation without issue, i.e., from Cold-Start the boot sequence is
proper and the desktop is populated from \\FileServ\...\PCDesktop.

But for this workstation, during the COLD-START cycle of power / this path is
not accessible during the startup process / not sure why. But AFTER the
login, if I Right Click and REFRESH my desktop - it's available than.

Again, getting the error message in earlier post [when recycle power].
ALSO, this only occurs for non-admin users. What should I look for with
this workstation - to see why it doesn't complete Cold+Boot login process
here / but on another identical workstation it does. Are there registry keys
I can check - is there a reinstall of network resource required etc... [I'm
not showing ANY network issues for Admin though - and if I Cold+Boot for
Admin, than logoff, login - not issue] - just when I Cold+Boot for
<non-admin> user on this machine it gives the message above.

Help - ASAP please

Any change I can get some help here!

"DavidS" wrote:

> Have workstation with XP SP2 installed. When a non-admin users power's up
> the machine from cold-start and attempts to login, the file share is not
> accessible - getting "\\FileServ\Users\<username>\<folder> is not accessible.
> You may not have permission to use this network resource. Access is denied.
> Network path was not found."
>
> Basically, person has permission on the \\FileServ\ server.
>
> From the \\FileServ\Users\<username>\PCDesktop - there is a subfolder that
> is used to populate the desktop icons for user. It's way we handle this for
> agency and has no issue for over 200 users. I can login this person on
> another workstation without issue, i.e., from Cold-Start the boot sequence is
> proper and the desktop is populated from \\FileServ\...\PCDesktop.
>
> But for this workstation, during the COLD-START cycle of power / this path is
> not accessible during the startup process / not sure why. But AFTER the
> login, if I Right Click and REFRESH my desktop - it's available than.
>
> Again, getting the error message in earlier post [when recycle power].
> ALSO, this only occurs for non-admin users. What should I look for with
> this workstation - to see why it doesn't complete Cold+Boot login process
> here / but on another identical workstation it does. Are there registry keys
> I can check - is there a reinstall of network resource required etc... [I'm
> not showing ANY network issues for Admin though - and if I Cold+Boot for
> Admin, than logoff, login - not issue] - just when I Cold+Boot for
> <non-admin> user on this machine it gives the message above.
>
> Help - ASAP please
>

On Tue, 22 Jul 2008 13:07:12 -0700, DavidS
<DavidS@discussions.microsoft.com> wrote:

> Any change I can get some help here!



Patience, please. This is a peer support newsgroup. We are all just
Windows XP users here, helping each other if and when we can. We are
not Microsoft employees (not even those of us with "Microsoft MVP"
behind our names; that's an honorary title for having provided
consistently helpful advice) except for an occasional employee who
posts here unofficially on his own time.

If you don't get an answer, it can be for a variety of reasons: you
may have asked your question poorly and nobody understood, nobody may
know the answer, the person who knows the answer may have missed your
question, and so on.

Or the person who knows the answer (not me, in this case) hasn't seen
your message yet.


> "DavidS" wrote:
>
> > Have workstation with XP SP2 installed. When a non-admin users power's up
> > the machine from cold-start and attempts to login, the file share is not
> > accessible - getting "\\FileServ\Users\<username>\<folder> is not accessible.
> > You may not have permission to use this network resource. Access is denied.
> > Network path was not found."
> >
> > Basically, person has permission on the \\FileServ\ server.
> >
> > From the \\FileServ\Users\<username>\PCDesktop - there is a subfolder that
> > is used to populate the desktop icons for user. It's way we handle this for
> > agency and has no issue for over 200 users. I can login this person on
> > another workstation without issue, i.e., from Cold-Start the boot sequence is
> > proper and the desktop is populated from \\FileServ\...\PCDesktop.
> >
> > But for this workstation, during the COLD-START cycle of power / this path is
> > not accessible during the startup process / not sure why. But AFTER the
> > login, if I Right Click and REFRESH my desktop - it's available than.
> >
> > Again, getting the error message in earlier post [when recycle power].
> > ALSO, this only occurs for non-admin users. What should I look for with
> > this workstation - to see why it doesn't complete Cold+Boot login process
> > here / but on another identical workstation it does. Are there registry keys
> > I can check - is there a reinstall of network resource required etc... [I'm
> > not showing ANY network issues for Admin though - and if I Cold+Boot for
> > Admin, than logoff, login - not issue] - just when I Cold+Boot for
> > <non-admin> user on this machine it gives the message above.
> >
> > Help - ASAP please
> >

--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup

Anything not clear in my request.

Anyone out there that can answer this?

"DavidS" wrote:

> Have workstation with XP SP2 installed. When a non-admin users power's up
> the machine from cold-start and attempts to login, the file share is not
> accessible - getting "\\FileServ\Users\<username>\<folder> is not accessible.
> You may not have permission to use this network resource. Access is denied.
> Network path was not found."
>
> Basically, person has permission on the \\FileServ\ server.
>
> From the \\FileServ\Users\<username>\PCDesktop - there is a subfolder that
> is used to populate the desktop icons for user. It's way we handle this for
> agency and has no issue for over 200 users. I can login this person on
> another workstation without issue, i.e., from Cold-Start the boot sequence is
> proper and the desktop is populated from \\FileServ\...\PCDesktop.
>
> But for this workstation, during the COLD-START cycle of power / this path is
> not accessible during the startup process / not sure why. But AFTER the
> login, if I Right Click and REFRESH my desktop - it's available than.
>
> Again, getting the error message in earlier post [when recycle power].
> ALSO, this only occurs for non-admin users. What should I look for with
> this workstation - to see why it doesn't complete Cold+Boot login process
> here / but on another identical workstation it does. Are there registry keys
> I can check - is there a reinstall of network resource required etc... [I'm
> not showing ANY network issues for Admin though - and if I Cold+Boot for
> Admin, than logoff, login - not issue] - just when I Cold+Boot for
> <non-admin> user on this machine it gives the message above.
>
> Help - ASAP please
>

Anything not clear in the initial request - and Any chance I can get some
assistance here.

"DavidS" wrote:

> Have workstation with XP SP2 installed. When a non-admin users power's up
> the machine from cold-start and attempts to login, the file share is not
> accessible - getting "\\FileServ\Users\<username>\<folder> is not accessible.
> You may not have permission to use this network resource. Access is denied.
> Network path was not found."
>
> Basically, person has permission on the \\FileServ\ server.
>
> From the \\FileServ\Users\<username>\PCDesktop - there is a subfolder that
> is used to populate the desktop icons for user. It's way we handle this for
> agency and has no issue for over 200 users. I can login this person on
> another workstation without issue, i.e., from Cold-Start the boot sequence is
> proper and the desktop is populated from \\FileServ\...\PCDesktop.
>
> But for this workstation, during the COLD-START cycle of power / this path is
> not accessible during the startup process / not sure why. But AFTER the
> login, if I Right Click and REFRESH my desktop - it's available than.
>
> Again, getting the error message in earlier post [when recycle power].
> ALSO, this only occurs for non-admin users. What should I look for with
> this workstation - to see why it doesn't complete Cold+Boot login process
> here / but on another identical workstation it does. Are there registry keys
> I can check - is there a reinstall of network resource required etc... [I'm
> not showing ANY network issues for Admin though - and if I Cold+Boot for
> Admin, than logoff, login - not issue] - just when I Cold+Boot for
> <non-admin> user on this machine it gives the message above.
>
> Help - ASAP please
>

On Jul 22, 9:07*pm, DavidS <Dav...@discussions.microsoft.com> wrote:
> Any change I can get some help here!
>
> <snip>>
> > Help - ASAP please-
>


if it's that importan and urgent and you are getting no answers yet,
then consider a win xp repair install.

Most big organisations just ghost from a perfect virgin machine
anyway. They don't worry about diagnosing these little issues if it
takes time.


.

Unreal!

Truly axx_inain.

Basically, yes it's important. Basically, it's configuration issue - I
didn't design XP - and need assistance reviewing registry setup.

I guestimate both persons who responded in this newsgroup are younger than
30 and although Windows "guro's" -

Please - I've "ghost" my machine for someone else's usage - this is not
issue. Maybe
some more meaningful responses might help me - but I guess that's not
possible either.

Send me more b.s. replies please!

"jameshanley39@yahoo.co.uk" wrote:

> On Jul 22, 9:07 pm, DavidS <Dav...@discussions.microsoft.com> wrote:
> > Any change I can get some help here!
> >
> > <snip>>
> > > Help - ASAP please-
> >
>
>
> if it's that importan and urgent and you are getting no answers yet,
> then consider a win xp repair install.
>
> Most big organisations just ghost from a perfect virgin machine
> anyway. They don't worry about diagnosing these little issues if it
> takes time.
>
>
> .
>
>

Also if it's such a LITTLE issue - than why can't someone as SMART as you
figure it out!

I'll go elsewhere - Linux is future for me

"DavidS" wrote:

> Unreal!
>
> Truly axx_inain.
>
> Basically, yes it's important. Basically, it's configuration issue - I
> didn't design XP - and need assistance reviewing registry setup.
>
> I guestimate both persons who responded in this newsgroup are younger than
> 30 and although Windows "guro's" -
>
> Please - I've "ghost" my machine for someone else's usage - this is not
> issue. Maybe
> some more meaningful responses might help me - but I guess that's not
> possible either.
>
> Send me more b.s. replies please!
>
> "jameshanley39@yahoo.co.uk" wrote:
>
> > On Jul 22, 9:07 pm, DavidS <Dav...@discussions.microsoft.com> wrote:
> > > Any change I can get some help here!
> > >
> > > <snip>>
> > > > Help - ASAP please-
> > >
> >
> >
> > if it's that importan and urgent and you are getting no answers yet,
> > then consider a win xp repair install.
> >
> > Most big organisations just ghost from a perfect virgin machine
> > anyway. They don't worry about diagnosing these little issues if it
> > takes time.
> >
> >
> > .
> >
> >