How to change Windows server 2003 Domain User password?

Hello,
I am using Windows Xp pro SP2 as a client to connect to Windows Server 2003
domain. i also have windows 98 machines as clients in same domain.
While i have setup domain on win 98 machines so every time while logging
they ask for domain id and pass, i haven't done so on xp machines because
they were taking too long to log on and being used by multiple users it
created too many users.
Now what i have done is to put all the computers on same work group (so as
to communicate in lan), and winxp machines have shortcut to server's hard
disk, so when ever i try to access files on the domain server it asks for the
password then and it gives me access. Do you have a better way to do this?
ALSO i have security policy which asks the domain users to change password
every 15 days. while win 98 users get a dialog that password is expired and
gives a option to change it, Winxp users don't get any notification and no
option to change password. how do i do this in winxp and change password?
Please Help.

i haven't done so on xp machines because
> they were taking too long to log on and being used by multiple users it
> created too many users.


XP clients in an AD domain rely on DNS to find the domain. Sounds like you
don't have DNS set up correctly.


> Now what i have done is to put all the computers on same work group (so as
> to communicate in lan), and winxp machines have shortcut to server's hard
> disk, so when ever i try to access files on the domain server it asks for
> the
> password then and it gives me access. Do you have a better way to do this?

Sounds like you are jumping through extra unnecessary hoops because DNS is
not set up correctly.

Winxp users don't get any notification and no
> option to change password. how do i do this in winxp and change password?
> Please Help.


This all comes back to your DNS being mis configured. Basic AD DNS is set up
a DNS server for the AD domain, point this DNS server to itself for DNS in
the properties of TCP/IP. Point all AD clients to this DNS server ONLY.
(servers are AD clients also) For Internet access, configure your AD DNS
server to forward requests and list your ISP's DNS server(s) as the
forwarder. This is the only place on an AD domain your ISP's DNS server
should be listed. Just guessing, I think you have your ISP's DNS server
listed on your AD clients as the preferred DNS server. This will cause long
log in times and group policy will not work. (Sound familiar?)

See:
http://support.microsoft.com/kb/814591/en-us
http://support.microsoft.com/kb/825036/en-us
http://support.microsoft.com/kb/323380/en-us

hth
DDS
"Raghav" <(E-Mail Removed)> wrote in message
news:994A879A-4FED-43A8-AB9E-(E-Mail Removed)...
> Hello,
> I am using Windows Xp pro SP2 as a client to connect to Windows Server
> 2003
> domain. i also have windows 98 machines as clients in same domain.
> While i have setup domain on win 98 machines so every time while logging
> they ask for domain id and pass, i haven't done so on xp machines because
> they were taking too long to log on and being used by multiple users it
> created too many users.
> Now what i have done is to put all the computers on same work group (so as
> to communicate in lan), and winxp machines have shortcut to server's hard
> disk, so when ever i try to access files on the domain server it asks for
> the
> password then and it gives me access. Do you have a better way to do this?
> ALSO i have security policy which asks the domain users to change password
> every 15 days. while win 98 users get a dialog that password is expired
> and
> gives a option to change it, Winxp users don't get any notification and no
> option to change password. how do i do this in winxp and change password?
> Please Help.

Dear Danny
Thanks for the reply!

1) Yes i think i do not have DNS setup on server, but i did notice DNS
server as one of the roles of the server in "Manage your Server" menu.
2) I would be glad to shift to Active Directory and Domain based envirment
if i have no logon issues and multiple desktops on commom computer issue.
3) Yes i have ISP's dns configured as preferred, how do i know what is my
servers DNS and about ISP DNS forwading my server, how do i do that?

Please read on for general information i think about the problem

I have a active directory setup for about 25 users, i access my files (ERP)
from a server with active directory. All users have their own machines (with
XP or win98). They have a Servers hard disk mapped so as to run the ERP.

I have few computers which are at common place to do common activities like
scanning, Internet (didnt want to give everyone access to net). Here the
problem is if i setup a domain client on this pc, i wouldnt get the same
desktop with common files or shortcuts on desktop. Also there was a log on
speed problem (which i will try and check with DNS setup).
What do you suggest for Common PC's, and for PC's with XP but not with
Common users.?

