Concurrent web connects to my 2003 Server.
Posted on 2004-11-04
Newbie to EE here:
I've just discovered (the hard way) that 2K3 defaults to 2 concurrent web connects and only for admin credentials. (I should have known better than to allow my hardware supplier to install 2K3 before delivering the box). It's configured with dual Xeons and 2Mb RAM, so this is actually the machine that I wanted to use for a whole bunch of stuff, including Exchange Server, Printer/Fax Spooling and Remote web connects for various 'concurrent' users.
Everything seems to be going along swimmingly, except for the remote user count and credential limitations.
This box is also used as a "proper" server, with hot swap RAID1 installed (2 x 120Gb SATAs) - so the rest of the network can get to it. We've purchased 15 licenses and before even moving peoples' .pst files into the Exchange environment, I'm trying to get going with multiple remote web connections to this box to facilitate an old proprietary RPG prog (DOS-based). [pls understand, I mean one connect per user, but having several users connecting to the server at once]. For the 2 connections that I'm allowed, thus far, things are working well... I just can't get enough concurrent connects and the permissions I've had to give to the 2 on board so far, a far more than I wanted.
I understand that I might have to set up a separate box with XP Pro as a dedicated in-house remote connection client (assuming I can get past this 2-user limit with THAT machine); however, I feel I'd be wasting the resource that I just purchased.
Is there a solution to this using the server I currently have?
[if so, please tell me it doesn't involve a re-install of the server]
(I would like to avoid buying another "dedicated" box, if I can.)
The surrounding nodes are either XP Pro or W2K - both remotely (through 3DES VPN) connected to the in-house network and on the network, itself. All machines have static 10-net addresses and both LANs are routed together (successfully) with a SOHO router, allowing for h/w NAT.
I keep with static addressing because I've been using VNC for remote assistance in my pre-2K3 days.