P
Peter Jenei
Hi All!
It's a solved problem, so I just write this post to be a lesson to everyone.
I wanted to do something with a win2003 server, so I connected to it with
XP's remote desktop. I noticed that the server is extremely slow. Task
Manager showed that winlogon uses about 88-90% of cpu. I tried everything
(restart, stopping services, searching newsgroups, etc.), but I didn't find
an answer. Finally (after more than 1 day) I found a post with a similar
problem, where the solution was changing some firewall settings. So I
started to adjust the firewall. At last I disabled all open ports, including
the one that is used by remote desktop, so the connection lost and I had to
go to server. There I found a few books on the Enter key of the server's
keyboard, so the Windows was continuously swapping the "press ctrl+alt+del"
screen with the one that explains why pressing ctrl+alt+del is so safe. This
continuous swapping caused winlogon to consume almost all cpu power.
So the lesson is: sometimes try to clean the table where your server's
keyboard is.
Peter Jenei
Budapest, Hungary
It's a solved problem, so I just write this post to be a lesson to everyone.
I wanted to do something with a win2003 server, so I connected to it with
XP's remote desktop. I noticed that the server is extremely slow. Task
Manager showed that winlogon uses about 88-90% of cpu. I tried everything
(restart, stopping services, searching newsgroups, etc.), but I didn't find
an answer. Finally (after more than 1 day) I found a post with a similar
problem, where the solution was changing some firewall settings. So I
started to adjust the firewall. At last I disabled all open ports, including
the one that is used by remote desktop, so the connection lost and I had to
go to server. There I found a few books on the Enter key of the server's
keyboard, so the Windows was continuously swapping the "press ctrl+alt+del"
screen with the one that explains why pressing ctrl+alt+del is so safe. This
continuous swapping caused winlogon to consume almost all cpu power.
So the lesson is: sometimes try to clean the table where your server's
keyboard is.
Peter Jenei
Budapest, Hungary