Hi Alan,
Of course we should consider the real world and Samba does usually
serve Windows clients. By "outside the scope of Samba" I meant
"outside the scope of what should be tested on a Samba exam", i.e. we
should test that Samba is doing the correct thing per SMB/CIFS, not
check that the client is doing the correct thing per SMB/CIFS.
I think this is not enough. The samba admins will be held responsible by
their employees if the Windows clients cant work with the servers, so
they should be able to diagnose and fix the client problem.
Imagine a scenario where Samba is set up correctly, but the client is
using the wrong authentication method. Should we have items on fixing
that client?
Yes, we should. :-) Because that's the real world LPICP-3 will live.
Remember that this then involves all the peculiarities
of different Windows versions, and LPI does not have a mandate to
test Windows competencies. In a case like this, the correct answer on
an item about this can be limited to "Samba is configured correctly,
the client is mis-configured".
Do you really believe anyone will be able to make such a statement and
not being able to fix the client?
And maybe the problem is not with either the Samba server nor the
Windows client. For example, tt could be caused by a mistake on the
dhcpd.conf file, that points to the wrong nbns (wins) server. The
LPICP-3 should be able to find and fix this kind of problem, and we
should test for that.
[]s, Fernando Lozano
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/mailman/listinfo/lpi-examdev
