Can you provide a simplified version of your app + .config files? Setting impersonate=true is okay unless you want anonymous access from the client to the server.
> -----Original Message----- > From: JC Oberholzer [mailto:[EMAIL PROTECTED] > Sent: Thursday, 24 July 2003 6:49 PM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Remoting on the new Framework > > > Hi All > > I'm strugling to get my 1.0 remoting apps running on 1.1 > Current implementation is on Windows XP and 2000 with 1.0, > hosting the objects in IIS with HTTP as transport. I now > need to move to 2003 Server, still hosting in IIS. The > problems I'm experiencing most probably has to do with the > more secure approach of 2003, and I need help sorting them out. > > So, what errors do I get: Well, I can't even do the basics. > I create my virtual dir in IIS and point to the dir with > web.confg, but the client app throws and exception "The > operation required the securityexception" > > So, to get past this, I set the impersonate=true in > Machine.config (?not a good option? What should I rather do?) > > It then gets past this, but get the following error > "The underlying connection was closed : unable to connect to > the remote server". Now, this happens after > HttpWebRequest.GetRequestStream and then > HttpWebRequest.CheckFinalStatus. So, it gets a connection to > IIS, but some security setting hijacks it? > > MSDN is of little help, so to all the Gurus: Please help > > Thx > > JC Oberholzer >
