Arrow, delete key behavior

  • Thread starter Thread starter Bob Graham
  • Start date Start date
B

Bob Graham

Hi, I posted this question in the wrong ng before I found this (the correct)
one.

I'm having a problem that when connecting from an XP external client to an
SBS win 2k server, the arrow and delete keys behave as if the shift key is
being held down. That is, left arow selects text to the left, delete key
acts as backspace etc. At least one other user I've found is having the
exact same problem. The situation may be related to sp4 going onto the win2k
server.

Anyone?
 
Did this only start happening after you installed SP4?
Have you tried to update the client's RDP client?

-M
 
I can't be certain, it started after building new hardware for my home
office and re-installing Terminal Services on my new machine. The SBS
servers (2000 server) I'm connecting to never displayed this behavior
before, and one of them has had SP4 since July. It first exhibited this
behavior when I changed my home office hardware last week. Then I installed
SP4 on the other 2K server a couple of days ago and now it's doing the same
thing. So the order in which the problem developed is inconclusive, as I
used TS from an external XP client to the 2k SP4 server for more than a
month before the problem developed.

"Update the client's RDP client" is unfamiliar lingo to me (I'm mostly a
database developer). Does that mean update Terminal Services with patch/new
version? Is RDP another term for TS or is it a protocol TS uses? Is there a
newer version of TS since 2k server came out? I'll research that on my own,
but if you have a reply I'd be glad to hear it.

Can I use XP Remote Desktop to the server instead of TS?

Thanks, Bob
 
Hmm...Have you tried giving your user account a new
profile? Could the server think you are using a different
type of keyboard than you actually are? Try changing you
keyboard through the control panel and see what happens.

-M
 
I shut down my system and put the USB adapter on my keyboard and rebooted,
now the system recognizes it as Microsoft USB Natural Keyboard (it was
generic before).

No change.

PS: Marni Dangerfield [[email protected]] is having the identical
problem.

I found her post in another newsgroup this morning, can't remember where
now.

Bob
 
What happens if you give the user a new profile?

Does this problem also occur at the console of the
terminal server? Have you tried other keyboard drivers
(other than generic and Microsoft USB Natural Keyboard) in
the terminal services session? Have you tried using a
different input locale?

-M
-----Original Message-----
I shut down my system and put the USB adapter on my keyboard and rebooted,
now the system recognizes it as Microsoft USB Natural Keyboard (it was
generic before).

No change.

PS: Marni Dangerfield [[email protected]] is having the identical
problem.

I found her post in another newsgroup this morning, can't remember where
now.

Bob


Hmm...Have you tried giving your user account a new
profile? Could the server think you are using a different
type of keyboard than you actually are? Try changing you
keyboard through the control panel and see what happens.

-M
TS
and it works, but
Click to expand...


.
Click to expand...
 
Ah...so based on that information, the problem is with
your home office computer, rather than with the terminal
server or an account.

Do you have the latest service pack for your Window XP
home office computer? What if your input locale set to on
that computer?

Just offhand, can you possibly remove SP4 from your
terminal server to see if that is causing the issue (since
you mentioned that this problem may have started after
installing SP4)?

-M
-----Original Message-----
I'm logging in as the Administrator account, (not the actual name), the
problem does not occur at the console, nor does it occur when I log into the
same accounts from my workstation inside the lan (also running the same
winXp + Sp1).

It only occurs when I'm connecting from my Home Office.

Bob


What happens if you give the user a new profile?

Does this problem also occur at the console of the
terminal server? Have you tried other keyboard drivers
(other than generic and Microsoft USB Natural Keyboard) in
the terminal services session? Have you tried using a
different input locale?

-M
-----Original Message-----
I shut down my system and put the USB adapter on my keyboard and rebooted,
now the system recognizes it as Microsoft USB Natural Keyboard (it was
generic before).

No change.

PS: Marni Dangerfield [[email protected]] is having the identical
problem.

I found her post in another newsgroup this morning,
Click to expand...
can't
remember where
now.

Bob


