Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (
More info?)
I just did the test on an XP SP1 machine with the Windows 2003 TS Client
installed from url
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
but that's not working.
Here the Windows 2003 TS Client:
29/08/2002 10:40 388.608 mstsc.exe
29/08/2002 10:40 598.016 mstscax.dll
Here the Windows XP SP2 (beta) TS Client:
12/03/2004 00:44 407.552 mstsc.exe
12/03/2004 00:44 655.360 mstscax.dll
The TS Client Windows XP SP2 Works fine. The Windows 2003 TS Client not. A
manual copy of the SP2 (Beta) files to an XP SP1 system results in a working
TS Client through WebSSL on port 3389 - that's the temporary workaround I'll
go for.
I hope the XP SP2 will be out soon.
Regards,
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns94E0EB39AA4D9veranoesthemutforsse@207.46.248.16...
> I believe you
As a side-note, the W2K TS CALs *can* be
> upgraded if you have Software Assurance. You can also get a free
> 2003 TS CAL for every XP Pro desktop that you owned before 24
> April 2003. Check details here:
>
> Terminal Server CAL Transition Plan FAQ
>
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/tsca
> ltransfaq.mspx
>
> I haven't run the beta SP2 version of mstsc, but that might not
> be needed.
> XP SP1 includes mstsc version 5.1.2600. To connect to a 2003 TS
> (and every other TS as well), it is recommended to run the mstsc
> version 5.2.3790, downloadable here:
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-
> 4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
>
http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "Naldo" <donald.neyt@skynet.be> wrote in
> news:ej0o2CtMEHA.684@TK2MSFTNGP09.phx.gbl:
>
> > Thanks Vera for your reply.
> >
> > The licensing server is on a Windows 2003 Server with the new
> > absolutely necessary Windows 2003 CALs for TS (Believe it or not
> > but the Windows 2000 CALs could not be upgraded). The Eventlog
> > isn't telling anything.
> >
> > For your information. With the XP SP2 Technical Preview
> > MSTSC.EXE it works fine just like in Windows 98, Linux.
> > (http://www.microsoft.com/technet/prodtechnol/winxppro/sp2previe
> w
> > .mspx)
> >
> > Do you know what's the difference is between the version of
> > MSTSC.EXE which comes with XP SP1 and XP SP2 ? The
> > documentation that comes with SP2 Beta isn't telling much.
> >
> > Regards,
> > Naldo.
> >
> >
> >
> > "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> > in message
> > news:Xns94DEEB64AF1C3veranoesthemutforsse@207.46.248.16...
> >> This error can appear if you had a temporary license and the
> >> 90 days has expired. It can appear if you do not have a
> >> TS License server in your domain or the TS License server is
> >> older than the TS Server (Windows 2003 TS and Windows 2000
> >> License Server). Check the EventLog on your TS.
> >> On which OS is your TS Licensing Server running?
> >>
> >> --
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >>
http://hem.fyristorg.com/vera/IT
> >> --- please respond in newsgroup, NOT by private email ---
> >>
> >> "Donald Neyt" <donald.neyt@skynet.be> wrote in
> >> news:uZxM7FRMEHA.140@TK2MSFTNGP09.phx.gbl:
> >>
> >> > I tried to delete the local license from the WinXP Pro
> >> > client. After that I got a protocol error message. Is more
> >> > than port 3389 required ?
> >> >
> >> > We have sufficient licenses on the TS 2003 as on the TS 2000
> >> > machines.
> >> >
> >> > Regards,
> >> > Naldo.
> >> >
> >> > "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
> >> > wrote in message
> >> > news:Xns94DCD5D0E4923veranoesthemutforsse@207.46.248.16...
> >> >> Which EventIDs do you get in the EventLog on the Terminal
> >> >> Server when the XP Pro client tries to connect?
> >> >> Have you tried to delete the local license from the client,
> >> >> and then connect again (twice; on first connection the
> >> >> client always receives a temporary license, on second
> >> >> connection it should receive a permanent license).
> >> >> Are both the W2K and 2003 TS in the same domain? If so, I
> >> >> assume that both are pointed to a 2003 TS Licensing Server?
> >> >> Have you checked if you have free TS CALs available on the
> >> >> TS Licensing Server?
> >> >> Are the 2003 TS CALs "Per User" or "Per Device" TS CALs?
> >> >> Is the 2003 TS in the same licensing mode as the 2003 TS
> >> >> CALs?
> >> >>
> >> >> 187614 - Removing Terminal Server Licenses from an RDP
> >> >> Client
http://support.microsoft.com/?kbid=187614
> >> >>
> >> >> --
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >>
http://hem.fyristorg.com/vera/IT
> >> >> --- please respond in newsgroup, NOT by private email ---
> >> >>
> >> >> "Naldo" <donald.neyt@skynet.be> wrote in
> >> >> news:#5p4Xh6LEHA.3904@TK2MSFTNGP09.phx.gbl:
> >> >>
> >> >> > I've investigated a bit further. Also from Windows 98
> >> >> > remote desktop is correctly connecting to terminal server
> >> >> > Win2003, en Win2000. Seems like the problem is located
> >> >> > within WinXP Pro.
> >> >> >
> >> >> > Regards,
> >> >> > Naldo.
> >> >> >
> >> >> > "Naldo" <donald.neyt@skynet.be> wrote in message
> >> >> > news:ONjA%23jtLEHA.2396@TK2MSFTNGP12.phx.gbl...
> >> >> >> We're in the process of setting up a Cisco Concentrator
> >> >> >> 3005 to connect
> >> >> > from
> >> >> >> the outside world through WebSSL to our internal Terminal
> >> >> >> Servers. The
> >> >> > main
> >> >> >> purpose is to go around all VPN Tunnel and NAT related
> >> >> >> problems and avoid connecting external systems through
> >> >> >> IPSec to our internal LAN. Surfing to
> >> >> > a
> >> >> >> HTTPS URL, input the username and the token id. After
> >> >> >> that the Windows XP Pro desktop is accessible from
> >> >> >> unprepared external internet connections.
> >> >> >>
> >> >> >> No problem when connecting to internal Windows XP Pro
> >> >> >> systems via Remote Desktop.
> >> >> >>
> >> >> >> But we're having problems to connect through port 3389 to
> >> >> >> a Windows 2003 Terminal Server or Windows 2000 Terminal
> >> >> >> Server environment out of Windows XP Pro. We don't have
> >> >> >> these problems when we connect from a Linux environment
> >> >> >> with rDesktop. WinXP remote desktop stalls for a minute
> >> >> >> or
> >> >> > so
> >> >> >> and comes back with a licensing error message. rDesktop
> >> >> >> not.
> >> >> >>
> >> >> >> It feels like WinXP wants to do more than the Linux
> >> >> >> rDesktop but can't. Only port 3389 is defined in the
> >> >> >> concentrator.
> >> >> >>
> >> >> >> Anybody experienced similar problems?
> >> >> >>
> >> >> >> And why rDesktop can and WinXP Remote Desktop can't
> >> >> >> connect.
> >> >> >>
> >> >> >> Kind regards,
> >> >> >> Naldo.
Facebook
Twitter
Instagram