Windows 98 connecting to 2003 Terminal Server

I have just installed a 2003 Terminal Server and all clients connect except
the 4 Windows 98 machines. I have reinstalled 98 onto one just in case this
was a problem but it hasn't helped.

The client is configured using RDP client 5.1 (or 5.2 tried both) and as
soon as the connection begins and the desktop pops up, the client locks and
the machine needs to be reset.

This does not occur when connecting to 2000 Terminal servers. This alos
occurs at multiple sites, I discovered after testing. This happens whether
the connection is done via the local network, or across the web.

Any help will be appreciated.

Regards,

Scott.

By default Windows 98 uses lm authentication. If the Windows 2003 server is
configured not to accept lm then that could be one problem. Another possible
problem is smb signing which W2003 requires by default. Open Local Security
Policy on the W2003 server and go to security settings/local policies/user
rights and make sure that lan manager authentication level is NOT set to
sends ntlmv2 response only - refuse lm\ntlm or sends ntlmv2 response only -
refuse lm. Also for Microsoft Network server:digitally sign
communications(always) configure to be DISABLED. Also see the link below for
other security options that may be a problem. Note that the Directory
Services Client can be applied to W98 computers that will allow them to use
ntlmv2 after a registry modification.--- Steve

http://support.microsoft.com/default...b;en-us;823659

"Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in message
news:4AD4017C-D530-4C0F-8C6B-(E-Mail Removed)...
>I have just installed a 2003 Terminal Server and all clients connect except
> the 4 Windows 98 machines. I have reinstalled 98 onto one just in case
> this
> was a problem but it hasn't helped.
>
> The client is configured using RDP client 5.1 (or 5.2 tried both) and as
> soon as the connection begins and the desktop pops up, the client locks
> and
> the machine needs to be reset.
>
> This does not occur when connecting to 2000 Terminal servers. This alos
> occurs at multiple sites, I discovered after testing. This happens
> whether
> the connection is done via the local network, or across the web.
>
> Any help will be appreciated.
>
> Regards,
>
> Scott.

Thanks for the reply.

I have tried all that with no success. I do not need to connect to the
servers in any way other than running the RDPClient so I don't know if there
would be any authentication issues. I am only connecting to port 3389 with
RDP.

I installed a fresh copy of 98 from the latest CD I have to ensure win98
wasn't corrupted but it didn't help.

I would not normally have a problem except in this case the whole machine
just freezes. Sometimes it is before the connection box has dissappeared,
other times it is after it has drawn the grey background of the 2003 login
screen. Whatever the case, it requires a reboot to fix as the whole system
is instantly unresponsive.

I can still gain access to network drives and folders with no problems but
get this, I can connect to the sbs server webpage and go to remote desktop
and connect via the activex control with no problems at all.

Why does remote desktop activex control run but the remote desktop win app
locks the entire workstation?


"Steven L Umbach" wrote:

> By default Windows 98 uses lm authentication. If the Windows 2003 server is
> configured not to accept lm then that could be one problem. Another possible
> problem is smb signing which W2003 requires by default. Open Local Security
> Policy on the W2003 server and go to security settings/local policies/user
> rights and make sure that lan manager authentication level is NOT set to
> sends ntlmv2 response only - refuse lm\ntlm or sends ntlmv2 response only -
> refuse lm. Also for Microsoft Network server:digitally sign
> communications(always) configure to be DISABLED. Also see the link below for
> other security options that may be a problem. Note that the Directory
> Services Client can be applied to W98 computers that will allow them to use
> ntlmv2 after a registry modification.--- Steve
>
> http://support.microsoft.com/default...b;en-us;823659
>
> "Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in message
> news:4AD4017C-D530-4C0F-8C6B-(E-Mail Removed)...
> >I have just installed a 2003 Terminal Server and all clients connect except
> > the 4 Windows 98 machines. I have reinstalled 98 onto one just in case
> > this
> > was a problem but it hasn't helped.
> >
> > The client is configured using RDP client 5.1 (or 5.2 tried both) and as
> > soon as the connection begins and the desktop pops up, the client locks
> > and
> > the machine needs to be reset.
> >
> > This does not occur when connecting to 2000 Terminal servers. This alos
> > occurs at multiple sites, I discovered after testing. This happens
> > whether
> > the connection is done via the local network, or across the web.
> >
> > Any help will be appreciated.
> >
> > Regards,
> >
> > Scott.
>
>
>

Sorry, I tell a lie.

It doesn't lock the pc when running in a window. As soon as I run
fullscreen, it locks the PC.

I guess video card drivers are next.

"Scott-BrisQld" wrote:

