Windows NT Win98 computers cannot RDP to terminal servers

  • Thread starter Thread starter Blair
  • Start date Start date
B

Blair

Installed a second domain controller to the domain. Next day windows 98 PC's
could not initiate RDP connections with any terminal servers in our network.

Only error message is that " The connection timed out "

All other PC's can access the terminal servers only Win98 PC's seem to be
affected.

Any suggestions?
 
Which OS do you run on the DCs?
Any errors in the EventLog on the DCs or the Terminal Servers?

Check if this helps:

555038 - How to enable Windows 98/ME/NT clients to logon to Windows
2003 based Domains
http://support.microsoft.com/?kbid=555038
_________________________________________________________
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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 08
jul 2007 in microsoft.public.windows.terminal_services:

> Installed a second domain controller to the domain. Next day
> windows 98 PC's could not initiate RDP connections with any
> terminal servers in our network.
>
> Only error message is that " The connection timed out "
>
> All other PC's can access the terminal servers only Win98 PC's
> seem to be affected.
>
> Any suggestions?
 
The DC's run Windows Server 2003. The 2nd DC has since been demoted, and
removed, from the network.

There are no errors in the event logs of either the DC, or the TS, that seem
to pertain to the problem.

The Windows98 workstations themselves do not log on to the domain, although
we have tried joining them to the domain, and still get the same results.


"Vera Noest [MVP]" wrote:

> Which OS do you run on the DCs?
> Any errors in the EventLog on the DCs or the Terminal Servers?
>
> Check if this helps:
>
> 555038 - How to enable Windows 98/ME/NT clients to logon to Windows
> 2003 based Domains
> http://support.microsoft.com/?kbid=555038
> _________________________________________________________
> 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 08
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Installed a second domain controller to the domain. Next day
> > windows 98 PC's could not initiate RDP connections with any
> > terminal servers in our network.
> >
> > Only error message is that " The connection timed out "
> >
> > All other PC's can access the terminal servers only Win98 PC's
> > seem to be affected.
> >
> > Any suggestions?
>
 
I assume that removing the 2nd DC didn't solve the problem?
Can you ping the TS from a W98 client? Connect to a shared folder
from them?
Can you connect if you use the server's IP number in stead of its
name?
_________________________________________________________
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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 09
jul 2007 in microsoft.public.windows.terminal_services:

> The DC's run Windows Server 2003. The 2nd DC has since been
> demoted, and removed, from the network.
>
> There are no errors in the event logs of either the DC, or the
> TS, that seem to pertain to the problem.
>
> The Windows98 workstations themselves do not log on to the
> domain, although we have tried joining them to the domain, and
> still get the same results.
>
>
> "Vera Noest [MVP]" wrote:
>
>> Which OS do you run on the DCs?
>> Any errors in the EventLog on the DCs or the Terminal Servers?
>>
>> Check if this helps:
>>
>> 555038 - How to enable Windows 98/ME/NT clients to logon to
>> Windows 2003 based Domains
>> http://support.microsoft.com/?kbid=555038
>> _________________________________________________________
>> 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on
>> 08 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Installed a second domain controller to the domain. Next day
>> > windows 98 PC's could not initiate RDP connections with any
>> > terminal servers in our network.
>> >
>> > Only error message is that " The connection timed out "
>> >
>> > All other PC's can access the terminal servers only Win98
>> > PC's seem to be affected.
>> >
>> > Any suggestions?
 
Just to add to Vera's questions:
1. What Remote Desktop client and version is installed on the win98 boxes
and is it compatible to the configuration of the server? You may need to set
the encription level to client compatible or to install the newest RDP
client that will support high encription.

2. Do you use SSL or RDP security layer? If SSL, then is the certificate
trusted on the client computer and does the RDP client application support
SSL for RDP?

NOTE:
the settings I mentioned are here:
Administrative Tools --> Terminal Services Configuration -->
Connections (on the left side) --> RDP-Tcp (on the right) -->
(page) General


George Valkov


