2008/11/24 Brandon Betances <[EMAIL PROTECTED]>: > now, I set the AppPool to NetworkService, and all Impersonation and Anon > Authentication to the Identity Pool, it works again. > > Baffling, really. > > On Mon, Nov 24, 2008 at 2:38 PM, BBetances <[EMAIL PROTECTED]> wrote: >> >> I can't stand this anymore. Here's my problem: >> >> IIS starts wonderfully, everything works, the sites work, I can >> connect through VS2008. This is a development server, BTW. When I >> leave VS running idle for a few minutes, usually 10, i'm guessing it >> times out, and I know this because my DNS query doesnt go through. My >> domain is home.net, so when I navigate to www.home.net, instead of >> seeing my page, I see the Internet implementation (a stupid real >> estate link site, check it out). I changed the binding to dc.home.net, >> the name of the server im on, and get a 404. >> >> The real problem here, is that the issue is consistent, but the >> resolution is not. Sometimes, I recycle the app pool, and it works. >> Sometimes I have to change the identity of the app pool, and that >> works. Most of the time, its the anonymous connection settings that >> need to be changed, and sometimes, its the ASP Impersonation that is >> the problem. My issue with these resolutions is that I use my Admin >> identity to connect to everything. No pass-through, no identity pool, >> and if I did use the app identity, it would still be administrative. I >> have full permissions on all drives and paths, so I should'nt be >> getting this problem. But it's very perplexing. >> >> Any ideas? >
This has almost nothing to do with IIS, and everything to do with DNS. Perhaps a little reading is in order
