Have to reset the passwords every day!!!

[marsha]

I have a network of 6 computers. There is one that is a has a folder that
is mapped
as a drive and that all the other computers use. For some strange reason,
it seems
to lose the passwords for the various other computers (not all of them) so
that I have
to go into control panel and users and reset the password every day. What
could be
causing this. It used to work perfectly (for several years) but is not
becoming a major
pain.

Thanks much to the genius with an answer!!!!

 

[Pegasus \(MVP\)]

I have a network of 6 computers. There is one that is a has a folder that
is mapped
as a drive and that all the other computers use. For some strange reason,
it seems
to lose the passwords for the various other computers (not all of them) so
that I have
to go into control panel and users and reset the password every day. What
could be
causing this. It used to work perfectly (for several years) but is not
becoming a major
pain.

Thanks much to the genius with an answer!!!!

Please be more specific:
- Do you run a workgroup or a domain environment?
- Do your users have individual or shared logon names?
- Does the account on the share's host machine get locked
out? (You wrote that you "lose the password" - you
cannot lose passwords!)
- How does the share get mapped on the various workstations?
Is it a remembered connection? By user interaction? By a script?

 

[marsha]

Please be more specific:
- Do you run a workgroup or a domain environment?
- Do your users have individual or shared logon names?
- Does the account on the share's host machine get locked
out? (You wrote that you "lose the password" - you
cannot lose passwords!)
- How does the share get mapped on the various workstations?
Is it a remembered connection? By user interaction? By a script?

Thanks Pegasus,
It is a workgroup environment. Each computer/user ahs an individual name.
Yes, the individual computers cannot access the host machine until I reset
the password on the host machine for that individual client machine. The
host
folder is mapped as a shared folder. I'm not sure if it is a remembered
connection
or interaction. I'm not sure what that means. It worked for years so I've
lost track
of how I did it. I turn on the host machine first. Then I turn on each
client. At each
client machine, I have to access that folder. It asks for the individual
machine password.
I plug that in and it can access the folder. But during the day, several of
the client computers
can no longer access the host. I sometimes have to reset the password 3
times before
they can access the folder again.
Thanks again for your interest. Any insights are welcome!!!

 

[Pegasus \(MVP\)]

Thanks Pegasus,
It is a workgroup environment. Each computer/user ahs
an individual name. Yes, the individual computers cannot
access the host machine until I reset the password on
the host machine for that individual client machine. The
host folder is mapped as a shared folder. I'm not sure
if it is a remembered connection or interaction. I'm
not sure what that means. It worked for years so I've
lost track of how I did it. I turn on the host machine
first. Then I turn on each client. At each client
machine, I have to access that folder. It asks for the
individual machine password. I plug that in and it can
access the folder. But during the day, several of
the client computers can no longer access the host.
I sometimes have to reset the password 3
times before they can access the folder again.

Thanks again for your interest. Any insights are welcome!!!
========================

I'm still confused, largely because you write things such as
"... until I reset the password on the host machine for that
individual client machine." How do you reset a password
for a client machine? I thought you reset passwords for
a user account, not for a client machine?

I am also puzzled by your mode of operation. You write:
==========
- I turn on the host machine first.
- Then I turn on each client [PC?].
- At each client machine, I have to access that folder
[How exactly do you do this?]
- It asks for the individual machine password.
[What account name do you specify? The same,
regardless of the client machine?]
- I plug that in and it can access the folder.
==========

I suspect that you have a clumsy typer who consistently
mistypes the password, thus causing the account on the
host machine to be suspended.

A far superior way goes like this:

1. Create a number of accounts on the host PC: One for
every staff member in the business.
2. Syncronise the passwords for these host accounts with
the passwords on the client PCs.
3. Create the following batch file on each client PC:

c:\documents and settings\start menu\programs\startup\netlogon.bat
@echo off
call \\HostPC\netlogon\netlogon.bat
(Replace "HostPC" with the real name of the host PC)