> Thanks for the reply.
>
> I have tried all that with no success. I do not need to connect to the
> servers in any way other than running the RDPClient so I don't know if there
> would be any authentication issues. I am only connecting to port 3389 with
> RDP.
>
> I installed a fresh copy of 98 from the latest CD I have to ensure win98
> wasn't corrupted but it didn't help.
>
> I would not normally have a problem except in this case the whole machine
> just freezes. Sometimes it is before the connection box has dissappeared,
> other times it is after it has drawn the grey background of the 2003 login
> screen. Whatever the case, it requires a reboot to fix as the whole system
> is instantly unresponsive.
>
> I can still gain access to network drives and folders with no problems but
> get this, I can connect to the sbs server webpage and go to remote desktop
> and connect via the activex control with no problems at all.
>
> Why does remote desktop activex control run but the remote desktop win app
> locks the entire workstation?
>
>
> "Steven L Umbach" wrote:
>
> > By default Windows 98 uses lm authentication. If the Windows 2003 server is
> > configured not to accept lm then that could be one problem. Another possible
> > problem is smb signing which W2003 requires by default. Open Local Security
> > Policy on the W2003 server and go to security settings/local policies/user
> > rights and make sure that lan manager authentication level is NOT set to
> > sends ntlmv2 response only - refuse lm\ntlm or sends ntlmv2 response only -
> > refuse lm. Also for Microsoft Network server:digitally sign
> > communications(always) configure to be DISABLED. Also see the link below for
> > other security options that may be a problem. Note that the Directory
> > Services Client can be applied to W98 computers that will allow them to use
> > ntlmv2 after a registry modification.--- Steve
> >
> > http://support.microsoft.com/default...b;en-us;823659
> >
> > "Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in message
> > news:4AD4017C-D530-4C0F-8C6B-(E-Mail Removed)...
> > >I have just installed a 2003 Terminal Server and all clients connect except
> > > the 4 Windows 98 machines. I have reinstalled 98 onto one just in case
> > > this
> > > was a problem but it hasn't helped.
> > >
> > > The client is configured using RDP client 5.1 (or 5.2 tried both) and as
> > > soon as the connection begins and the desktop pops up, the client locks
> > > and
> > > the machine needs to be reset.
> > >
> > > This does not occur when connecting to 2000 Terminal servers. This alos
> > > occurs at multiple sites, I discovered after testing. This happens
> > > whether
> > > the connection is done via the local network, or across the web.
> > >
> > > Any help will be appreciated.
> > >
> > > Regards,
> > >
> > > Scott.
> >
> >
> >

Hmm. I don't really know what is going on and have not used W98 in a while.
It may be worth a try to install the Directory Services Client on one of the
W98 computers [from W2003 install disk], and try posting in
Microsoft.public.windows.terminal_services newsgroup. --- Steve


"Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in message
news:ADCF4C8A-C18A-44C6-BF58-(E-Mail Removed)...
> Thanks for the reply.
>
> I have tried all that with no success. I do not need to connect to the
> servers in any way other than running the RDPClient so I don't know if
> there
> would be any authentication issues. I am only connecting to port 3389
> with
> RDP.
>
> I installed a fresh copy of 98 from the latest CD I have to ensure win98
> wasn't corrupted but it didn't help.
>
> I would not normally have a problem except in this case the whole machine
> just freezes. Sometimes it is before the connection box has dissappeared,
> other times it is after it has drawn the grey background of the 2003 login
> screen. Whatever the case, it requires a reboot to fix as the whole
> system
> is instantly unresponsive.
>
> I can still gain access to network drives and folders with no problems but
> get this, I can connect to the sbs server webpage and go to remote desktop
> and connect via the activex control with no problems at all.
>
> Why does remote desktop activex control run but the remote desktop win app
> locks the entire workstation?
>
>
> "Steven L Umbach" wrote:
>
>> By default Windows 98 uses lm authentication. If the Windows 2003 server
>> is
>> configured not to accept lm then that could be one problem. Another
>> possible
>> problem is smb signing which W2003 requires by default. Open Local
>> Security
>> Policy on the W2003 server and go to security settings/local
>> policies/user
>> rights and make sure that lan manager authentication level is NOT set to
>> sends ntlmv2 response only - refuse lm\ntlm or sends ntlmv2 response
>> only -
>> refuse lm. Also for Microsoft Network server:digitally sign
>> communications(always) configure to be DISABLED. Also see the link below
>> for
>> other security options that may be a problem. Note that the Directory
>> Services Client can be applied to W98 computers that will allow them to
>> use
>> ntlmv2 after a registry modification.--- Steve
>>
>> http://support.microsoft.com/default...b;en-us;823659
>>
>> "Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in
>> message
>> news:4AD4017C-D530-4C0F-8C6B-(E-Mail Removed)...
>> >I have just installed a 2003 Terminal Server and all clients connect
>> >except
>> > the 4 Windows 98 machines. I have reinstalled 98 onto one just in case
>> > this
>> > was a problem but it hasn't helped.
>> >
>> > The client is configured using RDP client 5.1 (or 5.2 tried both) and
>> > as
>> > soon as the connection begins and the desktop pops up, the client locks
>> > and
>> > the machine needs to be reset.
>> >
>> > This does not occur when connecting to 2000 Terminal servers. This
>> > alos
>> > occurs at multiple sites, I discovered after testing. This happens
>> > whether
>> > the connection is done via the local network, or across the web.
>> >
>> > Any help will be appreciated.
>> >
>> > Regards,
>> >
>> > Scott.
>>
>>
>>

