Discussion Locked

System Policy Editor

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a system with NT Server 4.0 and another one with Windows 95 networked to it. In the server's System Policy Editor, I click on File, Connect, and type in the computer name of the workstation and the server cannot see it. It sees it fine in Network Neighborhood. Also, I have enabled Remote Administration and User Profiles on the workstation. It can also see the server in Network Neighborhood. What gives?

13 replies

by knight205

Sounds Like File and Print sharing has not been enabled on the Windows 95 system or a share has not been setup for the C:, or D: drive of the windows 95 system where the file will be placed. You would get to the drive by putting in the pipe command \\Windows 95(system name)\c$ or whatever share name you give the drive.

by knight205

Sounds Like File and Print sharing has not been enabled on the Windows 95 system or a share has not been setup for the C:, or D: drive of the windows 95 system where the file will be placed. You would get to the drive by putting in the pipe command \\Windows 95(system name)\c$ or whatever share name you give the drive.

by mwf

Is your Win95 PC on a different subnet? You may need to add an entry into the lmhosts file on the server to provide name to address resolution.

by brain_junk

It seems you want to make system policy for windows 95, for your information you cannot make or edit sysetem policy in windows NY 4.0 for win95 you have make it in win95 first and then you can use it in windows NT 4.0. For more information see MS Windows95 resourcekit.

by trebor

The File/Connect command is attempting to connect directly to a machines active registry. When I do this for an NT machine, it lists the user logged onto the computer (both active log ins and services) and asks which one I want to administer. I think that if no one is authenticated to the server from the Win 95 machine, it will find no user, and therefore nothing to administer. Try authenticating to the domain on the win 95 machine and see if that makes it visible to the system policy editor.

by sergio_bourren

How can I create a security policy so that Windows 95 clients who log in domain, cannot have access to change the screen saver?

This discussion is closed to new replies.