Add DB server IP to localhost when using SQL Alias

So, when you implement the "best practice" of using SQL Server ALIAS names (to be flexible at all times of where your SharePoint databases will be hosted), apparently it's also a best practice to add the IP & ALIAS name to (all) your WFE & APP's that are using this name.

This came to my attention when I started receiving ERROR logs in the windows APP log of a WFE:

Log Name: Application

Source: Microsoft-SharePoint Products-SharePoint Foundation

Date: 2013/10/02 07:24:00 AM

Event ID: 6398

Task Category: Timer

Level: Critical

Keywords: 

User: **

Computer: **

Description:

The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDatabaseServerDiagnosticsPerformanceCounterProvider (ID 5bce4422-820a-465f-aee4-5ce0f31640ce) threw an exception. More information is included below.

SharePointDbServer:The network path was not found.

;

Please ensure that the database server is available

Eh.. duh.. of course the database server is available.. I personally know the DBA ! :P :P 

(Yeah, he's one of my personalities)...

Ok; so .. apparently when you use the SPDiag toolkit from MS, this toolkit starts monitoring stuff and will trigger above ERROR in your eventlog, as being described here:

http://social.technet.microsoft.com/Forums/sharepoint/en-US/4b397f6c-249a-43f0-aa91-ff210e4e132b/timer-event-6398-spdatabaseserverdiagnosticsperformancecounter

Thank you so much Mohammed Al-Basri for pointing this out :) 

I added the HOME ip (in this case it's a single server install) 127.0.0.1 + DB ALIAS name and voila, another problemo solved !

Unable to save (word) file on SharePoint 2010

Thanks to: http://blog.domcosgrove.com/this-file-cannot-be-saved-to-this-location-because-there-is-no-connection/

Building a POC for a client I ran into this issue on my Virtual Box virtual SharePoint 2010 environment; While saving the word document in a document library I would get:
This file cannot be saved to this location because there is no connection

The solution is to open up good old DOS command prompt and type:

net stop sens

(Temp solution..)
Voilla! It works like a charm :)

More perminent solution is to disable the System Event Notification service