Ok here's the problem.
When you switched to extensionless urls, the 'old' urls (with the extension at the end) are now considered to be 'less friendly' than the full url with the extension. As such, you get a redirect to the second url that you show. As you can see, the _utm values are now incorporated into the friendly url path, which I imagine stops the analytics code from working correctly, as the rewriting (to tabid=xx&_utm=souce etc) happens at the internal asp.net level, and the google code runs as javascript and doesn't see the rewritten url.
So, there's two ways to fix this:
1) change the urls in your google links, so that no redirect occurs. This just means removing the .aspx from the url, leaving www.culookup.com/calculatorsforyourwebsite?_utm_source=NAFCUWebsite... (etc). By doing this, you won't get a redirect, and the utm_ parameters won't get included in the path.
2) update the regex field in the 'Host->Friendly Url Settings->Advanced Regex Settings' section, called 'doNotIncludeInPath'. All you would need is a value called utm_ - this prevents the utm_ parameters from being included in the friendly url Path (ie, keeps them in the qureystring section of the url).
Either way will work as effectively.
Note that you won't have stopped getting tracking data on Google Analytics, it's just that the new Urls will start a new record (ie will start counting from zero) because Analytics sees them as distinctly different Urls (which they are). You'll have to manually add the two values together during the reporting period, until you have had the new urls running for a full reporting period.
-Bruce