T
Tom Penharston
Workgroup connectivity
1. Ping from client to the server, or visa versa. No authentication.
2. If shares are enabled, SMB - Samba file sharing between client and
server, or visa versa. SMB authentication.
3. If IIS enabled, client browses server. No authentication, or
certificates.
4. If Remote Assistance or Remote Desktop are enabled on client, server
can access client via IP address using local account authentication.
5. WSUS connectivity via IP address.
Active Directory connectivity
1. Manage - Computer Management MMC
2. Group Policy
3...
At this point I need some help. Active Directory supports different
functionalies, but aren't all of the secure channels the same?
What's the baseline connectivity test for a secure channel?
Once I am able to use the management console on a remote machine, then
can I reasonably assume that all Group Policies will succeed?
(Terminal Services is more complex, with licensing requirements etc.;
so disregard for this discussion.)
1. Ping from client to the server, or visa versa. No authentication.
2. If shares are enabled, SMB - Samba file sharing between client and
server, or visa versa. SMB authentication.
3. If IIS enabled, client browses server. No authentication, or
certificates.
4. If Remote Assistance or Remote Desktop are enabled on client, server
can access client via IP address using local account authentication.
5. WSUS connectivity via IP address.
Active Directory connectivity
1. Manage - Computer Management MMC
2. Group Policy
3...
At this point I need some help. Active Directory supports different
functionalies, but aren't all of the secure channels the same?
What's the baseline connectivity test for a secure channel?
Once I am able to use the management console on a remote machine, then
can I reasonably assume that all Group Policies will succeed?
(Terminal Services is more complex, with licensing requirements etc.;
so disregard for this discussion.)