4. Start a command prompt on the host machine and type
these commands:
md c:\netlogon
net share netlogon=c:\netlogon
copy con c:\netlogon\netlogon.bat
@echo off
net use S: \\HostPC\NameOfShare
(Press function key F6 here)
(Replace "HostPC" and "NameOfShare" with the actual
names that apply in your case)

5. Check your NTFS permissions on the host:
- Everyone must have read-access to the c:\netlogon folder.
- Everyone must have full access to the shared folder.

6. Check your permissions for the netlogon share:
Everyone must have "Full access" to it.

Doing this would create a tightly controlled environment
that is completely transparent. It will not rely on some
remembered share connections that nobody really knows
what they are and how they came into existence.

 

[Phillip Windell]

I have a novel idea, why a mapped drive letter in the first place? These
are always a "last choice" thing when there is no other way possible to do
something. They are always a bunch of trouble, and they are increasingly
undependable with newer OS that have timeouts on the connection.

Use UNC paths and forget the mapped drives. Or just create a shrocut using
the UNC path and place it in the profile location of "All Users-->Desktop".
Or if it is not required by all users then place the Shortcut in the "My
Documents" of the user so that it appears as just another folder within
their My Documents where most Applications automatically open to when
anything is "opened".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[Andrei Ungureanu]

or could be that someone has discovered how to change your password and is
doing this to annoy you.
Is the account used to share that folder a member of the Administrators
group?


--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader beta!
http://www.altairtech.ca/eventreader/default2.asp?ref=au

Thanks Pegasus,
It is a workgroup environment. Each computer/user ahs
an individual name. Yes, the individual computers cannot
access the host machine until I reset the password on
the host machine for that individual client machine. The
host folder is mapped as a shared folder. I'm not sure
if it is a remembered connection or interaction. I'm
not sure what that means. It worked for years so I've
lost track of how I did it. I turn on the host machine
first. Then I turn on each client. At each client
machine, I have to access that folder. It asks for the
individual machine password. I plug that in and it can
access the folder. But during the day, several of
the client computers can no longer access the host.
I sometimes have to reset the password 3
times before they can access the folder again.

Thanks again for your interest. Any insights are welcome!!!
========================

I'm still confused, largely because you write things such as
"... until I reset the password on the host machine for that
individual client machine." How do you reset a password
for a client machine? I thought you reset passwords for
a user account, not for a client machine?

I am also puzzled by your mode of operation. You write:
==========
- I turn on the host machine first.
- Then I turn on each client [PC?].
- At each client machine, I have to access that folder
[How exactly do you do this?]
- It asks for the individual machine password.
[What account name do you specify? The same,
regardless of the client machine?]
- I plug that in and it can access the folder.
==========

I suspect that you have a clumsy typer who consistently
mistypes the password, thus causing the account on the
host machine to be suspended.

A far superior way goes like this:

1. Create a number of accounts on the host PC: One for
every staff member in the business.
2. Syncronise the passwords for these host accounts with
the passwords on the client PCs.
3. Create the following batch file on each client PC:

c:\documents and settings\start menu\programs\startup\netlogon.bat
@echo off
call \\HostPC\netlogon\netlogon.bat
(Replace "HostPC" with the real name of the host PC)

4. Start a command prompt on the host machine and type
these commands:
md c:\netlogon
net share netlogon=c:\netlogon
copy con c:\netlogon\netlogon.bat
@echo off
net use S: \\HostPC\NameOfShare
(Press function key F6 here)
(Replace "HostPC" and "NameOfShare" with the actual
names that apply in your case)

5. Check your NTFS permissions on the host:
- Everyone must have read-access to the c:\netlogon folder.
- Everyone must have full access to the shared folder.

6. Check your permissions for the netlogon share:
Everyone must have "Full access" to it.

Doing this would create a tightly controlled environment
that is completely transparent. It will not rely on some
remembered share connections that nobody really knows
what they are and how they came into existence.

 

[Pegasus \(MVP\)]

