Windows 95

[Techdewd49]

I know this is a Win 2000 forum, but since there is nothing for Windows 95
hopefully someone here can help me out?

One of my locations recently migrated to a 2003 ad enviroment and many of
their workstations are loaded with windows 95. Here is his question:

Maryville has a number of factory PCs that connect to older equipment and
which are running Windows 95 and need access to the network. We installed DS
Client for window 95 on these PCs back when we did the AD migration and this
allowed them to login into the HI domain. Today, a user called saying that
after he changed his password he was no longer able to log in into the
Windows 95 PCs anywhere. He gets the message: “the domain password you
supplied is not correct or access to your logon server has been denied†If he
tries this too many times, his account gets locked out. Have there been any
policy changes on the DC that could be causing this? Any other accounts that
have not changed passwords are able to login without a problem. I went to
check the problem and was able to login with my admin account; then I changed
the password on my account and could not log in either after that. This can
become a critical issue since they need these legacy PCs on the network for
production.


Thanks for the help in advance!

 

[Pegasus [MVP]]

I know this is a Win 2000 forum, but since there is nothing for Windows 95
hopefully someone here can help me out?

One of my locations recently migrated to a 2003 ad enviroment and many of
their workstations are loaded with windows 95. Here is his question:

Maryville has a number of factory PCs that connect to older equipment and
which are running Windows 95 and need access to the network. We installed
DS
Client for window 95 on these PCs back when we did the AD migration and
this
allowed them to login into the HI domain. Today, a user called saying that
after he changed his password he was no longer able to log in into the
Windows 95 PCs anywhere. He gets the message: "the domain password you
supplied is not correct or access to your logon server has been denied" If
he
tries this too many times, his account gets locked out. Have there been
any
policy changes on the DC that could be causing this? Any other accounts
that
have not changed passwords are able to login without a problem. I went to
check the problem and was able to login with my admin account; then I
changed
the password on my account and could not log in either after that. This
can
become a critical issue since they need these legacy PCs on the network
for
production.


Thanks for the help in advance!

Type this into a Google search box:
"public.win95"
"public.win98"
You will get more relevant newsgroups than you can poke a stick at. By the
way, isn't it time to replace this antiquated and unsupported operating
system with something more up-to-date and far more stable?

 

[Anteaus]

Your problem here is almost certainly the "Microsoft network server:
Digitally sign communications (always)" policy setting.

It's under Local Polices>Security Options.

Pre-NT OS's do not support signed communications.

 

[Techdewd49]

The issue with upgrading is my admin has legacy apps that will only work with
95.

 

[Phillip Windell]

I really doubt the Legacy Apps won't also run on at least Win98SE. Most
likely they will still run on Windows2000,...and in many cases they will
even run on XP if you set the Compatibiliy Mode in the properties of the
Apps executable.

I have run many old things designed for Win95 on an XP machine. In some
cases it was only the Apps installation program that would refuse to run and
not the App itself,...so I installed it on an old Win9x first then just
copies the File Tree over to the XP machine,...set the Compatibility to what
it needed in th eproperties of the executable and it worked. If registry
entries are required (often they really aren't) they can be exported from
the old machine and imported into XP with Regedit via *.reg text files.

Try it rather than just taking the vendors word for it.
Also if the vendor wants to stay in business,...they need to bring their
product out of the dark ages.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.

 

[Techdewd49]

Thanks for the advise, but I'm only relaying the message of one of my admins.
I don't know his enviroment or specifically which apps he uses or why he
hasen't moved on from that archaic OS.

 

[Phillip Windell]

Well, you can pass my post on to him.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Ace Fekay [Microsoft Certified Trainer]]

Thanks for the advise, but I'm only relaying the message of one of my
admins.
I don't know his enviroment or specifically which apps he uses or why he
hasen't moved on from that archaic OS.

Just to add, I've gotten legacy apps to run on Vista by using the
compatibility settings for the executable.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup/forum to benefit from collaboration among
responding engineers, as well as to help others benefit from your
resolution.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(e-mail address removed)
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

 

[sgrove]

Techdewd49 - did you find a solution to your problem? I have the exact
problem that you encountered. Just wondering if you can share the solution.

 

