TSE and Windows 98

[jp]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

I have a domain with a Windows NT4 server and 3 workstations with Windows 98
SE.

I install a Windows 2000 server as a new domain controler. I install TSE on
it with 10 licences.

Everything works.

I install 4 workstations that had Windows XP PRO on it.
I could connect to Windows 2000 Terminal Services with no problem.

I install 2 workstations that had Windows 98 SE on it.
I could connect to Windows 2000 Terminal Services with no problem.

But with the 3 old Windiws 98 workstations I cannot access the terminal
services: I have the message: "Your server must be to busy... try to connect
after..."

What do I have to do to get this to work???

Thanks in advance

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Did you install and activate a W2K Terminal Server Licensing
Server?
And did you buy and install TS CAL on it?
Is there anything in the EventLog on the TS?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"JP" <JP-martin@tiscali.fr> wrote on 15 sep 2004:

> I have a domain with a Windows NT4 server and 3 workstations
> with Windows 98 SE.
>
> I install a Windows 2000 server as a new domain controler. I
> install TSE on it with 10 licences.
>
> Everything works.
>
> I install 4 workstations that had Windows XP PRO on it.
> I could connect to Windows 2000 Terminal Services with no
> problem.
>
> I install 2 workstations that had Windows 98 SE on it.
> I could connect to Windows 2000 Terminal Services with no
> problem.
>
> But with the 3 old Windiws 98 workstations I cannot access the
> terminal services: I have the message: "Your server must be to
> busy... try to connect after..."
>
> What do I have to do to get this to work???
>
> Thanks in advance

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

It is not a licence problem .

It is a onnexion problem...


"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> a écrit dans le
message de news:Xns9566A44143DB3veranoesthemutforsse@207.46.248.16...
> Did you install and activate a W2K Terminal Server Licensing
> Server?
> And did you buy and install TS CAL on it?
> Is there anything in the EventLog on the TS?
>
> --
> Vera Noest
> MCSE,CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> *----------- Please reply in newsgroup -------------*
>
> "JP" <JP-martin@tiscali.fr> wrote on 15 sep 2004:
>
> > I have a domain with a Windows NT4 server and 3 workstations
> > with Windows 98 SE.
> >
> > I install a Windows 2000 server as a new domain controler. I
> > install TSE on it with 10 licences.
> >
> > Everything works.
> >
> > I install 4 workstations that had Windows XP PRO on it.
> > I could connect to Windows 2000 Terminal Services with no
> > problem.
> >
> > I install 2 workstations that had Windows 98 SE on it.
> > I could connect to Windows 2000 Terminal Services with no
> > problem.
> >
> > But with the 3 old Windiws 98 workstations I cannot access the
> > terminal services: I have the message: "Your server must be to
> > busy... try to connect after..."
> >
> > What do I have to do to get this to work???
> >
> > Thanks in advance

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

License problems are the most common cause of connection
problems......

But if you repost and answer "yes" to my questions about the TS LS
and the TS CALs, and what the EventLog shows, we can dig deeper
into the problem.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"Cible98" <~cible98@tiscali.fr> wrote on 17 sep 2004:

> It is not a licence problem .
>
> It is a onnexion problem...
>
>
> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> a
> écrit dans le message de
> news:Xns9566A44143DB3veranoesthemutforsse@207.46.248.16...
>> Did you install and activate a W2K Terminal Server Licensing
>> Server?
>> And did you buy and install TS CAL on it?
>> Is there anything in the EventLog on the TS?
>>
>> --
>> Vera Noest
>> MCSE,CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> *----------- Please reply in newsgroup -------------*
>>
>> "JP" <JP-martin@tiscali.fr> wrote on 15 sep 2004:
>>
>> > I have a domain with a Windows NT4 server and 3 workstations
>> > with Windows 98 SE.
>> >
>> > I install a Windows 2000 server as a new domain controler. I
>> > install TSE on it with 10 licences.
>> >
>> > Everything works.
>> >
>> > I install 4 workstations that had Windows XP PRO on it.
>> > I could connect to Windows 2000 Terminal Services with no
>> > problem.
>> >
>> > I install 2 workstations that had Windows 98 SE on it.
>> > I could connect to Windows 2000 Terminal Services with no
>> > problem.
>> >
>> > But with the 3 old Windiws 98 workstations I cannot access
>> > the terminal services: I have the message: "Your server must
>> > be to busy... try to connect after..."
>> >
>> > What do I have to do to get this to work???
>> >
>> > Thanks in advance