"Blair" <Blair@discussions.microsoft.com> wrote in message
news:B44219BC-5C7F-4323-ABD6-02ED9BC271B5@microsoft.com...
| The DC's run Windows Server 2003. The 2nd DC has since been demoted, and
| removed, from the network.
|
| There are no errors in the event logs of either the DC, or the TS, that
seem
| to pertain to the problem.
|
| The Windows98 workstations themselves do not log on to the domain,
although
| we have tried joining them to the domain, and still get the same results.
|
|
| "Vera Noest [MVP]" wrote:
|
| > Which OS do you run on the DCs?
| > Any errors in the EventLog on the DCs or the Terminal Servers?
| >
| > Check if this helps:
| >
| > 555038 - How to enable Windows 98/ME/NT clients to logon to Windows
| > 2003 based Domains
| > http://support.microsoft.com/?kbid=555038
| > _________________________________________________________
| > 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 08
| > jul 2007 in microsoft.public.windows.terminal_services:
| >
| > > Installed a second domain controller to the domain. Next day
| > > windows 98 PC's could not initiate RDP connections with any
| > > terminal servers in our network.
| > >
| > > Only error message is that " The connection timed out "
| > >
| > > All other PC's can access the terminal servers only Win98 PC's
| > > seem to be affected.
| > >
| > > Any suggestions?
| >
 
Removing the 2nd DC did not solve the problem.

We can ping the TS from the Win98 client.

The Win98 client cannot connect using the IP address, or the host name, of
the TS.

The Win98 clients are using version 5.2 of the Remote Desktop

All of the clients were connecting, with no issues, before we brought in the
2nd DC.

The security level in Terminal Services Configuration is set at RDP, and the
encryption level is set to client compatible.

Just to reiterate, our Win98 clients had been able to connect to their
respective TS's, with no problems, up until we added a 2nd Domain Controller.
We've since demoted, and removed, the 2nd DC from the network. Our Win98
clients do not log on to the network (although we tried this). all other
clients (Win2K, XP Pro, and some thin clients) are able to connect to their
TS's.





"George Valkov" wrote:

> Just to add to Vera's questions:
> 1. What Remote Desktop client and version is installed on the win98 boxes
> and is it compatible to the configuration of the server? You may need to set
> the encription level to client compatible or to install the newest RDP
> client that will support high encription.
>
> 2. Do you use SSL or RDP security layer? If SSL, then is the certificate
> trusted on the client computer and does the RDP client application support
> SSL for RDP?
>
> NOTE:
> the settings I mentioned are here:
> Administrative Tools --> Terminal Services Configuration -->
> Connections (on the left side) --> RDP-Tcp (on the right) -->
> (page) General
>
>
> George Valkov
>
>
> "Blair" <Blair@discussions.microsoft.com> wrote in message
> news:B44219BC-5C7F-4323-ABD6-02ED9BC271B5@microsoft.com...
> | The DC's run Windows Server 2003. The 2nd DC has since been demoted, and
> | removed, from the network.
> |
> | There are no errors in the event logs of either the DC, or the TS, that
> seem
> | to pertain to the problem.
> |
> | The Windows98 workstations themselves do not log on to the domain,
> although
> | we have tried joining them to the domain, and still get the same results.
> |
> |
> | "Vera Noest [MVP]" wrote:
> |
> | > Which OS do you run on the DCs?
> | > Any errors in the EventLog on the DCs or the Terminal Servers?
> | >
> | > Check if this helps:
> | >
> | > 555038 - How to enable Windows 98/ME/NT clients to logon to Windows
> | > 2003 based Domains
> | > http://support.microsoft.com/?kbid=555038
> | > _________________________________________________________
> | > 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 08
> | > jul 2007 in microsoft.public.windows.terminal_services:
> | >
> | > > Installed a second domain controller to the domain. Next day
> | > > windows 98 PC's could not initiate RDP connections with any
> | > > terminal servers in our network.
> | > >
> | > > Only error message is that " The connection timed out "
> | > >
> | > > All other PC's can access the terminal servers only Win98 PC's
> | > > seem to be affected.
> | > >
> | > > Any suggestions?
> | >
>
>
>
 
Mysterious!
I get the feeling that adding the second DC could be a red herring.
Maybe something else was done at the same time: reboot of the first
DC (which could activate a configuration change made weeks
earlier), security updates on the DC and/or the TS?

