Running DNN 4.4.1. Dev server is XP Pro. Prod Server is 2k3. Sql Server 2005

I wrote a module that allows a user to select a type of pdf to view. My function that shows the report, calls another web app that I have on a file server, and that app then stream the pdf to the client's browser.

When I try to retrieve the pdf, on my dev machine I always get prompted for the domain userid/pswd. But on the prod server, it just bombs out.

I have made edits to web.config like so:

<identity impersonate="true" userName="mydomain\myusername" password="mypswd"/>

have also tried uncommenting 
<trust level="Medium" originUrl=".*" />
 
Nothing works so far. I only get:
 
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

Parser Error Message: Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'Logon failure: unknown user name or bad password.
'

Source Error: 

Line 99: 		<!-- permits errors to be displayed for remote clients -->
Line 100:		<customErrors mode="Off"/>
Line 101:    <identity impersonate="true" userName="domain\userID" password="pswd"/>
Line 102:		<!-- Forms or Windows authentication -->
Line 103:		<authentication mode="Forms">



Source File: C:\Statements_DNN\web.config    Line: 101  

 
Any suggestions please?

Actually Mitchell it looks like he's doing it correctly. Without impersonation it's going to attempt to contact the file server using the local production server's ASPNET user credentials (which won't work).

Tigris, I suspect it's something in your network setup. If you logged into the server locally (using the local Administrator account) and tried to connect to the share/app on the production server does it work when you supply it with the username/password in your web.config? We ran into something similar on an internal module that I wrote that allows our students to access a network share. We had to talk to our head networking guy to get him to "poke" a hole that would allow web traffic through to the file server otherwise we'd get errors like crazy. It works from your dev machine because it's not restricted from seeing/access the file server.

I don't know how to respond. I have tried everything I could think of. Commented/uncommented the lines in the web.config I mentioned earlier, added permissions to the folder that contains the web app on the fileserver. ...

Should I try to experiment ing with the authentication section? I am at my wits end here.

Also, once I uploade to the web server, when the app bombs out, it tries to load http://myDevMachineIP/client/error.aspx into the browser instead of http://myDomainName/client/error.aspx . Why is it stuck on sending the client back to my dev machine IP?