"The local policy of this system does not
permit you to logon interactively."

I have found this issue as well, make sure the Remote user has emabled the "RDP" add-on in Internet exporer.
I encountered this after adjusting Internet Security on my home PC.
Hope it helps.

Nick Petry
SBS2003 Adminstrator from the get go.



David C wrote:

Remote login
02-Apr-09

We have SBS 2003 and have had a user connecting up with Remote Desktop for a
long time. Now, he is getting "The local policy of this system does not
permit you to logon interactively.". I can logon as administrator, but not
via the user login for some reason.
I tried the KB289289 from Microsoft, but still cannot login. This user is a
member of the remote group. Any ideas on what else I can try? Thank you.

David

Previous Posts In This Thread:

On Thursday, April 02, 2009 12:11 PM
David C wrote:

Remote login
We have SBS 2003 and have had a user connecting up with Remote Desktop for a
long time. Now, he is getting "The local policy of this system does not
permit you to logon interactively.". I can logon as administrator, but not
via the user login for some reason.
I tried the KB289289 from Microsoft, but still cannot login. This user is a
member of the remote group. Any ideas on what else I can try? Thank you.

David

On Thursday, April 02, 2009 2:06 PM
Dave Nickason [SBS MVP] wrote:

Is the RDP user attempting to connect to the SBS, or to a client PC?
Is the RDP user attempting to connect to the SBS, or to a client PC? Can he
log into the machine locally? RDP into it from within the LAN?



The first thing to check is on the machine that's rejecting the RDP logins,
CP -> System -> Remote tab. Is the user listed there? (Or a group the user
belongs to).


"David C" <dlchase@newsgroup> wrote in message
news:e1eE836sJHA.1492@newsgroup

On Thursday, April 02, 2009 2:57 PM
KimG wrote:

Hi DavidI've seen this problem a few times, and like you, I browsed around
Hi David

I've seen this problem a few times, and like you, I browsed around a
long time, to find an answer, and a solution.

here is what I found:

When connecting to a terminal server, users may sometines eperience the
following errors:
? The remote session was disconnected because the local computer?s
client access license could not be upgraded or renewed. Please contact
the server administrator.
? The remote computer disconnected the session because of an error in
the licensing protocol. Please try connecting to the remote computer
again or contact your server administrator.
? The remote session was disconnected because there were network
problems during the licensing protocol. Please try connecting to the
remote computer again.
? A licensing error occurred while the client was attempting to
connect. (Licensing timed out.) Please try connecting to the remote
computer again.
? The remote session was disconnected because there are no Terminal
Server client access licenses available for this computer. Please
contact the server administrator.
? The remote session was disconnected because there are no Terminal
Server License Servers available to provide a license. Please contact
the server administrator.
? Because of a security error, the client could not connect to the
terminal server. After making sure that you are logged on to the
network, try connecting to the server again.

In order to fix the above errors a bit of regisry fixing needs to take
place. Before making any changes to your registry,

BACK IT UP

The instuctions on how to fix the above errors are below:
1. Open the Windows Registry Editor by entering the command
regedit32.exe in the Run command box under the Start Menu.
2. Navigate to the Registry Key
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing
3. Delete the MSLicensing key and its subkeys.
4. Reboot the computer.


--
KimG
------------------------------------------------------------------------
KimG's Profile: http://forums.techarena.in/members/84545.htm
View this thread: http://forums.techarena.in/small-bus...er/1153415.htm

http://forums.techarena.in

On Thursday, April 02, 2009 6:14 PM
David C wrote:

Trying to connect to his workstation from home.
Trying to connect to his workstation from home.

Yes, the user is listed as member of remote users. He logs into the domain
so where is the controlling policy? At the PC or server? Thanks.

p.s. I think I turned all policy off

David
"Dave Nickason [SBS MVP]" <gwdibble@newsgroup> wrote in message
news:%23LErx27sJHA.5112@newsgroup

On Thursday, April 02, 2009 6:16 PM
David C wrote:

But I didn't get any of the errors you mentioned...?
But I did not get any of the errors you mentioned...?

David

On Thursday, April 02, 2009 8:30 PM
Jim Behning SBS MVP wrote:

Try to RDP log on to the workstation from inside the network first.
Try to RDP log on to the workstation from inside the network first. If
it works with that user's account and password then you could focus on
home workstation problems.

On Thu, 2 Apr 2009 17:14:21 -0500, "David C" <dlchase@newsgroup>
wrote:

See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive...A/default.aspx

On Friday, April 03, 2009 12:38 PM
Dave Nickason [SBS MVP] wrote:

Re: Remote login
Or firewall.

On Friday, April 03, 2009 4:00 PM
David C wrote:

Does it help to know that he can login remotely to his PC as administrator?
Does it help to know that he can login remotely to his PC as administrator?
Thanks.

David

EggHeadCafe - Software Developer Portal of Choice
VB.NET TCP Client - Server Socket Communications
http://www.eggheadcafe.com/tutorials...nt--serve.aspx