How to setup a Home Wireless Router

1. Wireless setup is fairly easy and not too complicated. The major steps are Power, connection to the Internet via a provider and configuring the router via the Admin Tool.
2. 1. To start, You will need to plug the wireless router into an electrical power source, then push the power button located in the front or rear of the Router(Depending on the Model).
3. 2. Connect the Internet Cable modem to the router. Plug into the router jack named WAN, UPLINK or Internet. 
4. 3. Power the router off and back on. This ensures that the Modem passes the correct information the router.
5. 4. Connect one computer to the router. Once a wireless router installation is complete, the computer can be changed over to a wireless connection if desired.
   
   
6. 5. Open the router's administration tool. From the computer connected to the router, first open your Web browser. Then enter the router's address for network administration in the Web address field and hit return to reach the router's home page. This is usually 192.168.1.1. Check the Routers guide for verification. This can also change depending on the Cable providers IP address configuration. 
7. 6. Log in to the router. The router's home page will ask you for a username and password. You may need to check the routers instructions for clarification. Remember to change the router's password for security reasons. 

1. 7. If you want your router to connect to the Internet, you must enter Internet connection information into that section of the router's configuration.
   
2. 8. If this is a wireless router, change the network name which is called the SSID.The router comes with a network name set at the factory, you will want to change this to a different name. 
3. 
   
4. 9. Verify the network connection is working between your one computer and the router. 
5. The best way to verify this is to open your Web browser(Chrome, Internet Explorer, FireFox) and visit a site such as www.google.com or www.yahoo.com. If the pages appear you are connected. 
6. 
   
7. 10. Verify wireless is working by connecting additional computers to the routers wireless Access. You have to change the network name (SSID) of each computer to match the routers name that you set above.
   
8. 11. REMEMBER to configure additional network security features as desired to guard your systems against Internet attackers and Hackers. The Wireless network must have security such as WEP,WAP to protect against intruders. 

1. 
   

Installing Vmware 5.5 Process

I attempted to load/Upgrade my Vmware 4.x to 5.5. After a few struggles, I finally completed the installations. These instructions may assist you in completing the process with minimal issues. 

Place the DVD into your server

2. The installation files will continue to load.

3. You will see the the OS VMKernel is loaded. 

4. The welcome screen will appear after the load.

5. Press F11 to Accept the License Agreement 

6. At this point you will need select a primary disk which will hold the VMware ESXi files. 

7. You can retrieve information here by selecting F1

8. If files already exist (As in my case) you will have an option to either upgrade and keep the old files or  select a clean install. The Clean install will overwrite all files. 

9. Select the language.

10. Set the password for the “root” user account. The installer does not enforce or warning you about complexity, However, I would recommend a complex password. It is ok to select a basic password but remember to change it later. 

11. You may receive warnings if you are working on a very old server or a server who settings have not been correctly configured.

12. Finally, you are given one last chance to abort the installation.

13. The the installer will copy the software to the disk/volume/LUN you selected earlier.

14. At the end of the install pressing [ENTER] will trigger a reboot – be sure to eject or close any mounted .ISO or physical DVD in the server.

15. After the reboot is completed,  you should see the VMware ESXi . This allows a number of post-configuration tasks to take place, and also be used as one method of troubleshooting an ESXi host if become unresponsive. You will have to setup the correct network and IP configuration after the install is completed. 

Terminal Server Not Using Saved Credentials

Terminal Service client not using saved credentials

I had this problem for quite a while now, and it finally bothered me enough to go and search for a solution. I was trying to change this on the Server (Host Computer) but it worked by changing the issue on the client side (Windows 7). All along I was focusing on the host. This should work in other scenarios also. (Windows 7 to 2k3, XP to 2k8, etc.)

I use TS client to connect with smartcard from my home Vista machine to various machines at work through a Terminal Services Gateway. 

When I'm connecting to Windows 2008 I am was receiving this error   On this machine, TS(RDP)  fails with the following message: "Your credentials did not work. Your system administrator does not allow the use of saved credentials to log on to the remote computer because its identity is not fully verified. Please enter new credentials." 



 I've searched the net for the exact error message but I could not find a solution. So I ended up asking the experts...

It turned out that my issue was described in this article from Terminal Services Team Blog, under Scenario 1 (Problems using saved credentials with Windows 7 RDP clients - Connecting remotely via RDP to a  server ). 

Fortunately there is a solution by altering the TS settings on the client side (this solution is not as secure as using certificates on server for server authentication).
In Vista, the Credential Security Support Provider protocol (CredSSP) adds a couple of group policy settings that are described in detail in MSDN CredSSP group policy settings page.

The following fixed the problem:

1. Log on to your local machine as an administrator.
2. Start Group Policy Editor - "gpedit.msc" and accept the UAC prompt.
3. Navigate to "Computer Configuration\Administrative Templates\System\Credentials Delegation".
4. Double-click the "Allow Saved Credentials with NTLM-only Server Authentication" policy. 
5. Enable the policy and then click on the "Show" button to get to the server list. 
6. Add "TERMSRV/" to the server list, in my case TERMSRV/alinc02.redmond.corp.microsoft.com. Using one wildcard (*) in a name is allowed. For example to enable the setting on all servers in "microsoft.com" domain you can type "TERMSRV/*.microsoft.com".
7. Confirm the changes by clicking on the "OK" button until you return back to the main Group Policy Object Editor dialog.
8. At a command prompt, run "gpupdate" to force the policy to be refreshed immediately on the local machine (although this changed for me after a while)



With this policy enabled, the login to my Windows 2k8 machine now works perfectly.