D
Dilligently seeking...
Hi All..
This is my 1st time at this so bear with me!
I'm sure i'm not the only person who's had this problem, but 1st the scenario!
Within the same forest i have an exchange server in one child domain, with
users in a separate child domain. If while working remotely (dial-up) the
users password expires, when they "fire up" the local outlook client (2003)
they are told that they must change their password, and are presented with a
dialogue box showing their username, domain, and exchange server name (which
is in a different domain). Trying to change the password in this dialogue
box is unsuccessful.
Whilst still dialled in to this same connection, pressing Ctrl+Alt+Delete,
gives you an option to change your password, only to be told that the
"...domain could not be found...". In the end you're left with a remote user
who cannot access email (and we know how much of a pain this is!).
So, obviously, my question is... how is this scenario resolved? It's no
good setting passwords not to expire, due to the huge security risk!
Obviously going to the server and changing the domain password does not work,
as the domain SAM needs to sync with the users local SAM(dial-up
authentication is in no way related to domain authentication, and signing on
having ticked the "Use dial-up networking" also draws a blank, even though
from a cmd prompt i can resolve my domain name and servers!!! - It would seem
that the user would need to physically connect to the LAN to resolve the
issue, but if they're hundreds of miles away????)
I'm sure there's an solution... but i've not yet located it... have any of
you?
This is my 1st time at this so bear with me!
I'm sure i'm not the only person who's had this problem, but 1st the scenario!
Within the same forest i have an exchange server in one child domain, with
users in a separate child domain. If while working remotely (dial-up) the
users password expires, when they "fire up" the local outlook client (2003)
they are told that they must change their password, and are presented with a
dialogue box showing their username, domain, and exchange server name (which
is in a different domain). Trying to change the password in this dialogue
box is unsuccessful.
Whilst still dialled in to this same connection, pressing Ctrl+Alt+Delete,
gives you an option to change your password, only to be told that the
"...domain could not be found...". In the end you're left with a remote user
who cannot access email (and we know how much of a pain this is!).
So, obviously, my question is... how is this scenario resolved? It's no
good setting passwords not to expire, due to the huge security risk!
Obviously going to the server and changing the domain password does not work,
as the domain SAM needs to sync with the users local SAM(dial-up
authentication is in no way related to domain authentication, and signing on
having ticked the "Use dial-up networking" also draws a blank, even though
from a cmd prompt i can resolve my domain name and servers!!! - It would seem
that the user would need to physically connect to the LAN to resolve the
issue, but if they're hundreds of miles away????)
I'm sure there's an solution... but i've not yet located it... have any of
you?