As for long logon times, i am using a IBM X226 8648 iAS server with Xeon 3.0
ghz processor and 1 gb ram. Is that causing slow logon times? for my client
pc's i have ISP's DNS put in as preferred. How do i know my Servers DNS? If i
do that how will the clients pc's access the net?

Please help..

"Danny Sanders" wrote:

> i haven't done so on xp machines because
> > they were taking too long to log on and being used by multiple users it
> > created too many users.
>
>
> XP clients in an AD domain rely on DNS to find the domain. Sounds like you
> don't have DNS set up correctly.
>
>
> > Now what i have done is to put all the computers on same work group (so as
> > to communicate in lan), and winxp machines have shortcut to server's hard
> > disk, so when ever i try to access files on the domain server it asks for
> > the
> > password then and it gives me access. Do you have a better way to do this?
>
> Sounds like you are jumping through extra unnecessary hoops because DNS is
> not set up correctly.
>
> Winxp users don't get any notification and no
> > option to change password. how do i do this in winxp and change password?
> > Please Help.
>
>
> This all comes back to your DNS being mis configured. Basic AD DNS is set up
> a DNS server for the AD domain, point this DNS server to itself for DNS in
> the properties of TCP/IP. Point all AD clients to this DNS server ONLY.
> (servers are AD clients also) For Internet access, configure your AD DNS
> server to forward requests and list your ISP's DNS server(s) as the
> forwarder. This is the only place on an AD domain your ISP's DNS server
> should be listed. Just guessing, I think you have your ISP's DNS server
> listed on your AD clients as the preferred DNS server. This will cause long
> log in times and group policy will not work. (Sound familiar?)
>
> See:
> http://support.microsoft.com/kb/814591/en-us
> http://support.microsoft.com/kb/825036/en-us
> http://support.microsoft.com/kb/323380/en-us
>
> hth
> DDS
> "Raghav" <(E-Mail Removed)> wrote in message
> news:994A879A-4FED-43A8-AB9E-(E-Mail Removed)...
> > Hello,
> > I am using Windows Xp pro SP2 as a client to connect to Windows Server
> > 2003
> > domain. i also have windows 98 machines as clients in same domain.
> > While i have setup domain on win 98 machines so every time while logging
> > they ask for domain id and pass, i haven't done so on xp machines because
> > they were taking too long to log on and being used by multiple users it
> > created too many users.
> > Now what i have done is to put all the computers on same work group (so as
> > to communicate in lan), and winxp machines have shortcut to server's hard
> > disk, so when ever i try to access files on the domain server it asks for
> > the
> > password then and it gives me access. Do you have a better way to do this?
> > ALSO i have security policy which asks the domain users to change password
> > every 15 days. while win 98 users get a dialog that password is expired
> > and
> > gives a option to change it, Winxp users don't get any notification and no
> > option to change password. how do i do this in winxp and change password?
> > Please Help.
>
>
>

> 2) I would be glad to shift to Active Directory and Domain based envirment
> if i have no logon issues and multiple desktops on commom computer issue.

You have already shifted to AD, you just haven't set up DNS properly so AD
works.

> 3) Yes i have ISP's dns configured as preferred, how do i know what is my
> servers DNS and about ISP DNS forwading my server, how do i do that?

This is the root of your problem. AD clients MUST find the SRV records for
your AD domain. You have them looking through your ISP's *Public* DNS server
for your *Private* SRV records. Most ISP's will not nor do you want you want
the SRV records for your AD domain located on a Public DNS server.





> I have few computers which are at common place to do common activities
> like
> scanning, Internet (didnt want to give everyone access to net). Here the
> problem is if i setup a domain client on this pc, i wouldnt get the same
> desktop with common files or shortcuts on desktop. Also there was a log on
> speed problem (which i will try and check with DNS setup).
> What do you suggest for Common PC's, and for PC's with XP but not with
> Common users.?

Not following you here.

> As for long logon times, i am using a IBM X226 8648 iAS server with Xeon
> 3.0
> ghz processor and 1 gb ram. Is that causing slow logon times? for my
> client
> pc's i have ISP's DNS put in as preferred. How do i know my Servers DNS?
> If i
> do that how will the clients pc's access the net?


