User's home share unaccessible after adding an Outlook profile

[Guest]

I have Windows XP SP2 machines in a SBS 2003 domain. Exchange has been set
up and everyone can access their e-mail with Outlook 2003 just fine. We just
had an employee leave, so I added a profile to one person's outlook to be
able to access that employee's e-mail.

After doing so, she was unable to access her network home drive! This is
the share set up automatically when her account was added to active
directory. I checked permissions on the folder and nothing had changed.

To test, I added permissions to her folder for the employee who had left and
then she was able to access her files on that share!

How is this possible? How can I fix it? I've already removed the extra
profile. I tried disconnecting all of her network shares and rebooting.

I was able to connect to it correctly using "Net use h: //server/users/name
/USER:domain/name" and did not have to specify a password, but as soon as she
logged off and on again, it was back to the way it was before.

Any ideas?

Thanks!
Kevin

 

[Lanwench [MVP - Exchange]]

In

I have Windows XP SP2 machines in a SBS 2003 domain. Exchange has
been set up and everyone can access their e-mail with Outlook 2003
just fine. We just had an employee leave, so I added a profile to
one person's outlook to be able to access that employee's e-mail.

So you a) granted this user "full mailbox access" to the old user's mailbox
in ADUC and then b) added the mailbox as a secondary one to the user's mail
profile? that's what I do......

After doing so, she was unable to access her network home drive!

Via a mapped drive, UNC path, ???

This is the share set up automatically when her account was added to
active directory. I checked permissions on the folder and nothing
had changed.

To test, I added permissions to her folder for the employee who had
left and then she was able to access her files on that share!

I don't know what you mean....

How is this possible? How can I fix it? I've already removed the
extra profile.

Outlook profile? Outlook has nothing to do with this - it would help if you
explained exactly what you did.....

I tried disconnecting all of her network shares and
rebooting.

I was able to connect to it correctly using "Net use h:
//server/users/name /USER:domain/name" and did not have to specify a
password, but as soon as she logged off and on again, it was back to
the way it was before.

Any ideas?

Are you using a login script? You should be....even a basic batch file.

net use * /del
net use h: /home /persistent:no
net use x: \\server\share /persistent:no
net use y: \\server\share /persistent:no

(etc)

 

[Steven L Umbach]

I tend to doubt it had anything to do with Outlook. It sounds as if the user
is authenticating as the wrong user. Next time she accesses the share go to
the server with the share and use Computer Management to look at shared
folders -sessions to see what user account is using that share from her
computer. Also have her try and access from another domain computer to see
what happens. If a user is authenticating as the wrong user then maybe the
user is using a mapped share with persistent alternate credentials or XP
stored credentials which the user can manage via Control Panel/user
accounts - their account and check manage network passwords. --- Steve

 

[Guest]

I don't understand how it could be anything to do with Outlook either, but
that seems to be the only change we've made to this machine. Anyway, I did
check the sessions in the server's computer management and it is
authenticating as the wrong user.

I logged on to another computer with Teri's username and password and am
able to access her network resources correctly.

I tried looking for the options you mentioned: persistent alternate
credentials or XP stored credentials, and finally found the little hyperlink
at the bottom of the dialog asking you to log in as an admin on that machine
that says "manage your passwords". When I clicked on that, there was an item
in that list with the name of our SBS server. Hitting the properties button
revealed that the wrong username was stored in there!

I removed that stored information, logged out and back in again and normal
connectivity has been restored!

Thank you very much for this information!

Kevin

 

[Lanwench [MVP - Exchange]]

In

I don't understand how it could be anything to do with Outlook
either, but that seems to be the only change we've made to this
machine. Anyway, I did check the sessions in the server's computer
management and it is authenticating as the wrong user.

I logged on to another computer with Teri's username and password and
am able to access her network resources correctly.

I tried looking for the options you mentioned: persistent alternate
credentials or XP stored credentials, and finally found the little
hyperlink at the bottom of the dialog asking you to log in as an
admin on that machine that says "manage your passwords". When I
clicked on that, there was an item in that list with the name of our
SBS server. Hitting the properties button revealed that the wrong
username was stored in there!

I removed that stored information, logged out and back in again and
normal connectivity has been restored!

Thank you very much for this information!

In the future, you might also try

net use * /del

in a command line to see if that resolves the issue.