Re: W2k TS & XP Rdp

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If there's anything else that you've already excluded, it would be
nice if you would mention that in your post.

What OS is your laptop running?
If it's not entitled to a free TS CAL from the TS Licensing Server
(the "Existing Windows 2000 TS CALs"), then you would need a
purchased TS CAL. This would apply to W2K Home, XP Home, unix,
Macintosh.
Do you have Administrative rights on your laptop? You need to be
able to write to the registry key which stores the license locally.
If you're running Vista, you need to start the rdp client with "Run
as Administrator".
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2VuYWN0?= <Kenact@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
04 aug 2007 in microsoft.public.windows.terminal_services:

Thanks, but Been there Done that.

I can get to a Remote Admin TS but not the App Mode TS.

"Vera Noest [MVP]" wrote:

There might be a black hole router between your client and the
TS, which blocks packets above a certain size. This prevents
the transfer of the permanent TS CAL to the client (on first
connection, the client gets a temporary license, on second
connection, it gets a permanent license).

If this is the problem, you have to change the MTU size. Check
the Terminal Services FAQ, there are 2 items about this under
"Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/ter
min al/terminal_faq.asp

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2VuYWN0?= <Kenact@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 03 aug 2007 in microsoft.public.windows.terminal_services:

I have a windows 2000 Terminal Server in a WinNT4 domain.
Licensing is running on the TS.

I am establishing a VPN connection from my laptop (not a
domain member) to the network using a SonicWALL TZ-170 and
the SW Global VPN client.

I can connect to another W2K server running in Remote Admin
mode, but I can't connect to the TS running in Application
Mode.
All I get in the Event Log is a 1004 "The terminal server
cannot issue a client license." event.

Once logged on to the server running Remote Admin mode, I can
log on to the Application Server.

Any clues?

Thx,
Ken
.

Relevant Pages

  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Client disconnected problem
    ... Resetting a thin client to the factory default is ... That would lead to the issueing of a new license (the ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Client on the PPC. ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Unable to access local workstations from SBS 2003
    ... domain AT the client. ... I did focus on the DNS of the server as a possible issue. ... Relative to the "..computer name is not in Win2K3" I mean that the laptop ... >> I'm able to do just about anything from the laptop or any other workstation ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW problem on one Client machine
    ... know it is occurs on a special client computer, ... |> services licensing service on a Windows 2000 domain controller. ... |> terminal license successfully. ... |> Services Licensing service on the SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)