PC Review
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Clients
Re: Client Can Not Connect ToTS
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Clients
Re: Client Can Not Connect ToTS
![]() |
Re: Client Can Not Connect ToTS |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
The EventLog?
Can the client ping the TS? -- Vera Noest MCSE, CCEA, MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please answer in newsgroup --- "Charlie Hill" <InterstateIT@IWantToKnow.com> wrote in news:0afc01c344b7$0d8dda10$a001280a@phx.gbl: > > A Windows 98 workstation gets the following error message > when it attempts to connect to a TS server. "Client Can > Not Connect To The Terminal Server. The server may be too > busy. Please try connecting later." It does not matter > which client is used, both the RDP 5.1, and TSAC client > reports this same error. > > The server is not too busy. There are no limit to the > number of connections. There has been only 5-7 other users > connected when this error is reported. There are still 12 > TS licenses available for issue. > > Do not know what to check next. |
|
|
|
#2 |
|
Guest
Posts: n/a
|
Yes, the client can ping the TS server. >-----Original Message----- >The EventLog? >Can the client ping the TS? > > -- >Vera Noest >MCSE, CCEA, MVP - Terminal Server >http://hem.fyristorg.com/vera/IT > --- please answer in newsgroup --- > >"Charlie Hill" <InterstateIT@IWantToKnow.com> wrote in >news:0afc01c344b7$0d8dda10$a001280a@phx.gbl: > >> >> A Windows 98 workstation gets the following error message >> when it attempts to connect to a TS server. "Client Can >> Not Connect To The Terminal Server. The server may be too >> busy. Please try connecting later." It does not matter >> which client is used, both the RDP 5.1, and TSAC client >> reports this same error. >> >> The server is not too busy. There are no limit to the >> number of connections. There has been only 5-7 other users >> connected when this error is reported. There are still 12 >> TS licenses available for issue. >> >> Do not know what to check next. >. > |
|
|
|
#3 |
|
Guest
Posts: n/a
|
How about the EventLog? This problem sounds like a license
problem. If so, the EventLog should tell you load and clear. -- Vera Noest MCSE, CCEA, MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please answer in newsgroup --- "Charlie Hill" <InterstateIT@IWantToKnow.com> wrote in news:7b3001c344bc$ce977a40$a401280a@phx.gbl: > > Yes, the client can ping the TS server. > > >>-----Original Message----- >>The EventLog? >>Can the client ping the TS? >> >>Vera Noest >> >>"Charlie Hill" <InterstateIT@IWantToKnow.com> wrote in >>news:0afc01c344b7$0d8dda10$a001280a@phx.gbl: >> >>> >>> A Windows 98 workstation gets the following error > message >>> when it attempts to connect to a TS server. "Client > Can >>> Not Connect To The Terminal Server. The server may be > too >>> busy. Please try connecting later." It does not matter >>> which client is used, both the RDP 5.1, and TSAC client >>> reports this same error. >>> >>> The server is not too busy. There are no limit to the >>> number of connections. There has been only 5-7 other > users >>> connected when this error is reported. There are still > 12 >>> TS licenses available for issue. >>> >>> Do not know what to check next. |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

