You can download the Windows RDP client free from Microsoft's website at http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx. Unfortunately, if you have the client installed but merely lost your shortcut, the install will fail.
Try Start, Run, MSTSC and Ok. If it's installed, it will run.
If you want to recreate the shortcut, the executable is MSTSC.EXE, normally found in C:\\Windows\System32.
Diary of technical happenstance, simple Internet accessible scratchpad, and brain dump to save myself later
Thursday, May 24, 2007
Friday, March 09, 2007
Cisco 7920, a WLC 4404, and WPA
Let's assume you want to deploy 7920 phones on a Cisco "light-weight" wireless network and don't want to deploy a RADIUS or ACS server to authenticate users against. You know WEP is broken, so what do you do?
Use WPA. Notice I didin't say WPA2?
First, get yourself a copy of the latest version of "Cisco Wireless IP Phone 7920 Administration Guide for Cisco CallManager". Make sure it's the latest.
Or...
Using the 7920 Configuration Utility, set the WPA Pre-shared key to your favorite cryptic value. The ASCII field only requires 8 characters, so it's easy for testing. Set the Authentication Type to AKM.
In WLC on your voice WLAN (you do have a seperate one, right?), set Layer 2 Security to WPA1+WPA2. Under WPA1+WPA2 Parameters, check only the WPA1 Policy, only TKIP , set the Auth Key Mgmt to PSK, the PSK format to ascii, and type your favorite cryptic value.
Export your phone configuration, and watch the authentication magic.
Use WPA. Notice I didin't say WPA2?
First, get yourself a copy of the latest version of "Cisco Wireless IP Phone 7920 Administration Guide for Cisco CallManager". Make sure it's the latest.
Or...
Using the 7920 Configuration Utility, set the WPA Pre-shared key to your favorite cryptic value. The ASCII field only requires 8 characters, so it's easy for testing. Set the Authentication Type to AKM.
In WLC on your voice WLAN (you do have a seperate one, right?), set Layer 2 Security to WPA1+WPA2. Under WPA1+WPA2 Parameters, check only the WPA1 Policy, only TKIP , set the Auth Key Mgmt to PSK, the PSK format to ascii, and type your favorite cryptic value.
Export your phone configuration, and watch the authentication magic.
Saturday, February 10, 2007
Access Gnome on Fedora 6 via VNC on reboot.
So I was hoping to use a spare PC as a test bed for some open source apps. I was looking to eliminate any questions as to where a configuration problem might lie and since I didn't have any schedule in mind, I figured I would install Fedora 6, as opposed to running a live CD or a VMWare image.
Without a KVM handy, and not wanting to pile another keyboard / mouse / monitor combo on my desk, I imagined I would run it headless and use VNC or an equivalent for control.
How to access a GNOME desktop on a PC running Fedora Core 6 via VNC without a user logging on locally.
1. Add a user "Joe".
2. Edit /etc/sysconfig/vncservers.
Add:
VNCSERVERS="1:joe"
VNCSERVERARGS[1]="-geometry 1024x768 -depth 24"
This will start an instance of vncserver using display 1, with joe as the user, at a 1024x768 resolution and a 24 bit color depth.
3. Run vncpasswd as Joe to set the vnc password.
4. As root, restart vnc by service vncserver restart.
5. As root, get vnc to start on boot by chkconfig vncserver on.
6. Edit /joe/.vnc/xstartup to include only:
unset SESSION_MANAGER
exec /usr/bin/gnome-session
Run vncviewer from another host, and connect to hostname:5901. You must use the port number 5900 + whatever display number you've indicated in the vncservers file above. You will be running a Gnome desktop as Joe. The user at the Fedora PC will be looking at a user login screen.
Without a KVM handy, and not wanting to pile another keyboard / mouse / monitor combo on my desk, I imagined I would run it headless and use VNC or an equivalent for control.
How to access a GNOME desktop on a PC running Fedora Core 6 via VNC without a user logging on locally.
1. Add a user "Joe".
2. Edit /etc/sysconfig/vncservers.
Add:
VNCSERVERS="1:joe"
VNCSERVERARGS[1]="-geometry 1024x768 -depth 24"
This will start an instance of vncserver using display 1, with joe as the user, at a 1024x768 resolution and a 24 bit color depth.
3. Run vncpasswd as Joe to set the vnc password.
4. As root, restart vnc by service vncserver restart.
5. As root, get vnc to start on boot by chkconfig vncserver on.
6. Edit /joe/.vnc/xstartup to include only:
unset SESSION_MANAGER
exec /usr/bin/gnome-session
Run vncviewer from another host, and connect to hostname:5901. You must use the port number 5900 + whatever display number you've indicated in the vncservers file above. You will be running a Gnome desktop as Joe. The user at the Fedora PC will be looking at a user login screen.
Monday, January 29, 2007
MCS-7825 won't copy OS 2000.4.3(a) image
See bug at: http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCse49574
Apparently, Cisco doesn't know why it happens to some and not to others and there is no way to prevent running into it. When attempting to load OS 2000.4.3(a) on a supported MCS-7825-H2 or the like, everything will proceed until the image is copied o the disk(s). The copy will fail and you'll have to begin the process again.
You can simply keep retrying (it may take a dozen attempts) and ultimately it will work, or follow the steps on the link re: trashing the RAID array. If that doesn't work:
"If perform all of the above steps and this has not resolved the issue, I have also seen it resolved by performing a System Erase from the HP SmartStart CD menu options (when booted from), prior to installing. If you do not have a SmartStart CD, you may be able to perform a similar action in the BIOS menu (F9 on boot-up) to Erase NVRAM/Boot Disk in the Advanced Options sub-menu. "
Nice.
Apparently, Cisco doesn't know why it happens to some and not to others and there is no way to prevent running into it. When attempting to load OS 2000.4.3(a) on a supported MCS-7825-H2 or the like, everything will proceed until the image is copied o the disk(s). The copy will fail and you'll have to begin the process again.
You can simply keep retrying (it may take a dozen attempts) and ultimately it will work, or follow the steps on the link re: trashing the RAID array. If that doesn't work:
"If perform all of the above steps and this has not resolved the issue, I have also seen it resolved by performing a System Erase from the HP SmartStart CD menu options (when booted from), prior to installing. If you do not have a SmartStart CD, you may be able to perform a similar action in the BIOS menu (F9 on boot-up) to Erase NVRAM/Boot Disk in the Advanced Options sub-menu. "
Nice.
Tuesday, January 23, 2007
Cisco 1841 and HWIC-AP-G-A
Although the Cisco.com website indicates all K9 IOS versions support the HWIC-AP-G-A, you must still use the T-train versions. Last success was using c1841-adventerprisek9-mz.124-2.T2.bin, verses new and improved but not supportive version c1841-advipservicesk9-mz.124-12.bin.
During boot you'll see UNKNOWN CARD in slot X if not supported.
During boot you'll see UNKNOWN CARD in slot X if not supported.
Subscribe to:
Posts (Atom)