Why does PWS stop working?

[Sensibilium]

Hi,<br><br>I'm running PWS on a network of 4 Win98 machines, and most of the time the intranet site works fine, but sometimes the browser just keeps looking and looking and looking, but doesn't manage to load in the page even though the status bar says 'Web Site found' but eventually it turns to a little eggtimer and the word 'done', even though the mouse eggtimer is still turning.<br><br>If I turn off the web server for about 8 hours and switch it back on, the pages are served fine...<br><br>Anyone know why this may be occurring? I have MDACS installed for ASP too...<br><br>Regards<br>Ahdli Kawshus<br> <p>ahdkaw<br><a href=mailto:ahdkaw@sensibilium.com>ahdkaw@sensibilium.com</a><br><a href=

http://sensibilium.com/>Sensibilium</a><br>'If

you do visit my sites - be warned! You must be of a discordian nature...'

 

[Webrookie]

I used to use PWS, but I also found it unstable.&nbsp;&nbsp;I installed NT Option Pack 4.0 on an NT machine and used Microsoft Management Console, it is a lot better.<br><br>I would get an NT machine setup.&nbsp;&nbsp;That's the only thing I can think of.

 

[JDurbin]

I have heard the same of PWS on the 98 platform;&nbsp;&nbsp;that it is just too buggy.&nbsp;&nbsp;Although this doesn't answer your specific answer it is noteworthy to keep in mind as you may undoubtably have other problems as well <p>John Durbin<br><a href=mailto: > </a><br><a href= > </a><br>ICQ VFP ActiveList #73897253

 

[unicorn11]

Some Times PWS wll only support 2 users on the site <br><br>so as more users log onto it , it starts reling out errors<br>&nbsp; <p>Unicorn11<br><a href=mailto:webmaster@tripmedia.com>webmaster@tripmedia.com</a><br><a href= > </a><br>Hi there it all likeminded fellows!!!!!!

 

[Karl Blessing]

In my opinion PWS serves best as a single-user test platform, that lets you develope a web application and test it on your own machine without having to distribute it to the NT server, I dont think it was ever really usefull as the Main webserver itself. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href=

http://kb244.8m.com>

</a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)

 

[Sensibilium]

Well, thats all well and good telling me that it shouldn't be used as a webserver across a network, but the documentation of PWS states that it can serve to a maximum of 5 concurrent users. I only have 4 users.<br><br>I cannot buy myself the NT4 Option Pack, because that would also mean buying NT4, which my budget will not stretch to. The company I work for don't like spending thousands of pounds on something that they can see no immediate benefit from. I know this is stupid, but what the boss says I must do.<br><br>I'm gonna have to start costing up NT4 + WebServer, just to see if I can't push it through.<br><br>According to my original entry, booting the machine a day later would solve the problem, however this seems to be no longer the case. I have tried re-installing PWS without effect. So what now? Should I re-install MDACS instead?<br> <p>ahdkaw<br><a href=mailto:ahdkaw@sensibilium.com>ahdkaw@sensibilium.com</a><br><a href=

http://sensibilium.com/>Sensibilium</a><br>'If

you do visit my sites - be warned! You must be of a discordian nature...'

 

[Karl Blessing]

if you can get NT4, I'm sure you can download the NT4 Service Pack that has IIS online, I mean I was able to download PWS4 off the same site, it was just a matter if I was downloading it for NT or if i Was downloading it for Win9x. also even if you are using just 5 users, and you have 4, there would be one extra for administrative tools(I think). <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href=

http://kb244.8m.com>

</a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)

 

[NickBulka]

Something that possibly needs clarification here:<br>PWS supports 5 concurrent sessions.&nbsp;&nbsp;Now, the lifetime of a session is determined by the method of ending a session.&nbsp;&nbsp;Unless you explicitly abandon a session,&nbsp;&nbsp;that session stays active until it times out, whether the user is actually still connected to the server.&nbsp;&nbsp;For example,&nbsp;&nbsp;a user goes to the site,&nbsp;&nbsp;views a page,&nbsp;&nbsp;then goes to some other site.&nbsp;&nbsp;The IIS session will remain active until it times out, which defaults to 20 minutes, if memory serves me right.&nbsp;&nbsp;You can see that it is easy to consume these 5 sessions without anybody still actually using the site.&nbsp;&nbsp;If your site uses frames and session variables, and your session variables are not initialized in global.asa,&nbsp;&nbsp;it is possible that each frame will be a separate session (this is a documented bug in the Microsoft knowledge base). In this case, assuming three frames in a frameset, your third user will be blocked from accessing the site.<br><br>To overcome this problem,&nbsp;&nbsp;you can supply a logout page where you abandon the session,&nbsp;&nbsp;but there's no guarantee that the users will bother to log out.&nbsp;&nbsp;You can also shorten the default timeout period, so sessions become available more quickly.<br><br>The previous posts in this thread offer the best solution: go to NT (or better yet, Win2K) and use the full-blown IIS.&nbsp;&nbsp;An important thing to note here is that in order to run IIS,&nbsp;&nbsp;you MUST use NT server.&nbsp;&nbsp;If you use NT workstation, you'll find you are still limited to using PWS.<br> <p>nick bulka<br><a href=mailto: > </a><br><a href= > </a><br>