It's not the speed of the computer, it's the fact that it *can't* *find* the
SRV records for your domain.
You need to provide a place on your AD domain to hold those SRV records,
that means setting up a DNS server to hold those SRV records. Then you need
to tell your AD clients *where* those SRV records are, by pointing them to
the DNS server set up for the AD domain.

You want to set up a DNS server for your AD domain to hold the private SRV
records for your domain.

On your servers look at the DNS console for a forward lookup zone with the
same name as your AD domain. This is a DNS server for your AD domain.Make
sure that in the properties of TCP/IP, this server lists itself as the DNS
server. See the "Configure DNS" section here for this:
http://support.microsoft.com/kb/814591/en-us


Point your AD clients to this DNS server in the properties of TCP/IP.
See:
http://support.microsoft.com/kb/825036/en-us


If i
> do that how will the clients pc's access the net?

For Internet access set up forwarders on your AD DNS server or use root
hints.
See:
http://support.microsoft.com/kb/323380/en-us

See the section on how to remove the Root DNS zone and how to configure
forwarders in the above article.

If you read through these three articles, they detail *everything* you need
to do in a step by step manner what you need to get DNS up and working. You
MUST get DNS up and working before you can even begin to work on *anything*
else in AD. AD relies on DNS so much it would be a waste of time trying to
troubleshoot *anything* in an AD domain until you get DNS working right.

Get your DNS working right and many of your problems will go away.


hth
DDS

"Raghav" <(E-Mail Removed)> wrote in message
news:FCB9AFCF-AE4B-4FA8-AD86-(E-Mail Removed)...
> Dear Danny
> Thanks for the reply!
>
> 1) Yes i think i do not have DNS setup on server, but i did notice DNS
> server as one of the roles of the server in "Manage your Server" menu.
> 2) I would be glad to shift to Active Directory and Domain based envirment
> if i have no logon issues and multiple desktops on commom computer issue.
> 3) Yes i have ISP's dns configured as preferred, how do i know what is my
> servers DNS and about ISP DNS forwading my server, how do i do that?
>
> Please read on for general information i think about the problem
>
> I have a active directory setup for about 25 users, i access my files
> (ERP)
> from a server with active directory. All users have their own machines
> (with
> XP or win98). They have a Servers hard disk mapped so as to run the ERP.
>
> I have few computers which are at common place to do common activities
> like
> scanning, Internet (didnt want to give everyone access to net). Here the
> problem is if i setup a domain client on this pc, i wouldnt get the same
> desktop with common files or shortcuts on desktop. Also there was a log on
> speed problem (which i will try and check with DNS setup).
> What do you suggest for Common PC's, and for PC's with XP but not with
> Common users.?
>
> As for long logon times, i am using a IBM X226 8648 iAS server with Xeon
> 3.0
> ghz processor and 1 gb ram. Is that causing slow logon times? for my
> client
> pc's i have ISP's DNS put in as preferred. How do i know my Servers DNS?
> If i
> do that how will the clients pc's access the net?
>
> Please help..
>
> "Danny Sanders" wrote:
>
>> i haven't done so on xp machines because
>> > they were taking too long to log on and being used by multiple users it
>> > created too many users.
>>
>>
>> XP clients in an AD domain rely on DNS to find the domain. Sounds like
>> you
>> don't have DNS set up correctly.
>>
>>
>> > Now what i have done is to put all the computers on same work group (so
>> > as
>> > to communicate in lan), and winxp machines have shortcut to server's
>> > hard
>> > disk, so when ever i try to access files on the domain server it asks
>> > for
>> > the
>> > password then and it gives me access. Do you have a better way to do
>> > this?
>>
>> Sounds like you are jumping through extra unnecessary hoops because DNS
>> is
>> not set up correctly.
>>
>> Winxp users don't get any notification and no
>> > option to change password. how do i do this in winxp and change
>> > password?
>> > Please Help.
>>
>>
>> This all comes back to your DNS being mis configured. Basic AD DNS is set
>> up
>> a DNS server for the AD domain, point this DNS server to itself for DNS
>> in
>> the properties of TCP/IP. Point all AD clients to this DNS server ONLY.
>> (servers are AD clients also) For Internet access, configure your AD DNS
>> server to forward requests and list your ISP's DNS server(s) as the
>> forwarder. This is the only place on an AD domain your ISP's DNS server
>> should be listed. Just guessing, I think you have your ISP's DNS server
>> listed on your AD clients as the preferred DNS server. This will cause
>> long
>> log in times and group policy will not work. (Sound familiar?)
>>
>> See:
>> http://support.microsoft.com/kb/814591/en-us
>> http://support.microsoft.com/kb/825036/en-us
>> http://support.microsoft.com/kb/323380/en-us
>>
>> hth
>> DDS
>> "Raghav" <(E-Mail Removed)> wrote in message
>> news:994A879A-4FED-43A8-AB9E-(E-Mail Removed)...
>> > Hello,
>> > I am using Windows Xp pro SP2 as a client to connect to Windows Server
>> > 2003
>> > domain. i also have windows 98 machines as clients in same domain.
>> > While i have setup domain on win 98 machines so every time while
>> > logging
>> > they ask for domain id and pass, i haven't done so on xp machines
>> > because
>> > they were taking too long to log on and being used by multiple users it
>> > created too many users.
>> > Now what i have done is to put all the computers on same work group (so
>> > as
>> > to communicate in lan), and winxp machines have shortcut to server's
>> > hard
>> > disk, so when ever i try to access files on the domain server it asks
>> > for
>> > the
>> > password then and it gives me access. Do you have a better way to do
>> > this?
>> > ALSO i have security policy which asks the domain users to change
>> > password
>> > every 15 days. while win 98 users get a dialog that password is expired
>> > and
>> > gives a option to change it, Winxp users don't get any notification and
>> > no
>> > option to change password. how do i do this in winxp and change
>> > password?
>> > Please Help.
>>
>>
>>

