MonteCristo33
asked on
LimitLogin Windows 2003 Server utility: error during domain setup installation
Dear Experts,
After extensive research, I have found that neither W2K3 or W2K8 offer any facility to limit users' concurrent logins (I eat my words Novell - at least you had that sorted ages ago!). The universal recommendation is to get the LimitLogin utility.
I have started the installation, however during the second install phase, the domain setup, I systematically get this error message:
"the underlying connection was closed:unable to connect to the remote server"
This happens when the utility is trying to connect to the local IIS server (on the same machine). I have setup SSL communiaction as directed by the instructions.
Does anyone have any experience dealing with this issue?
your help is greatly appreciated.
Harvey
After extensive research, I have found that neither W2K3 or W2K8 offer any facility to limit users' concurrent logins (I eat my words Novell - at least you had that sorted ages ago!). The universal recommendation is to get the LimitLogin utility.
I have started the installation, however during the second install phase, the domain setup, I systematically get this error message:
"the underlying connection was closed:unable to connect to the remote server"
This happens when the utility is trying to connect to the local IIS server (on the same machine). I have setup SSL communiaction as directed by the instructions.
Does anyone have any experience dealing with this issue?
your help is greatly appreciated.
Harvey
ASKER
Dear pfcjoker,
Thank you for your post. I will try your suggestions. You mention step-by-step guide at the end of your message, however it is nowhere in sight. Could you be so kind as to include it again please?
Many thanks for your help.
Harvey
Thank you for your post. I will try your suggestions. You mention step-by-step guide at the end of your message, however it is nowhere in sight. Could you be so kind as to include it again please?
Many thanks for your help.
Harvey
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. We got to the point where LimitLogin is installed on the DC. We can ping the workstations from LL, however the login packets are not relayed to the DC. We will deploy teh .NET framework on the workstations, see if it helps. Any idea as what needs doing so the workstations "speak" to LL on teh DC?
Thanks
Harvey
Thanks
Harvey
Should be just the updated .NET framework - have you had a chance to update one workstation and test?
ASKER
Hi, sorry about the delay in responding. We still have a few teething problems. I will probably re-post a question as the rest applies to WIN2K3 Server rather than IIS. Thanks for your help so far.
Harvey
Harvey
ASKER
Answer helpful, but still experiencing problems.
did you also confirm the website responds (even if just with the standard IIS page) on https://127.0.0.1 - with no SSL cert errors?
Here is a step-by-step guide that may help