Peer to peer

[Jerry Fortenberry]

We have peer to peer networks at some locations. The ones that are all
Windows 98 work as expected. In the mixed environments, we have a Windows
2000 Pro or Windows XP pro set as the host.... it shares hard drive and
printers. All W2k and XP pc's are joined to the domain. On the "host" I give
rights to the other Windows 98 users based on them being a user on the
domain. My question also pertains to the networks that are completely W2k.
Everything works well as long as the domain is accessible. If the domain
controller goes down or they loose connectivity to the WAN, then the shares
on the host become inaccessible to other pc's. I need to configure the
host shares in such a way that they can be seen even if the domain
controller is down. Thank you.

 

[CZ]

We have peer to peer networks at some locations. The ones that are all
Windows 98 work as expected. In the mixed environments, we have a Windows
2000 Pro or Windows XP pro set as the host.... it shares hard drive and
printers. All W2k and XP pc's are joined to the domain. On the "host" I give
rights to the other Windows 98 users based on them being a user on the
domain. My question also pertains to the networks that are completely W2k.
Everything works well as long as the domain is accessible. If the domain
controller goes down or they loose connectivity to the WAN, then the shares
on the host become inaccessible to other pc's. I need to configure the
host shares in such a way that they can be seen even if the domain
controller is down. Thank you.

Jerry:

Why not create a second DC?

 

[GTS]

If you are granting share rights to domain members and the domain controller
is down, it makes sense that the shares could not be accessed. The host
will attempt to validate the access right through the domain server. To
permit access if it is down would require setting rights in addition to
domain membership. For a Win2K host, you would have to add user accounts
for the clients and set permissions for them to permit access and retain a
level of security.

 

[Jerry Fortenberry]

Money...there are 14 of these small networks

Windows 98 work as expected. In the mixed environments, we have a Windows
2000 Pro or Windows XP pro set as the host.... it shares hard drive and
printers. All W2k and XP pc's are joined to the domain. On the "host" I give
rights to the other Windows 98 users based on them being a user on the
domain. My question also pertains to the networks that are completely W2k.
Everything works well as long as the domain is accessible. If the domain
controller goes down or they loose connectivity to the WAN, then the shares
on the host become inaccessible to other pc's. I need to configure the
host shares in such a way that they can be seen even if the domain
controller is down. Thank you.

Jerry:

Why not create a second DC?

 

[Jerry Fortenberry]

I understand what you are saying and feel I have done that. There seems to
be an issue loosing the drive mappings from the Windows 98 pc's to the
2000/xp host (when the domain is inaccessible). I need the drive
connections to be based on domain authentication when possible or host
(2000/xp) authentication when the domain is not available


..

If you are granting share rights to domain members and the domain controller
is down, it makes sense that the shares could not be accessed. The host
will attempt to validate the access right through the domain server. To
permit access if it is down would require setting rights in addition to
domain membership. For a Win2K host, you would have to add user accounts
for the clients and set permissions for them to permit access and retain a
level of security.
--

 

[GTS]

In your initial post you said "On the "host" I give rights to the other
Windows 98 users based on them being a user on the
domain." I assumed from this that you are granting the rights to domain
members, and did not create individual user accounts for the 98 users. In
that case, if the host, cannot communicate with the domain server to
validate the permission, it will not allow access.

What I was suggesting was that you would have to create an individual user
account on the host for each Win 98 PC. Note that the account must exactly
match the user name and password used in the Win 98 machine logon. (Blank
passwords are not allowed by default, although that can be changed in
security policies.)

I'm not sure of how the server will sequence the application of permissions
when both (i.e. domain membership and individual user accounts) are present,
but suspect it shouldn't interrupt access if initially validated by the
domain server and that drops out.
--

I understand what you are saying and feel I have done that. There seems to
be an issue loosing the drive mappings from the Windows 98 pc's to the
2000/xp host (when the domain is inaccessible). I need the drive
connections to be based on domain authentication when possible or host
(2000/xp) authentication when the domain is not available


.