Works on localhost, but not when uploaded?

Alright,

I'm currently making a website in ASP.net 2.0.  I've gotten to the point where I
need to upload it to a server (I'm gonna use Windows Authentication later on, so
I've decided to try and get started on learning that).  Everything so far works
fine and dandy on my localhost from the Visual Studio 2005 build, but when I get
it on the server, I get some errors.

Basically, it brings up the typical Debug/Error screen, with the title of
"Server Error in '/' Application" and "Runtime Error".  From
there, it just tells me to make an error page and set it using web.config.  I
did end up making the error page, and it works, but not when it should - no
matter what page I go to, I get the error page, even on one that just has an 
HTML iframe.

At first I thought that the server may not have the ASP.net 2.0 runtime
installed, but the server's admin assures me that he has.  I checked that out,
and there's a folder in the wwwroot entitled "aspnet_client" with a
series of subfolders that eventually get to 2_0_50702, so it appears as though
it is installed.  

I've never actually hosted any .net 2.0 on a server, but I do know a bit about
it...  I figure that it might be a problem with how IIS is configured, but I
have no idea if that's true or not.  If you guys have any ideas as to what might
be causing this problem, I'd love to hear them.  =D

Thank you very much.

What server version is this on?

Just because ASP.NET 2.0 is installed it doesn't mean your application or site
is configured to use it.  If you have access to the IIS console, check the
ASP.NET tab.  (IIS 6).

Jeff

Unfortunatly, I don't have access to the IIS, and for all I know, this server is
on Mars.  I'll throw an e-mail in the direction of the admin, asking him if it's
enabled in IIS console's ASP.NET tab.  >_>

... well that's some key info if you want us to help you.

If this is running on Windows 2000, I've seen this error when the local ASPNET
account does not have NTFS permissions to the content.  That's something your
IIS admin would have to fix for you ...