Just to narrow down the problem: can you enable Remote Desktop
connections on an XP client in the same domain + network, and try
to connect to the XP host from a W98 client?
_________________________________________________________
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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 10
jul 2007 in microsoft.public.windows.terminal_services:

> Removing the 2nd DC did not solve the problem.
>
> We can ping the TS from the Win98 client.
>
> The Win98 client cannot connect using the IP address, or the
> host name, of the TS.
>
> The Win98 clients are using version 5.2 of the Remote Desktop
>
> All of the clients were connecting, with no issues, before we
> brought in the 2nd DC.
>
> The security level in Terminal Services Configuration is set at
> RDP, and the encryption level is set to client compatible.
>
> Just to reiterate, our Win98 clients had been able to connect to
> their respective TS's, with no problems, up until we added a 2nd
> Domain Controller.
> We've since demoted, and removed, the 2nd DC from the network.
> Our Win98
> clients do not log on to the network (although we tried this).
> all other clients (Win2K, XP Pro, and some thin clients) are
> able to connect to their TS's.
>
>
> "George Valkov" wrote:
>
>> Just to add to Vera's questions:
>> 1. What Remote Desktop client and version is installed on the
>> win98 boxes and is it compatible to the configuration of the
>> server? You may need to set the encription level to client
>> compatible or to install the newest RDP client that will
>> support high encription.
>>
>> 2. Do you use SSL or RDP security layer? If SSL, then is the
>> certificate trusted on the client computer and does the RDP
>> client application support SSL for RDP?
>>
>> NOTE:
>> the settings I mentioned are here:
>> Administrative Tools --> Terminal Services Configuration -->
>> Connections (on the left side) --> RDP-Tcp (on the right) -->
>> (page) General
>>
>>
>> George Valkov
>>
>>
>> "Blair" <Blair@discussions.microsoft.com> wrote in message
>> news:B44219BC-5C7F-4323-ABD6-02ED9BC271B5@microsoft.com...
>> | The DC's run Windows Server 2003. The 2nd DC has since been
>> | demoted, and removed, from the network.
>> |
>> | There are no errors in the event logs of either the DC, or
>> | the TS, that seem
>> | to pertain to the problem.
>> |
>> | The Windows98 workstations themselves do not log on to the
>> | domain, although
>> | we have tried joining them to the domain, and still get the
>> | same results.
>> |
>> |
>> | "Vera Noest [MVP]" wrote:
>> |
>> | > Which OS do you run on the DCs?
>> | > Any errors in the EventLog on the DCs or the Terminal
>> | > Servers?
>> | >
>> | > Check if this helps:
>> | >
>> | > 555038 - How to enable Windows 98/ME/NT clients to logon to
>> | > Windows 2003 based Domains
>> | > http://support.microsoft.com/?kbid=555038
>> | > _________________________________________________________
>> | > 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?QmxhaXI=?= <Blair@discussions.microsoft.com>
>> | > wrote on 08 jul 2007 in
>> | > microsoft.public.windows.terminal_services:
>> | >
>> | > > Installed a second domain controller to the domain. Next
>> | > > day windows 98 PC's could not initiate RDP connections
>> | > > with any terminal servers in our network.
>> | > >
>> | > > Only error message is that " The connection timed out "
>> | > >
>> | > > All other PC's can access the terminal servers only Win98
>> | > > PC's seem to be affected.
>> | > >
>> | > > Any suggestions?
 
I was unable to connect ot a Win XP client.

However, I did discover that one (and only one) of our Win98 clients could
connect to the TS using the host name, but could not connect using the IP
address.

Is it possible that their could have been a registry ID problem on the Win
98 clients? I re-installed Win98 on one of the clients, and they were able
to connect to the host name, but not the IP address (this is a seperate
client form the one mentioned in the previous paragraph)

"Vera Noest [MVP]" wrote:

