The Security log auditing of Logon Events is triggered anytime a client connects to the audited machine.
So, if you have Successful logons audited, then everytime a user tries to connect to the server, a record will be written.
This does include double-clicking on a Shared folder, making a drive mapping, even double-clicking on the server in Network Neighborhood.
If you have a logon script that maps a drive to the server, this will be logged.
If a person types in \\MACHINENAME in the Start-> Run box (where MACHINENAME is the name of the server that is auditing), that will generate an alert.
Accessing a shared printer will generate a log.
Basically from a user perspective, anytime they touch the server in any way, it will generate alog event.
Now, just opening Network Neighborhood and seeing all of the servers in your domain will NOT generate a log. But, if a user double-clicks this audited server, that will write an event.