IIS 5.1 help?
I have installed IIS 5. 1 and set it up to use d:\webserver as webserver directory. I made a testpage. html and it worked but when I changed the extension to. asp I got an 500 internal server error. Whats up with that? I thought IIS 5.
I have installed IIS 5.1 and set it up to use d:\webserver as webserver directory. I made a testpage.html and it worked but when I changed the extension to .asp I got an 500 internal server error. Whats up with that? I thought IIS 5.1 would be able to run asp pages?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
erm....
Quote: I'm going for apache. I'm going for apache.
I dont think that makes a differences as far as TCP/IP connections goes. You are limited to ten still, are you not?
Quote: I'm going for apache. I'm going for apache.
I dont think that makes a differences as far as TCP/IP connections goes. You are limited to ten still, are you not?
I realise I could be misunderstanding you guys here, but are you saying that Windows itself won't allow more than 10 connections? Is this a feature of just web serving, or any connections? If it's any, then I'm afraid someone'e been giving out wrong information as I know that you can run an FTP server & have someone else connect to it with an FTP prog [eg FlashFXP], & then start a download going with Mass Downloader which makes 10 connections @ the same time, & have someone else connected as well with another FTP prog [either FlashFXP or similar], which makes a total of 12 connections by my reckoning.
I apologise in advance if I've got the wrong end of the stick.
I apologise in advance if I've got the wrong end of the stick.
The restriction is not in IIS
Last summer where I was working, co-workers were developing a java migrating agent program. And one of the problems that they ran into was the TCP/IP connections for a MS Pro package was limited to 10 users.
Last summer where I was working, co-workers were developing a java migrating agent program. And one of the problems that they ran into was the TCP/IP connections for a MS Pro package was limited to 10 users.
Quote:
I realise I could be misunderstanding you guys here, but are you saying that Windows itself won't allow more than 10 connections? Is this a feature of just web serving, or any connections? If it's any, then I'm afraid someone'e been giving out wrong information as I know that you can run an FTP server & have someone else connect to it with an FTP prog [eg FlashFXP], & then start a download going with Mass Downloader which makes 10 connections @ the same time, & have someone else connected as well with another FTP prog [either FlashFXP or similar], which makes a total of 12 connections by my reckoning.
I apologise in advance if I've got the wrong end of the stick.
No, the workstation versions of all NT OSs are limited to 10 connections using the default MS applications (like IIS) and network resources (such as file and print sharing). Whether or not there have been some applications trying to get around it, I don't know. Now, having multiple connections per user is another thing, and that sounds like what you are getting at Alien. It sounds like you might have had 12 connections, but you had 2 concurrent user connections to those resources. That might be why you were getting confused.
I realise I could be misunderstanding you guys here, but are you saying that Windows itself won't allow more than 10 connections? Is this a feature of just web serving, or any connections? If it's any, then I'm afraid someone'e been giving out wrong information as I know that you can run an FTP server & have someone else connect to it with an FTP prog [eg FlashFXP], & then start a download going with Mass Downloader which makes 10 connections @ the same time, & have someone else connected as well with another FTP prog [either FlashFXP or similar], which makes a total of 12 connections by my reckoning.
I apologise in advance if I've got the wrong end of the stick.
No, the workstation versions of all NT OSs are limited to 10 connections using the default MS applications (like IIS) and network resources (such as file and print sharing). Whether or not there have been some applications trying to get around it, I don't know. Now, having multiple connections per user is another thing, and that sounds like what you are getting at Alien. It sounds like you might have had 12 connections, but you had 2 concurrent user connections to those resources. That might be why you were getting confused.