Well, for one million fact points i thought i'd take a stab at it.
i decided to look up the proper definition of what null session is. I have also included the source for this article at the bottom of this post in case anyone was interesed in reading more about null sessions and acknowledge where this reply came from.

Microsoft Windows machines allow remote users to log in remotely (or via their domain) to a server in order to use a shared resource, such as a printer or shared directory. Once a user is logged in, their connection to the remote machine is referred to as a "session".

Microsoft Windows Servers run many services and programs. Some of these services need to communicate with other Windows Servers in order to complete their tasks. Sometimes, a Windows server needs to create a "session" with another Windows server. In some cases, a Windows server will login to a remote Windows Server using a blank username and password. This is referred to as a "Null Session".

Unfortunately, a number of hackers have learned that they also can login to some remote Windows Servers using a blank username and password. They can use this to obtain NetBios information from this machine, and to perform various other exploits against this machine. This is referred to as exploiting the "Null Session Vulnerability"...

The full article and a Null session scanner can be obtained from the author(s) of this article from this link: http://www.lokboxsoftware.com/help/h...ullSession.htm

Do i get the million fact points?

Remote_Access_