Fixed.

It turned out to be video drivers. It was fine in a window but not in
fullscreen.

I eventually (do you know how hard it is to find drivers for a video card
from a manufacturer that went out of business at least 4 years ago???)
Anyway, even the Windows Update drivers failed the same way. I finally found
a later driver on a french website that works. The really bizzare
coincidence is that the remaining machines all have different video cards.

Well at least the problem is resolved.

Thanks.

"Steven L Umbach" wrote:

> Hmm. I don't really know what is going on and have not used W98 in a while.
> It may be worth a try to install the Directory Services Client on one of the
> W98 computers [from W2003 install disk], and try posting in
> Microsoft.public.windows.terminal_services newsgroup. --- Steve
>
>
> "Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in message
> news:ADCF4C8A-C18A-44C6-BF58-(E-Mail Removed)...
> > Thanks for the reply.
> >
> > I have tried all that with no success. I do not need to connect to the
> > servers in any way other than running the RDPClient so I don't know if
> > there
> > would be any authentication issues. I am only connecting to port 3389
> > with
> > RDP.
> >
> > I installed a fresh copy of 98 from the latest CD I have to ensure win98
> > wasn't corrupted but it didn't help.
> >
> > I would not normally have a problem except in this case the whole machine
> > just freezes. Sometimes it is before the connection box has dissappeared,
> > other times it is after it has drawn the grey background of the 2003 login
> > screen. Whatever the case, it requires a reboot to fix as the whole
> > system
> > is instantly unresponsive.
> >
> > I can still gain access to network drives and folders with no problems but
> > get this, I can connect to the sbs server webpage and go to remote desktop
> > and connect via the activex control with no problems at all.
> >
> > Why does remote desktop activex control run but the remote desktop win app
> > locks the entire workstation?
> >
> >
> > "Steven L Umbach" wrote:
> >
> >> By default Windows 98 uses lm authentication. If the Windows 2003 server
> >> is
> >> configured not to accept lm then that could be one problem. Another
> >> possible
> >> problem is smb signing which W2003 requires by default. Open Local
> >> Security
> >> Policy on the W2003 server and go to security settings/local
> >> policies/user
> >> rights and make sure that lan manager authentication level is NOT set to
> >> sends ntlmv2 response only - refuse lm\ntlm or sends ntlmv2 response
> >> only -
> >> refuse lm. Also for Microsoft Network server:digitally sign
> >> communications(always) configure to be DISABLED. Also see the link below
> >> for
> >> other security options that may be a problem. Note that the Directory
> >> Services Client can be applied to W98 computers that will allow them to
> >> use
> >> ntlmv2 after a registry modification.--- Steve
> >>
> >> http://support.microsoft.com/default...b;en-us;823659
> >>
> >> "Scott-BrisQld" <Scott-(E-Mail Removed)> wrote in
> >> message
> >> news:4AD4017C-D530-4C0F-8C6B-(E-Mail Removed)...
> >> >I have just installed a 2003 Terminal Server and all clients connect
> >> >except
> >> > the 4 Windows 98 machines. I have reinstalled 98 onto one just in case
> >> > this
> >> > was a problem but it hasn't helped.
> >> >
> >> > The client is configured using RDP client 5.1 (or 5.2 tried both) and
> >> > as
> >> > soon as the connection begins and the desktop pops up, the client locks
> >> > and
> >> > the machine needs to be reset.
> >> >
> >> > This does not occur when connecting to 2000 Terminal servers. This
> >> > alos
> >> > occurs at multiple sites, I discovered after testing. This happens
> >> > whether
> >> > the connection is done via the local network, or across the web.
> >> >
> >> > Any help will be appreciated.
> >> >
> >> > Regards,
> >> >
> >> > Scott.
> >>
> >>
> >>
>
>
>