Raghav <(E-Mail Removed)> wrote:
> Hello,
> I am using Windows Xp pro SP2 as a client to connect to Windows
> Server 2003 domain. i also have windows 98 machines as clients in
> same domain.
> While i have setup domain on win 98 machines so every time while
> logging they ask for domain id and pass, i haven't done so on xp
> machines because they were taking too long to log on and being used
> by multiple users it created too many users.
> Now what i have done is to put all the computers on same work group
> (so as to communicate in lan), and winxp machines have shortcut to
> server's hard disk, so when ever i try to access files on the domain
> server it asks for the password then and it gives me access. Do you
> have a better way to do this? ALSO i have security policy which asks
> the domain users to change password every 15 days. while win 98 users
> get a dialog that password is expired and gives a option to change
> it, Winxp users don't get any notification and no option to change
> password. how do i do this in winxp and change password? Please Help.

Hi -

I replied to your identical posts in the WinXP groups. Please don't
multipost - if you need to post to multiple groups, it's best to crosspost
instead, by posting a single message to a handful of relevant groups
(separate the NG names with commas) so that everyone can follow the thread.
Thanks :-)

See http://www.blakjak.demon.co.uk/mul_crss.htm

Danny,
I know what to do now, just have few queries, can we instant message? i
would be glad. i am available on yahoo: rkalantri on MSN:
(E-Mail Removed) on Gtalk: rkalantri now. Can i contact you?

"Danny Sanders" wrote:

> > 2) I would be glad to shift to Active Directory and Domain based envirment
> > if i have no logon issues and multiple desktops on commom computer issue.
>
> You have already shifted to AD, you just haven't set up DNS properly so AD
> works.
>
> > 3) Yes i have ISP's dns configured as preferred, how do i know what is my
> > servers DNS and about ISP DNS forwading my server, how do i do that?
>
> This is the root of your problem. AD clients MUST find the SRV records for
> your AD domain. You have them looking through your ISP's *Public* DNS server
> for your *Private* SRV records. Most ISP's will not nor do you want you want
> the SRV records for your AD domain located on a Public DNS server.
>
>
>
>
>
> > I have few computers which are at common place to do common activities
> > like
> > scanning, Internet (didnt want to give everyone access to net). Here the
> > problem is if i setup a domain client on this pc, i wouldnt get the same
> > desktop with common files or shortcuts on desktop. Also there was a log on
> > speed problem (which i will try and check with DNS setup).
> > What do you suggest for Common PC's, and for PC's with XP but not with
> > Common users.?
>
> Not following you here.
>
> > As for long logon times, i am using a IBM X226 8648 iAS server with Xeon
> > 3.0
> > ghz processor and 1 gb ram. Is that causing slow logon times? for my
> > client
> > pc's i have ISP's DNS put in as preferred. How do i know my Servers DNS?
> > If i
> > do that how will the clients pc's access the net?
>
>
> It's not the speed of the computer, it's the fact that it *can't* *find* the
> SRV records for your domain.
> You need to provide a place on your AD domain to hold those SRV records,
> that means setting up a DNS server to hold those SRV records. Then you need
> to tell your AD clients *where* those SRV records are, by pointing them to
> the DNS server set up for the AD domain.
>
> You want to set up a DNS server for your AD domain to hold the private SRV
> records for your domain.
>
> On your servers look at the DNS console for a forward lookup zone with the
> same name as your AD domain. This is a DNS server for your AD domain.Make
> sure that in the properties of TCP/IP, this server lists itself as the DNS
> server. See the "Configure DNS" section here for this:
> http://support.microsoft.com/kb/814591/en-us
>
>
> Point your AD clients to this DNS server in the properties of TCP/IP.
> See:
> http://support.microsoft.com/kb/825036/en-us
>
>
> If i
>

