unusual port 445 connections

I'm running a member server in an AD domain that functions like the domain controller for my workgroup.  In other words, the workstations connect to the server for file sharing, but the server itself isn't at the top of the AD domain, just a member server in my delegated OU.  Anyway, I try to restrict access to the workstations and the server as much as possible, but I'm relatively new to all of this so I have to utilize a guess-and-check method more often than not.

I've noticed that the member (win 2k3) server has connections that I thought were blocked.  In the GPO for the server, I allow acces to the computer from only the computers in my OU and the DC (obviously), and I only allow logins from my OU users.  That being said, I find connections with netstat -a that are connecting to port 445 from unauthorized computers.  Since the computers in question aren't authorized to log in, nor to access the computer from the network, I'm wondering how TCP/IP connections can be established at all, even if they aren't showing up as attempted logins in the security log.  

I also notice that another member server in the domain is able to login (according to the security log) as ANONYMOUS LOGON, even though anonymous connections are forbidden (the DC logs in that way as well, but that doesn't bother me because I can't override the DC's authority).  I've never had any formal training in network administration, and while I can keep things running fine, I'm frustrated at some of the confusing hair-splitting involved here.  I don't believe my server is being hacked, but I also don't know why systems other than the DC and the workstations in my OU are connecting when only the latter two were granted access.  

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

could these be outbound connections from the server itself?  check and see if the "automatically search for network folders and printers" setting under folder options is turned off on the server... also.. you may want to use an ip security policy to allow only the computers you want to access the server access...  the 445 connections could the client systems attempting to search for network folders and printers as well... they would be able to initiate and establish a 445 session but just wouldn't be able to authenticate... although... being as the member server is on the same playing field as a member workstation the system accounts should still be able to authenticate on the server... users wouldn't be able to access the resources though unless they ran a script as the system account on their workstation....  ofcourse... an ip security policy would prevent even these connections...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.