You are currently browsing the category archive for the 'Remote Login' category.
Since installing bbPress on the forum.blandname.com subdomain, I’ve become addicted to the rapid posting workflow: add topic, title, description and post! It’s 4 steps and is over so quick I’ve been thinking about making a bookmarklet that will automate the task for me. Here’s the latest smaller posts I sent there, but should some day expand upon here (I’ll use blandname for longer posts from now on):
- vTiger CRM Virtual Machine
- RDP Manager for your Windows System Tray
- HOWTO TrixBox - VoIP Virtual Machine
- Online Virtual Machine Builder
- Microsoft Distributes Demo Software via VHD
- FREE Terminal Server Monitoring Tool
- VMware Workstation 6 Feature List
- Multi monitor support for RDP 6
- Add Reflections to bbPress Images
- Google PageRank and Alexa in Your Firefox 2
- Display Digg in WordPress - Digg Dugg Plugin
- Google Analytics Plugn for bbPress
Related Articles:
Currently the only way to get Vista on Vista virtualization running is to either use Virtual Server 2005 with some tweaks, or if you are part of the Virtual PC 2007 beta you can install Virtual PC 2007 (VPC 2K7) on Vista with no tweaks or hacks needed whatsoever. Unfortunately neither of these solutions can virtualize a 64bit operating system, but VMware Server should be Vista compliant soon - so I’m holding me breath until then.
Following my friend’s guide to setting up Virtual PC 2007 on Windows Vista found over at WebandRaptors, I was able to get VPC 2k7 set up quickly and without pain.
Next came the Windows Vista install, which was pretty straightforward. Something to note: you don’t actually need to use a CD key during installation, you can simply click the “next” button and the installer will inform you that a CD key will be needed later, I think it’s about 30days before it becomes necessary.
Once Vista is installed and configured for remote access from within VPC, all you need to do to get Aero Glass running is to connect to the virtual machine using the Remote Desktop Connection (RDP 6) client. If your host, or physical, machine supports Aero Glass, the virtual machine will allow you to take advantage of it, giving you transparent blurred windows, mouse-over taskbar previews, and cool windows+tab animation!
Related Articles:
SSH is one powerful tool. You can do just about everything under the sun using an SSH login to a remote computer. SSH works very well in low-bandwidth situations like dialup, or satlinks.
But wakeup, we’re no longer in the 80s - people want GUIs, let’s give them fancy-pants graphics, bouncing cursors and silly linux wizards. Remotely.
Enter Xming, what I would name as top of my favorite applications. Xming is just like X over SSH, for dummies (or people who would rather spend more time working).
Xming allows you to connect to remote or local Linux workstations and servers and run full graphical applications on those remote machines on your local Windows computer.
Here’s how it works: all of the applications are run remotely, but when it comes to the graphics, the information that would invoke the graphics is sent to your local computer, not a bitmap or a sequence of bitmaps like VNC. Xming uses a local X server on your Windows computer in order to display your remote applications. This local X server is 2D accelerated, and it’s sometimes difficult to even notice that you are working remotely.
Since Xming can run in windowed or full-screen modes, you can establish thin client connections in this fashion, or you can publish applications Citrix-style.
Xming is completely free to install and setup. It is a great way to manage virtual machines, and in fact is often faster than Microsoft’s Virtual Server ActiveX control (surprised?), VMWare’s Virtual Machine view (even with VMWare tools!), and even Parallels speedy virtual machine view.
To set the whole thing up, you’ll need a computer running Microsoft Windows, one Linux box, a network connection between the two, but you won’t need much effort.
First install the Windows Xming server on your Windows computer. We’ll use Windows XP SP2 in this example, but it could easily be other varieties. Xming can be found on Sourceforge quite easily, download it, run the install (use defaults), and start XLauncher.
On the Linux computer this are slighlty more complicated, but not by much. For Gnome or KDE on Ubuntu Edgy, go to the System>Administration menu in your menu bar. In Administration, we’ll select login preferences as we’ll be setting up a new logon method (we’re using XDMCP). Select the Remote tab, and enable remote logon (same as local) to your Edgy Eft machine.
Now on your Windows machine, set up XLaunch to logon to your Linux machine using it’s IP address. Save the setting if you want, and connect. You will be presented with a logon screen to your Linux desktop!
Related Articles:
If you’re like me, you have many computers that you connect to remotely when away from work, or home, using RDP.
The easiest way to connect to all of these computers (aside from setting up a VPN) is to change the default port on which Windows will accept RDP connections.
Since things have changed a bit in Microsoft Windows Vista, here is how to change that port:
Click on the Start button, and navigate to accessories. From there, clik on the Run icon. Once the Run applet has started, we’ll enter the good ole regedit command. It still works like a charm!
Within the registry editor, navigate to:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\
Terminal Server\WinStations\EH-Tcp
We want to change the registry key PortNumber in order to modify the default port. The default port is 3390, and I normally use ports in the 338x range, so double click on the key, check the decimal setting, the set the “Value data” to 3389.
Click OK, then close Regedit, and connect from a remote PC.
Note: you may want to create a firewall rule for port 3389 in order to allow connections.
Related Articles:
Here are screenshots from the upcoming Micorosoft RDP 6 client for Windows (Vista and XP), and explanations for each feature so that you can get started with your testing now and stay ahead of the game.
The options screen to the new RDP 6 client is very similar to that in version 5, but as you can see, it does not have input regions for login name and password. This is now done when you connect, and yes it can still be stored. Also note that just like in previous versions, if you would like to save the settings you will need to return to this tab as Microsoft still seems to think that saving options should not be done from all tabs for some reason. If you would like to make the options that you changed or reconfigured global, you would save the file as default.rdp in your “My Documents” folder. In Vista this is simply called “Documents” to make things easier. Yes, they have gotten rid of the “My” prefix now.
We have all of three options here: Remote Desktop Size, Colors and the Option to diplay the connection bar when in full screen mode. Remote desktop size: whether you want to display your remote desktop connection in full screen mode or not. This does work fer very large monitors, including those widescreen suckers. It will scale down to many other sizes depending on what you maximum resolution is. The amount of colors has now increased to 32bit in the newest version of the Remote Desktop Connection 6 client (RDP 6). This means getting accurate color from applications such as Adobe Photoshop is much easier now, though you will still need to do proper calibration.
The local resources tab controls the way your remote computer or terminal connects to your Longhorn or Windows 2003 R2 Terminal Server. For sound, you have the option to play sound locally, to leave the sound on the remote computer (host) or to ignore sound completely. I have noticed that the sound quality seems tobe much better in the new RDP client, but that it depends on the connection you are using. For example when using a Wifi-B connection, the sound quality appeared to be roughly the same as the previous client iteration. When I then connected the laptop to a wired (LAN) connection, the difference was apparent when switching back and forth between RDP 5 and RDP 6. I should probably be more precise here - what I mean by sound quality appears to affect times when multiple sounds play at once, as well as when sound are triggered by alerts or login notifications, the sounds appear to play faster, having less latency than in the RDP 5 client.
The keyboard menu here allows you to specify whether actions such as alt-tab will always be recognized by the remote computer even when in windowed mode, or if the host should accept them - the host being your computer in this case. I think the default is fine for most people - meaning keep it set to only accept these commands when in full-screen mode.
Local Devices and Resources: RDC 6 supports using local devices will logged into a remote computer provided that the proper driver exists on the remote host. Microsoft will be writing generic drivers for many devices, and currently things like smart cards, serial ports and hard drives are already supported, but the list will be growing.
The programs tab allows you to specify applications to run on connection to a remote host. You can specify the path of the application to run, as well as input information regarding the folder to start the program in.
The experience tab allows you to tweak the connection settings in order to get a less latent (slow updating) connection to your remote host. When people complain about this to me it typically involves things like typing speed not being fast enough in RDP sessions, and screen refreshes being very slow. If you are using a connection to a remote computer in a local network that runs at 100mbit or up, I have found that you can safely have all of the experience options turned on. On a wireless B connection (11mbps), you may want to turn all of the settings off. If you are connecting remotely, I would highly recommend turning all of them off.
There is also an option on the screen that has always looked out of place to me - and I think it should be on the general page as it seems to be a general option. At any rate, you can also specify whether or not to reconnection after your connection is dropped by checking this checkbox. I typically have this checked.
Lastly, we have the advanced tab, which allows you to set so-called “advanced” options. Basically this involves two things.
The first is server authentication. This allows you to confirm if you are connecting to the proper remote computer. In practice, I have found that this simply does not work in Windows XP, and now have it set to not warn me if the authentication fails, because it will always fail, without a doubt. If you use Vista or Windows Server Codename Longhorn, this does in fact work, so you can leave it set to default (”Warn me if authentication fails”).
The second option dubbed “Connect from anywhere” only works with gateway servers, like the new Terminal Services in Longhorn. At this point, you are unable to use the function on Windows XP. You are able to turn it on in Windows Vista, and can play with the settings provided you have a Terminal Services Gateway Server in your network.
Related Articles:
This hack will allow you to connect multiple time to your Microsoft Windows XP machine using an RDP client coming from a Mac, Linux, or another PC like a real Terminal Server, or a Windows Server running Citrix.
In detail, this hack patches many pieces of Windows XP in order to allow the same Terminal Services functionality that you find in Microsoft Windows Terminal Server, but without the licensing costs. The stability of the hack has not been verified, but the virtual machine used has been running for over a week now with 20 conenctions to it and has yet to fail once.
In order to perform the hack you will need one external file, some guts, and a backup. The backup is extremely important. I highly recommend that you test the procedure using virtualisation technoloy like Parallels, Virtual Server (free), or VMWare Server (also free). You have no excuse to procede without a backup - consider yourselves warned.
Let’s begin.
The file needed for the hack is actually a combination of some registry tweaks and DLL/EXE patches made by “antiwpa”. antiwpa is known for dealing with another Windows XP issue that we won’t get into here - I’m sure you can guess what it is easily.
No that you have the file, and backup, we’ll extract it and start the install process. It’s quite simple - you double-click on the application, it starts a command line window, you press a key and the patch commences. Eventually the command line portion will end and you will get a Windows warning regarding system files having been replaced - we’ll cancel the restore “feature”, and let Microsoft know that we are running untested code by pressing the “yes” button on the next window.
A second patcher launches with full GUI this time. We click on the “patch” button and we are finished. Easy huh?
Moving on… If you try to connect to the XP machine now, you will notice that the maximum number of connections has been reached. This is easy enough to fix, but it’s readily apparent where we need to go. Click on Start, then Run, and type in:
gpedit.msc
Once the Group Policy Editor has opened, navigate to “Computer Configuration”, “Administrative Templates”, then “Terminal Services”.
In the “Terminal Services” tree, you’ll see a policy named “Limit number of connections”. Double-click on this policy. Set the policy to enabled, and adjust the maximum connections to suit your need. I recommend trying “2″ to start off with.
Now reboot your machine, and attempt to connect the amount of times you have specified. If you need mre connections, navigate back to the policy editor and set the maximum amount higher.
Once you have completed your testing, back the machine up once more for good measure. If you don’t have disk imaging software, I’d recommend using the open source g4u - otherwise commercial applications such as Symantec Ghost will work.
Moving on, if you feel the need to manage the users (log them off, control sessions) like on a real Terminal Server, you can grab a copy of the “tsadmin.exe” file from a Windows Server 2003 machine’s “SYSTEM32″ folder and copy to the Windows XP machine’s SYSTEM32 folder. Running TSAdmin is as easy as clicking on Start, Run, then typing tsadmin, but you might also want to make a shortcut to the file for good measure.
Related Articles:
Recent Comments