|
Posted by Roger Abell [MVP] on August 23, 2006, 1:36 am
Please log in for more thread options > This is really helpful and thanks.
>
por nada
> What is SNA?
>
An IBM protocol that pre-existed Tcp/Ip and formed first cut
at the 7 layer model of network protocols. I don't recall at the
moment but think it was System rather than Server in System
Network Architecture = SNA
You need those if you articulate with IBM mainframe world,
such as with the MS product aimed at that intercommunication.
> Remote management of objects in my SAM...just what every standalone
> Windows
> box in a DMZ needs! :)
Mostly used in situations like domain join, new account creation, etc.
>
> I tried to empty the list, and immediately many Windows 2003 applications
> start to hang when you logout. So it's back to making smaller random
> experiments and just praying something else doesn't break later.
You want LSA and if in domain Netlogon
If people need to find the list of SQL instances installed SQL/Query, but
not just to use and SQL if they know what instance
Spooler of course supports print services
Browser if will be participating in MS Networking (browse lists, etc.)
>
> --
> Will
>
>
>> Read in the Wiindows Server 2003 Security guide.
>> There you will see that the two you mention are also controlled by the
>> setting to allow (or not) anonymous access to shares and named pipes,
>> and if I recall correctly, the guide recommends emptying the list of
>> shares for high sec environment.
>> The named pipes can be trimmed significantly for most machines.
>> The guide gives use information for these as
>>
>> COMNAP - SNA session access
>> COMNODE - SNA session access
>> SQL\QUERY - SQL instance access
>> SPOOLSS - Spooler service
>> LLSRPC - License Logging service
>> Netlogon - Net Logon service
>> Lsarpc - LSA access
>> Samr - SAM access
>> browser - Computer Browser service
>>
>> which is pretty fully informative except for maybe Samr, which is
>> the protocol for remote management of objects in the Sam.
>
>
| 
XML Sitemap