Password changing problem

August 17th, 2005 - 03:46 am ET by Viktor | Report spam
Hi,

I have a problem, which already appeared on this board, but I found no exact
answer, what to do...
So the issue is the following:
We have an NT4.0 domain, with 2000 member servers and client. We have a
preset password expiration day-limit, when the users should change their
passwords.
This worked perfectly untill yesterday, when a user reported, that it is not
possible for him to change, altough the changing window appeared, but after a
very long waiting it wrote out that it cannot reach the domain.
According to my knowledge nothing was changed in the configuration.

As I read the previous messages I tried the pings: with the IP it worked
perfectly, with the name worked also, but a bit slower...

So it would be just great if You could please help!

Thanx in advance,
Viktor
email Follow the discussionReplies 2 repliesReplies Make a reply

Replies

#1 Viktor
August 18th, 2005 - 02:28 am ET | Report spam
Thanx for the answer!

I checked the mapping: it worked both ways, without any problem...
I ran also nbtstat -c, and I see the following:

Server1(PDC) 00 UNIQUE IP-ADDRESS 2
Server2(BDC and WINS) 00 UNIQUE IP-ADDRESS 2
Server3(WINS) 00 UNIQUE IP-ADDRESS 362
Server1(PDC) 20 UNIQUE IP-ADDRESS 295
Domain-name 1B UNIQUE IP-ADDRESS(of PDC) 275
Domain-name 1C GROUP IP-ADDRESS(of PDC) 270
Server4(just a Member) 20 UNIQUE IP-ADDRESS 217

I hope it is more informative to You, than to me...

Thank You for Your answer in advance.

"Michael Giorgio - MS MVP" wrote:

Attempt to map to a share on the PDC first by
tcp/ip address then by name. If either fails post
the exact error. When a user attempts to change
their password and fails open a dos prompt and
run nbtstat -c, what do you see?

"Viktor" wrote in message news:.
> I have a problem, which already appeared on this board, but I found no
> exact
> answer, what to do...
> So the issue is the following:
> We have an NT4.0 domain, with 2000 member servers and client. We have a
> preset password expiration day-limit, when the users should change their
> passwords.
> This worked perfectly untill yesterday, when a user reported, that it is
> not
> possible for him to change, altough the changing window appeared, but
> after a
> very long waiting it wrote out that it cannot reach the domain.
> According to my knowledge nothing was changed in the configuration.
>
> As I read the previous messages I tried the pings: with the IP it worked
> perfectly, with the name worked also, but a bit slower...
>
> So it would be just great if You could please help!





Similar topics