You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, download files, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
For a very long time, I have found myself caught in a bind. I like to use terminal server to access my machines for maintenance, and remote assistance of clients. Yet, due to some custom networking security situations, I cannot use the default port (3389) for my sessions. This has left me in a bind. I can access computers remotely using another desktop computer, but using the Pocket PC's Terminal Services client, I cannot. The reason is the PPC client doesn't support anything but the remote port connection. Not only that, you cannot fake it by trying to bind your port into a connection IP (i.e. 192.168.80.52:120)
That's where Tweaks2K2.NET comes into play. I've searched high and low for years for a registry hack or port remapper that would allow me to do it. Well, it appears this little app, has just been updated to include a port switching function!
And it works too! First time! No reconfig or trying to hack your way in. Just set it and go! W00T!
I might also add that it seems the Terminal Services Client for Pocket PC is quite optimized compared to other times I've used it. Things seem to go lickity split, and the desktop optimization feature that shrinks your desktop makes it a lot easier to get around via the "small screen".
Any Comments?
Seriously, I've been looking for this solution for YEARS! I am so happy that it can be done now.
The way it works for most of the people in my line of work is the problem that needs solving is compounded by the distance you are away from a particular server or desktop. So odds are I'm up in the mountains or at the beach on a mini-vacation when someone locks up a printer queue or something. Or worse! I've been called when riding a commuter bus in a different state to remedy something 250 miles away that is simple for me, but impossible for non-admins. The idea that I could pull up the machine in question and fix it instantly makes Terminal Server a great product-- heck you don't even have to wait to boot a laptop! Tweaks, is great in that it makes Terminal Server work around all the barriers.
Plus, its so cool to administer a machine while sitting and having some coffee at starbucks.
Not only that, you cannot fake it by trying to bind your port into a connection IP (i.e. 192.168.80.52:120)
Linear Mode
