I used to receive the maximum number of connections error message when I try to log on to the Windows 2003 Server in my office via Windows Remote Desktop.
This is pretty annoying if you have some urgent work to do in the server. Most of the already logged in users won’t even be using the session at the time, but I can’t login! So how to solve this? After a bit of googling, as usual, I found a simple way to disconnect other remotely logged in sessions.
First of all you must be logged in to your client computer as a domain Admin user. Now open the command prompt and type in the following command.
The Ip address or domain name of the Remote server should be entered in place of SERVERIP
You will get a list of the Remote Sessions in the command window.
In the above sceenshot we can clearly see an Active RDP session with the ID 2 which belongs to the user Administrator. In order to disconnect that user we are going to use the session ID. Use the following command line to disconnect the remote session.
rwinsta /server:SERVERIP SESSIONID
For example in order to terminate the session of the Administrator user the following command should be given.
rwinsta /server:10.10.1.10 2
Now let’s confirm if the user is really disconnected. Just type in the qwinsta command in proper format.
As you can see our session with ID 2 is no longer there. Now for the user we just disconnected will see the following message.
The remote session was disconnected because you session was logged off at the remote computer. Your administrator or another user might have ended your connection.
Source : TechTalkz
Due to a problem with some of our servers I was trying to compare 3 registry’s because 2 did function correct and one had an unidentified problem which caused the problem.
I found a nice and easy tool called regdiff. It once was nested inside the Windows Resource Kit.
You can download it at http://www.p-nand-q.com/download/tools/regdiff.zip
Easiest is too export the two directories you want to compare. You also can use the whole registry but think about all the variables which are different per server. You will get a lot of failed compares then.
If you just have a little clue where too search for your problem, try to compare some directories there instead of the whole regsitry.
You can find more information on:
A few days ago I found a nice very lite twitter app. It’s a CLI which works like a charm.
So don’t expect flashy visuals and gui’s like most other twitter applications. Just back to basics for fast reading and posting 🙂
It’s also completely standalone uses only one executable and one configuration file. No installer needed, just unpack the ZIP file.
You can download it at
With Quitter, you can…
- Read, post, reply and retweet.
- Organize the people you follow into groups and read tweets by group.
- Filter (or highlight) tweets from specific users or that contain certain #hashtags.
- Use URL shorteners like TinyUrl.com for tweeting URLs.
- Easily open tweeted links from other users in your default browser (no copy/paste needed)
- Send and receive direct messages
- Follow or unfollow other users
Quitter runs on Windows 2000/XP/Vista and requires Version 2.0 of the Microsoft .NET Framework or higher (version 2.0 was released in 2006; most Windows machines should have version 2.0 or higher).
Quitter is free (as in beer) and open-source and will always be both.