I can only connect to my Windows 2003 Terminal Server with an Administative
User when connecting from the local network, I am pretty sure users could
connect before as some apps are ONLY installed on the TS so they connect to
them internally from there occasionally.
I have checked externally by logging in from my home machine over VPN with a
standard user and it works fine.
I have recently done some re-configuration of Group Policy and I have to
wonder if this is what is stopping users loggin on locally.
This isn't a huge problem as we usually only use the Terminal Server for
Remote Access anyway, but I tend to troubleshoot problems by connecting as
the user, and now I cannot do this unless I connect to my home pc via
logmein then create vpn there back into network and log on as the user,
which works!!!
Hope someone can point me in the direction of what I may have done wrong in
Group Policy and/or other possibilities
Did you get any error message when you try to login a s normal user? I assume
the TS is configured in Application mode? Did you have enough client access
licenses from MS?
Best regards
Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
> Hi,
>
> I can only connect to my Windows 2003 Terminal Server with an
> Administative User when connecting from the local network, I am pretty
> sure users could connect before as some apps are ONLY installed on the
> TS so they connect to them internally from there occasionally.
>
> I have checked externally by logging in from my home machine over VPN
> with a standard user and it works fine.
>
> I have recently done some re-configuration of Group Policy and I have
> to wonder if this is what is stopping users loggin on locally.
>
> This isn't a huge problem as we usually only use the Terminal Server
> for Remote Access anyway, but I tend to troubleshoot problems by
> connecting as the user, and now I cannot do this unless I connect to
> my home pc via logmein then create vpn there back into network and log
> on as the user, which works!!!
>
> Hope someone can point me in the direction of what I may have done
> wrong in Group Policy and/or other possibilities
>
> Cheers
>
> Sean
>
"Meinolf Weber (Myweb)" <meiweb@gmx.de> wrote in message
news:ff16fb664bac78c9ae2a94251afa@msnews.microsoft.com...
> Hello Sean,
>
> Did you get any error message when you try to login a s normal user? I
> assume the TS is configured in Application mode? Did you have enough
> client access licenses from MS?
Hi MyWeb
When a standard user tries to logon and I am connected to the console via
remote desktops snap-in they get this message.
"The user DOMAIN\administrator is currently logged on to this computer. Only
the current user or an administrator can log on to this machine."
When I log off the console via Remote Desktops snap-in they get this
message.
"To log on to this remote console session, you must have administrative
permissions on this computer."
I'm currently connected via logmein/VPN/RD as a standard user and ale to
work as normal from my home laptop, here in the office though it's no go.
Re: CAN'T Connect to Terminal Server from local Network, CAN Connectvia VPN Externally, What have I done?
Howdie!
Sean schrieb:
> When a standard user tries to logon and I am connected to the console via
> remote desktops snap-in they get this message.
>
> "The user DOMAIN\administrator is currently logged on to this computer. Only
> the current user or an administrator can log on to this machine."
>
> When I log off the console via Remote Desktops snap-in they get this
> message.
>
> "To log on to this remote console session, you must have administrative
> permissions on this computer."
>
> I'm currently connected via logmein/VPN/RD as a standard user and ale to
> work as normal from my home laptop, here in the office though it's no go.
Try Start->Run-> "mstsc" (Remote Desktop Client without /console
parameter). Does that work as normal user?
cheers,
Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Did you test it with revert the policy settings you did and is it working
then?
Best regards
Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
> "Meinolf Weber (Myweb)" <meiweb@gmx.de> wrote in message
> news:ff16fb664bac78c9ae2a94251afa@msnews.microsoft.com...
>
>> Hello Sean,
>>
>> Did you get any error message when you try to login a s normal user?
>> I assume the TS is configured in Application mode? Did you have
>> enough client access licenses from MS?
>>
> Hi MyWeb
>
> When a standard user tries to logon and I am connected to the console
> via remote desktops snap-in they get this message.
>
> "The user DOMAIN\administrator is currently logged on to this
> computer. Only the current user or an administrator can log on to this
> machine."
>
> When I log off the console via Remote Desktops snap-in they get this
> message.
>
> "To log on to this remote console session, you must have
> administrative permissions on this computer."
>
> I'm currently connected via logmein/VPN/RD as a standard user and ale
> to work as normal from my home laptop, here in the office though it's
> no go.
>
> Cheers
>
> Sean
>
"Meinolf Weber (Myweb)" <meiweb@gmx.de> wrote in message
news:ff16fb664bb038c9ae335b744b0a@msnews.microsoft.com...
> Hello Sean,
>
> Did you test it with revert the policy settings you did and is it working
> then?
>
> Best regards
>
> Meinolf Weber (Myweb)
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
I checked what I actually set in Group Policy and I 'think'it is unrelated,
the only policies set are
Windows Components/Terminal Services
Remove Disconnect option from Shut Down dialog - Enabled
Restrict Terminal Services users to a single remote session - Enabled
Windows Components/Terminal Services/Sessions
Set time limit for disconnected sessions - Enabled
End a disconnected session - 3 hours
That's the only GPO in the OU that our TS Server sits in and inheritance is
blocked.
"Florian Frommherz [MVP]" <florian@PLEASELEAVETHISOUT.frickelsoft.net> wrote
in message news:OiKmspA4HHA.3400@TK2MSFTNGP03.phx.gbl...
> Howdie!
>
> Try Start->Run-> "mstsc" (Remote Desktop Client without /console
> parameter). Does that work as normal user?
>
> cheers,
>
> Florian
RE: CAN'T Connect to Terminal Server from local Network, CAN Connect v
hi,
check if the normal users have the rights to "allow logon throught terminal
services" on local policies of terminal server and on GPO's applied to
terminal server.
also on terminal services configuration on rdp-tcp properties on permissions
tab regular users have the proper rights.
--
Dragos CAMARA
MCSA Windows 2003 server
"Sean" wrote:
> Hi,
>
> I can only connect to my Windows 2003 Terminal Server with an Administative
> User when connecting from the local network, I am pretty sure users could
> connect before as some apps are ONLY installed on the TS so they connect to
> them internally from there occasionally.
>
> I have checked externally by logging in from my home machine over VPN with a
> standard user and it works fine.
>
> I have recently done some re-configuration of Group Policy and I have to
> wonder if this is what is stopping users loggin on locally.
>
> This isn't a huge problem as we usually only use the Terminal Server for
> Remote Access anyway, but I tend to troubleshoot problems by connecting as
> the user, and now I cannot do this unless I connect to my home pc via
> logmein then create vpn there back into network and log on as the user,
> which works!!!
>
> Hope someone can point me in the direction of what I may have done wrong in
> Group Policy and/or other possibilities
>
> Cheers
>
> Sean
>
>
>
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.