-
Posted to
IIS7 - Known Issues and Workarounds
by
espresso
on
03-23-2009, 12:10 AM
Ok then what DO you use? I had to put in response.Close or else I kept getting a timeout error right after request.GetRequestStream() in my code during a bunch of bulk API calls..one right after the other. On the first two API calls I made, they were fine. It was always on that 3rd API call I got a timeout error until I put ...
-
Posted to
IIS7 - Known Issues and Workarounds
by
espresso
on
03-23-2009, 12:08 AM
Ok, then what DO you use? Recently I was getting timeout errors when making a bunch of API calls one right after the other. Until I put in response.Close() I was getting that timeout error after only the 3rd SOAP API call.
-
Posted to
IIS 7 - ASP.NET Administration
by
espresso
on
03-20-2009, 12:19 AM
so is that: telnet serverip 80 ?
-
Posted to
IIS 7 - ASP.NET Administration
by
espresso
on
03-15-2009, 10:06 PM
I do not think it's even working locally either. I don't get why if I set this up it's not working. I think it's pretty straight forward:
1) Create a new site in IIS 7
2) Set it to the right app pool type
3) make sure it's set to the right folder...where your web project resides
4) specify the ...
-
Posted to
IIS 7 - ASP.NET Administration
by
espresso
on
03-14-2009, 12:55 AM
I published my site, setup a site in IIS 7 on our Windows Server 2008. I setup the bindings and still I can't get to the site when putting in IP/sitename in my browser from my PC. I can ping the server from my PC just fine and both are on same network.
What magic besides specifying the app pool and just creating a site in IIS7 do ...
-
Posted to
IIS7 - Security
by
espresso
on
12-22-2008, 8:14 PM
resolved. Set PC IP as site IP in site settingssettings
-
Posted to
IIS7 - Security
by
espresso
on
12-22-2008, 12:27 PM
Ok, our dev server is on our domain. I setup a new website that points to the directory of the website I published on my server which is running Server 2008.
I can run the site locally via the following in the URL of a browser on that server:
http://localhost/
http://servername/
http://ipname/
but if I try to access it from a PC such ...
-
Posted to
General
by
espresso
on
12-22-2008, 11:50 AM
I'm running Server 2008. If an existing website is taking up port 80, how can I:
Find another valid port to run another web site on the same box . Wha'ts the rule of thumb on assigning open ports other than 80 when you need to and how do you find the open port #s?