can't logon with windows 98

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently a Windows 98 box stopped being able to logon to any terminal
servers. It can logon to servers that are set to remote management mode, but
not any servers that are in application mode. It had been working for years
until now.

Terminal service clients have been uninstalled and reinstalled. The license
key has been deleted from the registry. Pings are returned from name and IP.
The telnet test works. What's left?

It errors out with "Terminal Server is too busy, too many connections, or
bad network." Any advice would be greatly appreciated!
 
Check the EventLog on your Terminal Server. This is most likely a
licensing issue. If you get that confirmed by the EventLog, check
your TS Licensing Manager to see the status of your licensing and if
you have any free TS CALs available.

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

"=?Utf-8?B?ZGFtb24gai4gZHVlaHJpbmc=?=" <damon j.
(e-mail address removed)> wrote on 01 feb 2005 in
microsoft.public.win2000.termserv.clients:
 
Thank you for your reply. There are no licensing-related errors in the event
logs. Also, there are plenty of free TS CALs available. This is why I deleted
the license setting from the client's registry, thinking that maybe it had
somehow become corrupt. I'm stumped...

Some additional info: Windows 98 client accessing Windows 2000 SP4 Terminal
Server through a Windows 2000 RAS over a PPTP VPN connection. The tunnel is
created just fine, and as I stated earlier, I can access other servers that
are set to Remote Administration via RDP.

Thank you for any advice.

damon
 
First of all: I've pasted your original post at the end of this
message. Why leave it out, it contains crucial information!

Since the client can logon to all servers in RA mode, and to none
in AS mode, I am not yet willing to give up the idea that this is
somehow related to licensing.
About the only thing that seems to be left is a black hole router,
which drops packets above a certain size. A full TS CAL could be
such a packet. If that's the case, you have to change the MTU size.

Check the TS FAQ at
http://www.microsoft.com/windowsserver2003/community/centers/termin
al/terminal_faq.mspx
There are 2 Q&As about this under "Connectivity".

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

"=?Utf-8?B?ZGFtb24gai4gZHVlaHJpbmc=?=" <damon j.
(e-mail address removed)> wrote on 07 feb 2005 in
microsoft.public.win2000.termserv.clients:
 
Vera, thank you for your help. It was a black hole router. I've temporarily
reduced the MTU of the host until the router can be properly configured.

Again, thanks!

damon
 
Back
Top