> Mysterious!
> I get the feeling that adding the second DC could be a red herring.
> Maybe something else was done at the same time: reboot of the first
> DC (which could activate a configuration change made weeks
> earlier), security updates on the DC and/or the TS?
>
> Just to narrow down the problem: can you enable Remote Desktop
> connections on an XP client in the same domain + network, and try
> to connect to the XP host from a W98 client?
> _________________________________________________________
> 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 10
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Removing the 2nd DC did not solve the problem.
> >
> > We can ping the TS from the Win98 client.
> >
> > The Win98 client cannot connect using the IP address, or the
> > host name, of the TS.
> >
> > The Win98 clients are using version 5.2 of the Remote Desktop
> >
> > All of the clients were connecting, with no issues, before we
> > brought in the 2nd DC.
> >
> > The security level in Terminal Services Configuration is set at
> > RDP, and the encryption level is set to client compatible.
> >
> > Just to reiterate, our Win98 clients had been able to connect to
> > their respective TS's, with no problems, up until we added a 2nd
> > Domain Controller.
> > We've since demoted, and removed, the 2nd DC from the network.
> > Our Win98
> > clients do not log on to the network (although we tried this).
> > all other clients (Win2K, XP Pro, and some thin clients) are
> > able to connect to their TS's.
> >
> >
> > "George Valkov" wrote:
> >
> >> Just to add to Vera's questions:
> >> 1. What Remote Desktop client and version is installed on the
> >> win98 boxes and is it compatible to the configuration of the
> >> server? You may need to set the encription level to client
> >> compatible or to install the newest RDP client that will
> >> support high encription.
> >>
> >> 2. Do you use SSL or RDP security layer? If SSL, then is the
> >> certificate trusted on the client computer and does the RDP
> >> client application support SSL for RDP?
> >>
> >> NOTE:
> >> the settings I mentioned are here:
> >> Administrative Tools --> Terminal Services Configuration -->
> >> Connections (on the left side) --> RDP-Tcp (on the right) -->
> >> (page) General
> >>
> >>
> >> George Valkov
> >>
> >>
> >> "Blair" <Blair@discussions.microsoft.com> wrote in message
> >> news:B44219BC-5C7F-4323-ABD6-02ED9BC271B5@microsoft.com...
> >> | The DC's run Windows Server 2003. The 2nd DC has since been
> >> | demoted, and removed, from the network.
> >> |
> >> | There are no errors in the event logs of either the DC, or
> >> | the TS, that seem
> >> | to pertain to the problem.
> >> |
> >> | The Windows98 workstations themselves do not log on to the
> >> | domain, although
> >> | we have tried joining them to the domain, and still get the
> >> | same results.
> >> |
> >> |
> >> | "Vera Noest [MVP]" wrote:
> >> |
> >> | > Which OS do you run on the DCs?
> >> | > Any errors in the EventLog on the DCs or the Terminal
> >> | > Servers?
> >> | >
> >> | > Check if this helps:
> >> | >
> >> | > 555038 - How to enable Windows 98/ME/NT clients to logon to
> >> | > Windows 2003 based Domains
> >> | > http://support.microsoft.com/?kbid=555038
> >> | > _________________________________________________________
> >> | > 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?QmxhaXI=?= <Blair@discussions.microsoft.com>
> >> | > wrote on 08 jul 2007 in
> >> | > microsoft.public.windows.terminal_services:
> >> | >
> >> | > > Installed a second domain controller to the domain. Next
> >> | > > day windows 98 PC's could not initiate RDP connections
> >> | > > with any terminal servers in our network.
> >> | > >
> >> | > > Only error message is that " The connection timed out "
> >> | > >
> >> | > > All other PC's can access the terminal servers only Win98
> >> | > > PC's seem to be affected.
> >> | > >
> >> | > > Any suggestions?
>
 
I'm sorry, but I can't make head or tail of your problem.
If it was a DNS problem, I would have expected the clients to be
unable to connect by hostname, but able to connect by IP number,
not the other way around.
But have you checked the ipconfig of the Win98 clients? Are you
using lmhosts files on them?
Re-installing the Win98 OS as a solution could indicate a licensing
problem, but that wouldn't prevent you from connecting to an XP
host.
But just to cover all possibilities, have you checked your TS
Licensing situation? Free TS CALs available? And the TS can locate
the TS LS? What's the OS of the Terminal Servers?
_________________________________________________________
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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 13
jul 2007 in microsoft.public.windows.terminal_services:

