Armstrongest's questions

It would appear that on my brand new Windows Server 2008 with IIS7, customErrors is not working.

We have customErrors set to RemoteOnly in the web.config on our Asp.Net sites and applications. However, no matter what we do, it would appear that our sites act like it's set to On and we can't get any detailed messages showing up on our applications when remoted into our servers.

I'm not entirely sure how to trace where this is being overrided, or if there is something in the way the server is configured that would make the server think the request is internal? How does this actually resolve correctly, anyway?

Any help is appreciated...

Our network admin has added domains to our hosts file to direct applications to the IP address.

Not sure if this is the right place for this question (Perhaps SuperUser), but I'm sure there are some Access gurus here on ServerFault.

Anyway, we support some legacy MS Access apps and recently a user was able to change some information in our database. NOT GOOD! It should be read only.

MS Access is using a Trusted Connection and the user is part of a Windows Group in SQL Server that is only a DB Reader.

Is there a list of Gotchas when implementing Windows Users on SQL Server that we've missed?

The only clue that we had is that we only allow connections on a non-standard port.

Does the iPhone's Active Sync Rely on IMAP Support? (Currently, I have it blocked) Is support better in Exchange 2007 or Exchange 2010?

What are the minimum requirements to set up an Exchange Server to play well with iPhones?

I haven't seen any questions specifically addressing this specific issue.

When URL Routing is used, The Request goes into IIS and then is routed to the Aspx Page. For example, a site: www.site.com/products may route the request to wwwroot/inetpub/mysite/pages/productsPage.aspx

It's important to note that the page is ROUTED, not ReDirected.

Note that to get the URLs to work properly in IIS 6, a Wildcard extension has to be set up which routes all resources to Asp.Net (Asp.Net will then hand static resources back over) This is documented here: http://blog.codeville.net/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/

It would appear that IIS doesn't GZip the content when it sends it back. I have followed the instructions here: http://www.kavinda.net/2007/02/17/how-to-enable-http-compression-iis6.html

to enable IIS 6 compression.

Any idea why Http Compression doesn't seem to work? It seems to work fine on other sites on my server. Just the one with URL Routing isn't working

I have an error message getting returned to me from a website which would appear to be something wrong with the Server side. However, this server works for all other sites on the box. Is there a possibility that I (Developer) am doing something wrong? I have no idea where to to start to track this down on the server and my sysadmin says everything appears normal:

The following recipient(s) cannot be reached:
  Customer Service Account on 6/3/2009 11:00 AM
         There was a SMTP communication problem with the
recipient's email server.  Please
contact your system administrator.
<fgdc.myservername.net #5.5.0 smtp;550 Requested action not taken: mailbox unavailable>

Server is 2003, 64-bit and running Exchange 2003

Site is Asp.Net C#, using URL Routing

Where would I start to troubleshoot this?

UPDATE

As it turns out, my system administrator traced the problem down to a layer of Spam protection. Turns out MIMESweeper may be throwing the message away, as it sees the message from our web server farm trying to send an email out with an internal address. We tested external addresses (gmail, hotmail, etc) and it worked Fine.

Thanks for all the answers. As it turns out, the best answer was "Talk to your System Admin" from my perspective... but I thought I'd update the question for anyone out there with something similar.