Gillus
Members-
Content count
11 -
Joined
-
Last visited
Never
Community Reputation
0 NeutralAbout Gillus
-
Rank
stranger
-
Well, I've spent some hours looking for something like that, but failed for now. I'm affraid this tweak will be a little tricky. Hacking around the registry won't be enough. I imported entire pieces of registry and components from Win2K server in my XP box, but it doesn't work I even tried to install Citr!x Metaframe XP and use ICA instead of RDP. failed as well. Looks like XP is kernely limited to only one active session at the same time. Any ideas are welcome. GS
-
Hmmm, sorry. You don't have native solution to remotely control a Win2K PRO box. Terminal Services aren't available on this version. You'll have to look at freeware tools. I'd suggest VNC, which is pretty powerful and completly free. BUT, don't forget there is no separation layer between the kernel and the GUI in Win2K PRO, thus remotely controlling the box will make all your actions "showing" on the console desktop, forbiding any user to use the computer at the same time. It's one of the most annoying limitation of this OS, and one that decided me to go to XP. However, XP in still not a multi-user OS, so establishing a remote connection on a XP box will temporarily desactivate any session of any local user (if allowed). I'm not sure how MS implemented this limitation, since Terminal services are part of XP, but I'm still "working" to find a fix for that. Gillus
-
Yes you can. The best terminal server client, IMHO, is the one that's on the XP CD. You can get it there : http://www.xs4all.nl/~binkbv/msrdpcli.zip Don't forget to give a password to the account you plan to use for logon, otherwise access will be denied. If you really want to open remote desktop access to accounts without passwords, you'll have to tweak the security policy Gillus
-
At last ! After spending some more time trying to fix the problem, I finaly found the solution. It was not a remote desktop client problem. It was a security policy issue ! But not the one you find easyly : Remote desktop is only allowed for accounts that have a password. That's all. I was just trying to connect with an logon that doesn't have one. Gillus
-
Well, unfortunatly the issue is not due to the terminal client. I tried various ones. It's not due to security policy of XP as well. I just wanted to know if someone here has ever managed to successfully connect to an XP Pro box *remotely* with a *non-administrator* account ? Gillus
-
Hmmm folks, it seems I have a clue. I forgot to mention that my remote terminal was running Win2K, *not* XP. I just read there is a limitation in the XP remote desktop client that doesn't allow non xp computer to connect to xp server... Can anyone confirm this ? Gillus
-
First, sorry for the cross-post. I just need some time to learn how this forum works. Second, I would like to give some clarification regarding the issue. I'm not talking about XP not allowing multiple sessions at the same time. I'm talking about XP not allowing *remote* connection from non admin group members. If joe is not admin, but is in the remote users group, he won't be allowed to remotly logon, even is he's already connected on the console, or even if nobody is currently connected on the console. Meanwhile, administrator is able to remotly logon, in any case, closing any console session (which is a normal behavior for a non multti-user OS). So I really don't understand why microsoft created that remote users group, and why microsoft claims that you are able to remotly connect to your desktop PC at work from home ? Why limiting such feature to the admin group ? Gillus
-
Hi, I'm currently testing Windows XP Professional, and this OS seems to be great. However, I didn't find how to authorize non-administrator users to remotely connect to the XP server using Terminal services & RDP. When creating the account, I add it to the remote users group, but this doesn't seems to work. I tried several tweaks, including modifying the security policy, but I still have the same error message after logon : "There are accounts limitation" I'm using XP Pro and XP remote desktop client. Please help ! Gillus
-
Hi, I'm currently testing Windows XP Professional, and this OS seems to be great. However, I didn't find how to authorize non-administrator users to remotely connect to the XP server using Terminal services & RDP. When creating the account, I add it to the remote users group, but this doesn't seems to work. I tried several tweaks, including modifying the security policy, but I still have the same error message after logon : "There are accounts limitation" I'm using XP Pro and XP remote desktop client. Please help ! Gillus
-
Hi, I'm currently testing Windows XP Professional, and this OS seems to be great. However, I didn't find how to authorize non-administrator users to remotely connect to the XP server using Terminal services & RDP. When creating the account, I add it to the remote users group, but this doesn't seems to work. I tried several tweaks, including modifying the security policy, but I still have the same error message after logon : "There are accounts limitation" I'm using XP Pro and XP remote desktop client. Please help ! Gillus
-
Hi, I'm currently testing Windows XP Professional, and this OS seems to be great. However, I didn't find how to authorize non-administrator users to remotely connect to the XP server using Terminal services & RDP. When creating the account, I add it to the remote users group, but this doesn't seems to work. I tried several tweaks, including modifying the security policy, but I still have the same error message after logon : "There are accounts limitation" I'm using XP Pro and XP remote desktop client. Please help ! Gillus