> I was unable to connect ot a Win XP client.
>
> However, I did discover that one (and only one) of our Win98
> clients could connect to the TS using the host name, but could
> not connect using the IP address.
>
> Is it possible that their could have been a registry ID problem
> on the Win 98 clients? I re-installed Win98 on one of the
> clients, and they were able to connect to the host name, but not
> the IP address (this is a seperate client form the one mentioned
> in the previous paragraph)
>
> "Vera Noest [MVP]" wrote:
>
>> Mysterious!
>> I get the feeling that adding the second DC could be a red
>> herring. Maybe something else was done at the same time: reboot
>> of the first DC (which could activate a configuration change
>> made weeks earlier), security updates on the DC and/or the TS?
>>
>> Just to narrow down the problem: can you enable Remote Desktop
>> connections on an XP client in the same domain + network, and
>> try to connect to the XP host from a W98 client?
>> _________________________________________________________
>> 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on
>> 10 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Removing the 2nd DC did not solve the problem.
>> >
>> > We can ping the TS from the Win98 client.
>> >
>> > The Win98 client cannot connect using the IP address, or the
>> > host name, of the TS.
>> >
>> > The Win98 clients are using version 5.2 of the Remote Desktop
>> >
>> > All of the clients were connecting, with no issues, before we
>> > brought in the 2nd DC.
>> >
>> > The security level in Terminal Services Configuration is set
>> > at RDP, and the encryption level is set to client compatible.
>> >
>> >
>> > Just to reiterate, our Win98 clients had been able to connect
>> > to their respective TS's, with no problems, up until we added
>> > a 2nd Domain Controller.
>> > We've since demoted, and removed, the 2nd DC from the
>> > network. Our Win98
>> > clients do not log on to the network (although we tried
>> > this). all other clients (Win2K, XP Pro, and some thin
>> > clients) are able to connect to their TS's.
>> >
>> >
>> > "George Valkov" wrote:
>> >
>> >> Just to add to Vera's questions:
>> >> 1. What Remote Desktop client and version is installed on
>> >> the win98 boxes and is it compatible to the configuration of
>> >> the server? You may need to set the encription level to
>> >> client compatible or to install the newest RDP client that
>> >> will support high encription.
>> >>
>> >> 2. Do you use SSL or RDP security layer? If SSL, then is the
>> >> certificate trusted on the client computer and does the RDP
>> >> client application support SSL for RDP?
>> >>
>> >> NOTE:
>> >> the settings I mentioned are here:
>> >> Administrative Tools --> Terminal Services Configuration -->
>> >> Connections (on the left side) --> RDP-Tcp (on the right)
>> >> --> (page) General
>> >>
>> >>
>> >> George Valkov
>> >>
>> >>
>> >> "Blair" <Blair@discussions.microsoft.com> wrote in message
>> >> news:B44219BC-5C7F-4323-ABD6-02ED9BC271B5@microsoft.com...
>> >> | The DC's run Windows Server 2003. The 2nd DC has since
>> >> | been demoted, and removed, from the network.
>> >> |
>> >> | There are no errors in the event logs of either the DC, or
>> >> | the TS, that seem
>> >> | to pertain to the problem.
>> >> |
>> >> | The Windows98 workstations themselves do not log on to the
>> >> | domain, although
>> >> | we have tried joining them to the domain, and still get
>> >> | the same results.
>> >> |
>> >> |
>> >> | "Vera Noest [MVP]" wrote:
>> >> |
>> >> | > Which OS do you run on the DCs?
>> >> | > Any errors in the EventLog on the DCs or the Terminal
>> >> | > Servers?
>> >> | >
>> >> | > Check if this helps:
>> >> | >
>> >> | > 555038 - How to enable Windows 98/ME/NT clients to logon
>> >> | > to Windows 2003 based Domains
>> >> | > http://support.microsoft.com/?kbid=555038
>> >> | > _________________________________________________________
>> >> | > 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?QmxhaXI=?= <Blair@discussions.microsoft.com>
>> >> | > wrote on 08 jul 2007 in
>> >> | > microsoft.public.windows.terminal_services:
>> >> | >
>> >> | > > Installed a second domain controller to the domain.
>> >> | > > Next day windows 98 PC's could not initiate RDP
>> >> | > > connections with any terminal servers in our network.
>> >> | > >
>> >> | > > Only error message is that " The connection timed out
>> >> | > > "
>> >> | > >
>> >> | > > All other PC's can access the terminal servers only
>> >> | > > Win98 PC's seem to be affected.
>> >> | > >
>> >> | > > Any suggestions?
 
