oRox,

I'd agree with Larry. If you're going to run IIS do so on a server and save yourself the headaches.

W2K's version of IIS is v5.0 whereas NT4's is 4.0 FYI. IIS can handle a lot of web sites.


>>What are the chances of upgrading the OS to NT Server not Workstation? IIS runs a helluva lot better (IMO) than PWS and there are many more options you can test (e.g. multiple web sites attached to different IP addresses).
>
>I thought of that, and I know I really need to get onto IIS... but if I'm gonna upgrade my OS I wanna go Win2K Pro and get current and be done with it. I did go check on how current the Win2K Toshiba drivers were for my model, and they were all dated like April/May... so methinks I'll just wait a few more weeks or so until the drivers I'm gonna need get a more recent date and then take the leap.
>
>What I ended up doing is dumping M$ PWS, stripped off all my web service related software (FrontPage, ColdFusion, VI, etc) and installed Peer Web Server via NT Networking. Reapplied SP6 and reinstalled all my software fresh and batta-bing, all the problems I had with PWS were gone and I was finally able to finally get the ColdFusion Server component to load and play nicely with the other kids (just so long as I disable user security management which is fine for what I need to do on my local machine). Note - dont ask me how long it took to figure out how much crap I had to strip off just to get Peer Web Server loaded properly < smirk > man what a PITA tool this sucker is!
>
>I havent tried to reinstall Web Connect yet after all this... hopefully it'll manage to deal with Peer Web Server better than it does with PWS. As soon as I dont need ColdFusion Server readily available I'll give the WC3.5 install another shot and see if I can manage to limp along with this setup until new Win2K drivers come out for my laptop.