I have no problem with UNC paths but I strongly disagree with
your claim that mapped drives "are increasingly undependable
with newer OSs". I have numerous sites that use mapped drive
letters, running anything from Win98 to WinXP, and they
experience no problem whatsoever. Perhaps you could refer
to some MS KB article that supports your claim?

 

[Phillip Windell]

experience no problem whatsoever. Perhaps you could refer
to some MS KB article that supports your claim?

There are the hundreds of newsgroup questions about problems with them that
are found all throughout the various "networking" newsgroups.

There is at least one KB article that was always passed around about
extending the timeout value of the "maps", that never solved the problem, it
only took the problem longer to happen (longer timeouts). The problem stems
from the "map" not reconnecting as it was supposed to when it was hit by
"activity" after the timeout period. I have never seen a solution given,
nor a patch given to solve it.

We have some here that I am unable to get away from due to poorly designed
Applications. Most of the time they work fine,...sometimes they do not.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[Pegasus \(MVP\)]

I hear what you say but until I see some authoritative KB article
on the subject I tend to believe what I see with my own eyes.
I know that there are lots of newsgroup questions on the topic.
The vast majority are based on insufficient knowledge about
networking, including this one. To draw a parallel, there are
thousands of claims that third party engine oil additives make
cars use less petrol and extend life expectancy, yet car makers
just shrug them off as a waste of money. So let's see this
KB article you're thinking of!

experience no problem whatsoever. Perhaps you could refer
to some MS KB article that supports your claim?

There are the hundreds of newsgroup questions about problems with them that
are found all throughout the various "networking" newsgroups.

There is at least one KB article that was always passed around about
extending the timeout value of the "maps", that never solved the problem, it
only took the problem longer to happen (longer timeouts). The problem stems
from the "map" not reconnecting as it was supposed to when it was hit by
"activity" after the timeout period. I have never seen a solution given,
nor a patch given to solve it.

We have some here that I am unable to get away from due to poorly designed
Applications. Most of the time they work fine,...sometimes they do not.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

 

[marsha]

or could be that someone has discovered how to change your password and is
doing this to annoy you.
Is the account used to share that folder a member of the Administrators
group?

Yes, they are all Administrators, but I don't think anyone would do that.
Thanks

 

[marsha]

I have a novel idea, why a mapped drive letter in the first place? These
are always a "last choice" thing when there is no other way possible to do
something. They are always a bunch of trouble, and they are increasingly
undependable with newer OS that have timeouts on the connection.

Use UNC paths and forget the mapped drives. Or just create a shrocut using
the UNC path and place it in the profile location of "All Users-->Desktop".
Or if it is not required by all users then place the Shortcut in the "My
Documents" of the user so that it appears as just another folder within
their My Documents where most Applications automatically open to when
anything is "opened".

That is interesting. I didn't want to get into details that I thought were
unnecessary,
but the folder that is mapped is because of the specialty software that is
used. The
company has bought the software and is dedicated to using it. They are the
ones that
tell us how to map the folder as a drive to appear on all the computers. It
is for appraisal
(homes) software. So all of the client machines are appraisers who use that
software. For
some reason, they have all started having problems connecting to the folder
on the server
machine. Some client computers have more problems more than others. But
the solution
is to go into the server and control panel and reset the password for that
client computer.
But it is getting VERY old doing this. I'm sorry I am unable to use the
correct terminology.
Thanks for any help!!!!

 

[marsha]

I'm still confused, largely because you write things such as
"... until I reset the password on the host machine for that
individual client machine." How do you reset a password
for a client machine? I thought you reset passwords for
a user account, not for a client machine?

Of course you are right. I have to reset the passwords on
the server for each individual client.

I am also puzzled by your mode of operation. You write:
==========
- I turn on the host machine first.
- Then I turn on each client [PC?].
- At each client machine, I have to access that folder
[How exactly do you do this?]
- It asks for the individual machine password.
[What account name do you specify? The same,
regardless of the client machine?]

No, each machine has it's own name.
and a separate password. Actually, I'm confused because
some client machines seem to check the server and connect
automatically. Others require the entry of the appropriate
password.

==========