What about the LM Level, or LM Type, or whatever it is called. IT has to do
with LAN Manager and how older clients authenticate with new Domains based
on Server2003. It had a big part to play in Win9x eing able to interact on
newer domain. Everytime they updated Server2003 (SP1, then R2, then SP2)
the conditions changed. Probably the new DC is not configured the same as
the previos one. Sorry I don't have any better detials, this is just
somthing that I barely remember any details on.

BTW - To the original poster,...Win9x cannot join a domain,...it can log on
to a Domain just fine, but not join a Domain. The two concepts are exclusive
to each other.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns996CDE752E76Bveranoesthemutforsse@207.46.248.16...
> I'm sorry, but I can't make head or tail of your problem.
> If it was a DNS problem, I would have expected the clients to be
> unable to connect by hostname, but able to connect by IP number,
> not the other way around.
> But have you checked the ipconfig of the Win98 clients? Are you
> using lmhosts files on them?
> Re-installing the Win98 OS as a solution could indicate a licensing
> problem, but that wouldn't prevent you from connecting to an XP
> host.
> But just to cover all possibilities, have you checked your TS
> Licensing situation? Free TS CALs available? And the TS can locate
> the TS LS? What's the OS of the Terminal Servers?
> _________________________________________________________
> 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on 13
> jul 2007 in microsoft.public.windows.terminal_services:
>
>> I was unable to connect ot a Win XP client.
>>
>> However, I did discover that one (and only one) of our Win98
>> clients could connect to the TS using the host name, but could
>> not connect using the IP address.
>>
>> Is it possible that their could have been a registry ID problem
>> on the Win 98 clients? I re-installed Win98 on one of the
>> clients, and they were able to connect to the host name, but not
>> the IP address (this is a seperate client form the one mentioned
>> in the previous paragraph)
>>
>> "Vera Noest [MVP]" wrote:
>>
>>> Mysterious!
>>> I get the feeling that adding the second DC could be a red
>>> herring. Maybe something else was done at the same time: reboot
>>> of the first DC (which could activate a configuration change
>>> made weeks earlier), security updates on the DC and/or the TS?
>>>
>>> Just to narrow down the problem: can you enable Remote Desktop
>>> connections on an XP client in the same domain + network, and
>>> try to connect to the XP host from a W98 client?
>>> _________________________________________________________
>>> 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?QmxhaXI=?= <Blair@discussions.microsoft.com> wrote on
>>> 10 jul 2007 in microsoft.public.windows.terminal_services:
>>>
>>> > Removing the 2nd DC did not solve the problem.
>>> >
>>> > We can ping the TS from the Win98 client.
>>> >
>>> > The Win98 client cannot connect using the IP address, or the
>>> > host name, of the TS.
>>> >
>>> > The Win98 clients are using version 5.2 of the Remote Desktop
>>> >
>>> > All of the clients were connecting, with no issues, before we
>>> > brought in the 2nd DC.
>>> >
>>> > The security level in Terminal Services Configuration is set
>>> > at RDP, and the encryption level is set to client compatible.
>>> >
>>> >
>>> > Just to reiterate, our Win98 clients had been able to connect
>>> > to their respective TS's, with no problems, up until we added
>>> > a 2nd Domain Controller.
>>> > We've since demoted, and removed, the 2nd DC from the
>>> > network. Our Win98
>>> > clients do not log on to the network (although we tried
>>> > this). all other clients (Win2K, XP Pro, and some thin
>>> > clients) are able to connect to their TS's.
>>> >
>>> >
>>> > "George Valkov" wrote:
>>> >
>>> >> Just to add to Vera's questions:
>>> >> 1. What Remote Desktop client and version is installed on
>>> >> the win98 boxes and is it compatible to the configuration of
>>> >> the server? You may need to set the encription level to
>>> >> client compatible or to install the newest RDP client that
>>> >> will support high encription.
>>> >>
>>> >> 2. Do you use SSL or RDP security layer? If SSL, then is the
>>> >> certificate trusted on the client computer and does the RDP
>>> >> client application support SSL for RDP?
>>> >>
>>> >> NOTE:
>>> >> the settings I mentioned are here:
>>> >> Administrative Tools --> Terminal Services Configuration -->
>>> >> Connections (on the left side) --> RDP-Tcp (on the right)
>>> >> --> (page) General
>>> >>
>>> >>
>>> >> George Valkov
>>> >>
>>> >>
>>> >> "Blair" <Blair@discussions.microsoft.com> wrote in message
>>> >> news:B44219BC-5C7F-4323-ABD6-02ED9BC271B5@microsoft.com...
>>> >> | The DC's run Windows Server 2003. The 2nd DC has since
>>> >> | been demoted, and removed, from the network.
>>> >> |
>>> >> | There are no errors in the event logs of either the DC, or
>>> >> | the TS, that seem
>>> >> | to pertain to the problem.
>>> >> |
>>> >> | The Windows98 workstations themselves do not log on to the
>>> >> | domain, although
>>> >> | we have tried joining them to the domain, and still get
>>> >> | the same results.
>>> >> |
>>> >> |
>>> >> | "Vera Noest [MVP]" wrote:
>>> >> |
>>> >> | > Which OS do you run on the DCs?
>>> >> | > Any errors in the EventLog on the DCs or the Terminal
>>> >> | > Servers?
>>> >> | >
>>> >> | > Check if this helps:
>>> >> | >
>>> >> | > 555038 - How to enable Windows 98/ME/NT clients to logon
>>> >> | > to Windows 2003 based Domains
>>> >> | > http://support.microsoft.com/?kbid=555038
>>> >> | > _________________________________________________________
>>> >> | > 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?QmxhaXI=?= <Blair@discussions.microsoft.com>
>>> >> | > wrote on 08 jul 2007 in
>>> >> | > microsoft.public.windows.terminal_services:
>>> >> | >
>>> >> | > > Installed a second domain controller to the domain.
>>> >> | > > Next day windows 98 PC's could not initiate RDP
>>> >> | > > connections with any terminal servers in our network.
>>> >> | > >
>>> >> | > > Only error message is that " The connection timed out
>>> >> | > > "
>>> >> | > >
>>> >> | > > All other PC's can access the terminal servers only
>>> >> | > > Win98 PC's seem to be affected.
>>> >> | > >
>>> >> | > > Any suggestions?
 