[Ace Fekay [MCT]]

Techdewd49 - did you find a solution to your problem? I have the exact
problem that you encountered. Just wondering if you can share the
solution.

Sgrove,

Did my suggestion help?

Ace

 

[sgrove]

No, The app is specific for 98. I tried running it for 2000/xp/vista
compatibility mode with no luck.

 

[Phillip Windell]

On the original problem:

Which was,...Change password,...now it doesn't authenticate.....

Delete the <username>.pwl file from the C:\Windows folder on the Win9x
machine.
Log off,..then log on,...try again.

Windows9x "caches" the passwords in a password file (*.pwl) that begins with
the username that it is tied to.

It was never made clear how he actually "changed the password",...it is very
possible that he only changed it on the Win9x machine (*.pwl) but never
changed it on the Domain,...or just the opposite,...changed it on the Domain
but not locally on Win9x.

I recommend first resetting the password in Active Directory first and *do
not* use the WIn9x machine to do this,...do it from a "real" machine,...and
verify it happened correctly by logging into the Domain from a "real"
machine.

Then after that delete aforementioned <username>.pwl file on the Win9x box
and then log into it with the new password which will create a *new* PWL
file.

Concerning the "DS Client for Win9x",...the only time I ever used that all
it did was make a mess of things. I ran Win9x machines on an Active
Directory domain for years and never ever ever ever installed the DS Client
for Win9x. It has nothing to do with your ability (or lack there of) to
log into the Domain. I don't remember all the supposed benefits of using
the thing,..but I do remember that I didn't think any of them were important
or critical,...so i never ever used it beyond the couple experimental
attempts that I was not impressed with.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[sgrove]

Thanks for the direction Phillip. I will give it a shot and post the results.

Steve

 

[sgrove]

Still having issues...
I changed the password for the AD user account and then sucessfully logged
onto the network with it on an XP Pro machine. I then deleted all the *.pwl
files from the 98 computer. I went one step further and unchecked the box so
the computer would not log into a windows nt domain. The login on the 98
computer worked just fine. When I went back and turned on "log on to windows
nt domain" the user id fails. This is where I get the error "The domain
password you supplied is not correct, or access to your logon server has been
denied".

Steve

 

[Ace Fekay [MCT]]

Still having issues...
I changed the password for the AD user account and then sucessfully logged
onto the network with it on an XP Pro machine. I then deleted all the
*.pwl
files from the 98 computer. I went one step further and unchecked the box
so
the computer would not log into a windows nt domain. The login on the 98
computer worked just fine. When I went back and turned on "log on to
windows
nt domain" the user id fails. This is where I get the error "The domain
password you supplied is not correct, or access to your logon server has
been
denied".

Steve

IIRC, if you're not using the DS client on a 9x machine, you will need to
detune the SMB signing policy on the DCs. Are you familiar with this policy?

Overview of Server Message Block signing
http://support.microsoft.com/kb/887429

How to upgrade Windows 2000 domain controllers to Windows Server 2003
For information about how to disable SMB signing, see the section "To
disable SMB ..."
http://support.microsoft.com/kb/325379

Ace

 

[Phillip Windell]

I then deleted all the *.pwl

files from the 98 computer. I went one step further and unchecked the box
so
the computer would not log into a windows nt domain.

Why whould you do that! I didn't say do that. You *want* it to log into
the Domain!

Ace makes a key point with SMB. I had forgot about that,....most of us
probably have,...it's been along time since Win9x.

Disable the SMB signing (because WIn9x can't handle it)
Leave it set to log into the domain.
Delete the *.pwl file,...heck for that matter delete every *.pwl file on the
machine.
Reboot and try again.

How to upgrade Windows 2000 domain controllers to Windows Server 2003
For information about how to disable SMB signing, see the section "To
disable SMB ..."
http://support.microsoft.com/kb/325379

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Ace Fekay [MCT]]

Ace makes a key point with SMB. I had forgot about that,....most of us
probably have,...it's been along time since Win9x.

Yep, I almost forgot about that. I was staring at this thread for a few
moments before it hit me about increased SMB security with 2003.

Ace