I suspect that you have a clumsy typer who consistently
mistypes the password, thus causing the account on the
host machine to be suspended.

I don't think so. They normally enter the password once
and that is supposed to stay connected all day.

A far superior way goes like this:

1. Create a number of accounts on the host PC: One for
every staff member in the business.
2. Syncronise the passwords for these host accounts with
the passwords on the client PCs.

Step 1 and 2 is what we have done. I don't understand step
3. Sorry for being so dumb.

3. Create the following batch file on each client PC:

c:\documents and settings\start menu\programs\startup\netlogon.bat
@echo off
call \\HostPC\netlogon\netlogon.bat
(Replace "HostPC" with the real name of the host PC)

4. Start a command prompt on the host machine and type
these commands:
md c:\netlogon
net share netlogon=c:\netlogon
copy con c:\netlogon\netlogon.bat
@echo off
net use S: \\HostPC\NameOfShare
(Press function key F6 here)
(Replace "HostPC" and "NameOfShare" with the actual
names that apply in your case)

5. Check your NTFS permissions on the host:
- Everyone must have read-access to the c:\netlogon folder.
- Everyone must have full access to the shared folder.

Everyone does have full access to the shared folder. That is the
way the software works.

6. Check your permissions for the netlogon share:
Everyone must have "Full access" to it.

I guess they do. How do I check this? Every user (client
computer) is an administrator on the server.

 

[Pegasus \(MVP\)]

I'm still confused, largely because you write things such as
"... until I reset the password on the host machine for that
individual client machine." How do you reset a password
for a client machine? I thought you reset passwords for
a user account, not for a client machine?

Of course you are right. I have to reset the passwords on
the server for each individual client.

I am also puzzled by your mode of operation. You write:
==========
- I turn on the host machine first.
- Then I turn on each client [PC?].
- At each client machine, I have to access that folder
[How exactly do you do this?]
- It asks for the individual machine password.
[What account name do you specify? The same,
regardless of the client machine?]

No, each machine has it's own name.
and a separate password. Actually, I'm confused because
some client machines seem to check the server and connect
automatically. Others require the entry of the appropriate
password.

==========

I suspect that you have a clumsy typer who consistently
mistypes the password, thus causing the account on the
host machine to be suspended.

I don't think so. They normally enter the password once
and that is supposed to stay connected all day.

A far superior way goes like this:

1. Create a number of accounts on the host PC: One for
every staff member in the business.
2. Syncronise the passwords for these host accounts with
the passwords on the client PCs.

Step 1 and 2 is what we have done. I don't understand step
3. Sorry for being so dumb.

3. Create the following batch file on each client PC:

c:\documents and settings\start menu\programs\startup\netlogon.bat
@echo off
call \\HostPC\netlogon\netlogon.bat
(Replace "HostPC" with the real name of the host PC)

4. Start a command prompt on the host machine and type
these commands:
md c:\netlogon
net share netlogon=c:\netlogon
copy con c:\netlogon\netlogon.bat
@echo off
net use S: \\HostPC\NameOfShare
(Press function key F6 here)
(Replace "HostPC" and "NameOfShare" with the actual
names that apply in your case)

5. Check your NTFS permissions on the host:
- Everyone must have read-access to the c:\netlogon folder.
- Everyone must have full access to the shared folder.

Everyone does have full access to the shared folder. That is the
way the software works.

6. Check your permissions for the netlogon share:
Everyone must have "Full access" to it.

I guess they do. How do I check this? Every user (client
computer) is an administrator on the server.

Doing this would create a tightly controlled environment
that is completely transparent. It will not rely on some
remembered share connections that nobody really knows
what they are and how they came into existence.

When you work in a domain environment then each user
profile can have a reference to a network logon batch file
included so that drives are mapped fully automatically at
logon time.

You work in a workgroup environment, hence this centralised
script is not directly available. However, you can still do it,
by placing a logon file into the Startup folder. It will run
automatically when a user logs on. And if you make it like so:

call \\HostPC\netlogon\netlogon.bat