I think you are referring to NTLM 2 Authentication. Yes, that was the
KB article I suggested in my very first reply in this thread:

> 555038 - How to enable Windows 98/ME/NT clients to logon
> to Windows 2003 based Domains
> http://support.microsoft.com/?kbid=555038

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

"Phillip Windell" wrote on 14 aug 2007
in microsoft.public.windows.terminal_services:

> What about the LM Level, or LM Type, or whatever it is called.
> IT has to do with LAN Manager and how older clients authenticate
> with new Domains based on Server2003. It had a big part to play
> in Win9x eing able to interact on newer domain. Everytime they
> updated Server2003 (SP1, then R2, then SP2) the conditions
> changed. Probably the new DC is not configured the same as the
> previos one. Sorry I don't have any better detials, this is
> just somthing that I barely remember any details on.
 
Last edited by a moderator:
Ok, yes, I see that post now.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns998CE13ED1D5Averanoesthemutforsse@207.46.248.16...
>I think you are referring to NTLM 2 Authentication. Yes, that was the
> KB article I suggested in my very first reply in this thread:
>
>> 555038 - How to enable Windows 98/ME/NT clients to logon
>> to Windows 2003 based Domains
>> http://support.microsoft.com/?kbid=555038
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Phillip Windell" wrote on 14 aug 2007
> in microsoft.public.windows.terminal_services:
>
>> What about the LM Level, or LM Type, or whatever it is called.
>> IT has to do with LAN Manager and how older clients authenticate
>> with new Domains based on Server2003. It had a big part to play
>> in Win9x eing able to interact on newer domain. Everytime they
>> updated Server2003 (SP1, then R2, then SP2) the conditions
>> changed. Probably the new DC is not configured the same as the
>> previos one. Sorry I don't have any better detials, this is
>> just somthing that I barely remember any details on.
 
Last edited by a moderator:
Back
Top