Neither of these features work in my environment.  I get a "There was an error checking for updates" message on one and I believe it is due to the fact that we use a  proxy that requires a login.  It could also be that I need to open specific ports that the teamlook install does not enable by default. I'm using version 1.0.1.24

Here is the content of the error I get with submit feedback:

If the web service cannot be reached please verify that the ASP .NET development port matches the port configured in the application web reference and update as necessary.  The application will need to be restarted after the configuration change.

Brandon,

Thank you for posting this issue.  We have had a couple emails about this exact problem.

You correctly concluded that we were not properly detecting proxy configurations.  In our next release we will have much better support for users behind a proxy.  In the next release we will detect the generic machine proxy settings and attempt to use those.  If the default credentials fail, we then call into the secure windows API for entering user name/password.

Look for this next release in the coming weeks.

Cheers,
~Joe