then you can control the logon process centrally, because
each and every user invokes "netlogon.bat" on "HostPC"!
==========
Share permissions are checked by launching Explorer,
right-clicking the shared folder, then clicking "Share" and
"Permissions".

By the way, you write "No, each machine has its own name.
and a separate password." It seems we're back to saying
that passwords are assocaiated with machines. THEY ARE NOT!
Do you perhaps mean to say "No, each user has his/her own
logon name and a separate password"? And are these
personal logon names / password all registered on the
host machine?

 

[Phillip Windell]

I hear what you say but until I see some authoritative KB article
on the subject I tend to believe what I see with my own eyes.

Then we are in the same position,...we just aren't seeing the same thing.
As far as the KB article you could probably find it just as easily. I have
seen it where others quoted from it or posted the link in their posts,..I
never kept the link and there is no way I could memorize that along with
everything else I am expected to know.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[Phillip Windell]

That is interesting. I didn't want to get into details that I thought were
unnecessary, but the folder that is mapped is because of the specialty software that is
used. The company has bought the software and is dedicated to using it. They are the
ones that tell us how to map the folder as a drive to appear on all the computers. It
is for appraisal (homes) software.

First, I would try it with a UNC path. Sometimes it works even when no one
thinks it will work (including the developers).

If it doesn't work, then you are stuck with the mapped drives.

When the drive goes into a disconnected state you can reconnect it by simply
"opening" it with Windows Explorer (open My Computer, double-click on the
Drive letter).

Mapped Drive Connection to Network Share May Be Lost
http://support.microsoft.com/default.aspx?scid=kb;en-us;297684

However as I said, we live in an imperfect world,...they don't always
reconnect properly like they are supposed to. The real solution is for the
developers of the Application to come out of the "stone age" and write the
Application so that it doesn't use them. We have not been able to get rid
of all of those situations here either,...but rest assured the developers
know what I think about it. I am not known for being "passive".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[Phillip Windell]

The article may have been the one I quoted to Marsha. It is the one about
changing the timeouts that I spoke of. It was not the issue of them
failing to reconnect that I was saying there was a KB on it. The fact is
that mapped drives don't always reconnect as they should. I don't need a KB
article for that. MS has actually encouraged MVPs to get envolved it the
production of KB articles because not all problems have KB articles for them
and other problems are not even fully acknowledged as "existing",...but it
doesn't mean the problem does exist. The problem with submitting a KB is
that you have to have a proven solution for a reproducable problem and I
have never seen a solution, and it is an intermitten problem that doesn't
seem to be reproducable "on demand".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[marsha]

By the way, you write "No, each machine has its own name.
and a separate password." It seems we're back to saying
that passwords are assocaiated with machines. THEY ARE NOT!
Do you perhaps mean to say "No, each user has his/her own
logon name and a separate password"? And are these
personal logon names / password all registered on the
host machine?

Yes, again you are right and once again I must ask forgiveness for
my clumsiness in wording due to ignorance. I like what you have
said and I can't tell you how thankful I am for you taking the time to
help. I will talk with the software company and see if they have any
reasons why we shouldn't do this. Thanks for this and any further
insights you might be so gracious as to give.

 

[marsha]

When the drive goes into a disconnected state you can reconnect it by simply
"opening" it with Windows Explorer (open My Computer, double-click on the
Drive letter).

We have tried that many times and it never works. As I stated, what seems
to
work best is to reset the password for that user on the server machine.

Mapped Drive Connection to Network Share May Be Lost
http://support.microsoft.com/default.aspx?scid=kb;en-us;297684

However as I said, we live in an imperfect world,...they don't always
reconnect properly like they are supposed to. The real solution is for the
developers of the Application to come out of the "stone age" and write the
Application so that it doesn't use them. We have not been able to get rid
of all of those situations here either,...but rest assured the developers
know what I think about it. I am not known for being "passive".

I also want to thank you for the time and energy you have taken to try and
help. Be assured I will mention your ideas to the developers and see what
they
say. If they say anything, I will come back and post it.
Thanks very much!!!!