Your cleanup rule on your inside interface has nothing to do with your issue.
Modern firwalls are statful so you don't need to explicitly allow traffic to go back to the original source.
What you need to do is to allow traffic from ANY to the NATED IP of your server.
access-list outside_access_in extended permit udp any host W_BASE object-group W_UDP
Then do a simple static NAT.
static (inside,outside) interface W_BASE netmask 255.255.255.255
Since you are not forwarding the ports, you can keep your NAT very simple and simply open the correct ports with your ACL.
You could also simplify your service objects like so:
object-group service W_Ports
service-object tcp eq 3005
service-object udp range 3000 3002
Then use W_Ports instead of having W_UDP and W_TCP.
Your ACL would then look like this:
access-list outside_access_in extended permit object-group W_Ports any object-group W_BASE
UPDATED version:
access-list outside_access_in extended permit object-group W_UDP any host W_BASE
The service is listening on the loopback adapter only. If you use the -n option to lsof (or netstat or ss), you'll see that the listening address is 127.0.0.1:27017. This means that connections made to your network IP address will not reach the listening process.
It looks like you need to set the net.bindIp configuration option.
Best Answer
Windows SharePoint Services could be opening that port thru uPNP.