Sometimes it’s handy to find out who is logged on at a remote Windows computer. For example, before rebooting a critical server after hours, you might want to make sure your boss isn’t logged in at his computer.
In Linux, this is easy. You simply login to the remote computer with ssh (or telnet…yikes) and run the who command. For example:
me@bosscomputer:~$ who
boss tty7 2008-10-16 07:57 (:0)
me pts/0 2008-11-14 15:25 (mycomputer)
In Windows, I found two ways of doing this. Both ways work with Windows XP and Windows 2003 (and perhaps other versions too). …Continue reading » How to Find Out Who is Logged On at a Windows Computer
Sometimes it’s useful to find out the uptime for a Windows computer. For example, if you are rebooting a whole bunch of Windows computers and you aren’t careful about keeping track of which ones you have just rebooted, you can check the uptime.
In Linux, it’s easy to find out how long a computer has been up and running. You just runtime the good ol’ uptime command. For example:
me@mycomputer:~$ uptime
09:17:32 up 23 days, 19:13, 3 users, load average: 0.36, 0.54, 0.49
In Windows, it’s almost as easy but not quite as intuitive. …Continue reading » How to Find Uptime in Windows
So we just started using Windows’ Distributed File System (or DFS for short). More specifically, we have been using the DFS Namespaces portion of DFS, which basically allows you to have one virtual share point to one or more underlying physical shares on any arbitrary physical server.
In theory, this level of indirection makes maintenance easier because on the client side you can map a drive letter to the virtual share, allowing you to change the physical share behind the scenes without any configuration changes on the client. For example, you could have a virtual share called \\myADDomain\corp\files that is configured to point to the physical share \\myFileServer\files. On the client, you can map a drive letter (e.g. Z:) to \\myADDomain\corp\files. Behind the scenes, that gets translated to \\myFileServer\files when the client uses the drive letter.
Today a user got the following error when logging into his Windows XP Pro machine: “An error occurred while reconnecting Z: to \\myADDomain\corp\files. Microsoft Windows Network: The system cannot find the file specified. The connection has not been restored.” …Continue reading » Windows DFS Brain Damage
Are you having problems getting Bart’s Boot CD to recognize the Broadcom NetXtreme 57xx Gigabit Controller network interface card?
I work with some Dell computers (models: Optiplex SX280, Optiplex GX620, Precision 690 and Precision 370) that have this NIC and the current version of Bart’s Boot CD is unable to recognize it. The automatic NIC detection fails with a message to the effect of “could not find any device, you can try manually selecting a driver” (sorry, I can’t remember the exact error). …Continue reading » Bart's Boot CD with Broadcom NetXtreme 57XX Gigabit Controller