> I know what to do now, just have few queries, can we instant message? i
> would be glad. i am available on yahoo: rkalantri on MSN:


We don't allow IM on our network.



DDS
"Raghav" <(E-Mail Removed)> wrote in message
news:67499569-FB17-4485-929B-(E-Mail Removed)...
> Danny,
> I know what to do now, just have few queries, can we instant message? i
> would be glad. i am available on yahoo: rkalantri on MSN:
> (E-Mail Removed) on Gtalk: rkalantri now. Can i contact you?
>
> "Danny Sanders" wrote:
>
>> > 2) I would be glad to shift to Active Directory and Domain based
>> > envirment
>> > if i have no logon issues and multiple desktops on commom computer
>> > issue.
>>
>> You have already shifted to AD, you just haven't set up DNS properly so
>> AD
>> works.
>>
>> > 3) Yes i have ISP's dns configured as preferred, how do i know what is
>> > my
>> > servers DNS and about ISP DNS forwading my server, how do i do that?
>>
>> This is the root of your problem. AD clients MUST find the SRV records
>> for
>> your AD domain. You have them looking through your ISP's *Public* DNS
>> server
>> for your *Private* SRV records. Most ISP's will not nor do you want you
>> want
>> the SRV records for your AD domain located on a Public DNS server.
>>
>>
>>
>>
>>
>> > I have few computers which are at common place to do common activities
>> > like
>> > scanning, Internet (didnt want to give everyone access to net). Here
>> > the
>> > problem is if i setup a domain client on this pc, i wouldnt get the
>> > same
>> > desktop with common files or shortcuts on desktop. Also there was a log
>> > on
>> > speed problem (which i will try and check with DNS setup).
>> > What do you suggest for Common PC's, and for PC's with XP but not with
>> > Common users.?
>>
>> Not following you here.
>>
>> > As for long logon times, i am using a IBM X226 8648 iAS server with
>> > Xeon
>> > 3.0
>> > ghz processor and 1 gb ram. Is that causing slow logon times? for my
>> > client
>> > pc's i have ISP's DNS put in as preferred. How do i know my Servers
>> > DNS?
>> > If i
>> > do that how will the clients pc's access the net?
>>
>>
>> It's not the speed of the computer, it's the fact that it *can't* *find*
>> the
>> SRV records for your domain.
>> You need to provide a place on your AD domain to hold those SRV records,
>> that means setting up a DNS server to hold those SRV records. Then you
>> need
>> to tell your AD clients *where* those SRV records are, by pointing them
>> to
>> the DNS server set up for the AD domain.
>>
>> You want to set up a DNS server for your AD domain to hold the private
>> SRV
>> records for your domain.
>>
>> On your servers look at the DNS console for a forward lookup zone with
>> the
>> same name as your AD domain. This is a DNS server for your AD domain.Make
>> sure that in the properties of TCP/IP, this server lists itself as the
>> DNS
>> server. See the "Configure DNS" section here for this:
>> http://support.microsoft.com/kb/814591/en-us
>>
>>
>> Point your AD clients to this DNS server in the properties of TCP/IP.
>> See:
>> http://support.microsoft.com/kb/825036/en-us
>>
>>
>> If i
>>