"Matthew Harris [MVP]" <[email protected]>
Click to expand...
wrote
in message
Hmm...Have you tried giving your user account a new
profile? Could the server think you are using a different
type of keyboard than you actually are? Try changing you
keyboard through the control panel and see what happens.

-M

-----Original Message-----
Ok, I tried connecting with Remote Desktop instead
Click to expand...
of
TS
and it works, but
the incorrect keyboard behavior is identical.

Bob


.
Click to expand...
Click to expand...


.
Click to expand...
 
regional.... is all English(US) or United States.


Matthew Harris said:
Ah...so based on that information, the problem is with
your home office computer, rather than with the terminal
server or an account.

Do you have the latest service pack for your Window XP
home office computer? What if your input locale set to on
that computer?

Just offhand, can you possibly remove SP4 from your
terminal server to see if that is causing the issue (since
you mentioned that this problem may have started after
installing SP4)?

-M
-----Original Message-----
I'm logging in as the Administrator account, (not the actual name), the
problem does not occur at the console, nor does it occur when I log into the
same accounts from my workstation inside the lan (also running the same
winXp + Sp1).

It only occurs when I'm connecting from my Home Office.

Bob


What happens if you give the user a new profile?

Does this problem also occur at the console of the
terminal server? Have you tried other keyboard drivers
(other than generic and Microsoft USB Natural Keyboard) in
the terminal services session? Have you tried using a
different input locale?

-M

-----Original Message-----
I shut down my system and put the USB adapter on my
keyboard and rebooted,
now the system recognizes it as Microsoft USB Natural
Keyboard (it was
generic before).

No change.

PS: Marni Dangerfield [[email protected]] is
having the identical
problem.

I found her post in another newsgroup this morning, can't
remember where
now.

Bob


in message
Hmm...Have you tried giving your user account a new
profile? Could the server think you are using a
different
type of keyboard than you actually are? Try changing
you
keyboard through the control panel and see what happens.

-M

-----Original Message-----
Ok, I tried connecting with Remote Desktop instead of
TS
and it works, but
the incorrect keyboard behavior is identical.

Bob


.
Click to expand...


.
Click to expand...
Click to expand...
 
Hi Bob.

I did a search on Google and came up with your thread.

I have "EXACTLY" the same symptons!

Maybe we can exchange notes to get to the bottom of this.

Here is my situation:

Win2K server at work.

WinXP SP1 at home.

- Remote Desktop from within work LAN to server, works normal.
[Have not tried with suspicious laptop]

- Remote Desktop from my home LAN to server:
- Wrong "DEL" key and "Arrow" behaviour from:
Dell Inspiron 5150 laptop (both with/without USB keyboard)
[This has a "Mobile Pentium M 3.06GHz"
- Correct key behaviour from:
Dell Inspiron 8100 laptop (Pentium III 1GHz)

Both of above running WinXP SP1, US keyboard in settings.

That's all I've tried for now.

It seems to me to be a client (and not a LAN/firewall/server issue).
What type of hardware are you running on?

Cheers,
Laz.
 
I've tried the workaround suggested in the thread above, which is to
kill the ati control panel process, and it works! The arrow keys and
delete keys behave properly in remote desktop to W2K server.

The workaround (in my case) was to bring up the window task manager
(ctl-ahift-esc) and stop the atiptaxx.exe process.

Cheers,

Laz.
 
Hmmmm,

My problem was there all weekend, but mysteriously disappeared this morning.

I am running ATI control panel with a driver in the series mentioned, if the
problem comes back I'll disable the taskbar icon and see if that fixes it.

Thanks, Bob
 
ATI have just released a new driver (last thursday, actually). I'm going to
give it a shot any way.

Doesn't mention this bug, but they have so many issues to work oon that it
might be a fix.

Bob
 
good morning..

my user does not have the ati process running, so i can't
try that fix. i was optimisit for a minute!! the video
driver is an sis.

and for the record, this particular user is on a new xp
(not sure of the brand, probably a clone of some kind) and
our w2000 server has sp2. the problem happens in the
login screen through ts, so it's not user specific as no
user is logged in.

still looking for a solution. thanks for all the help so
far.
marni
 
Back
Top