24 December 2006

Microsoft.com running on MOSS ‘07

The word is out… Microsoft is moving www.microsoft.com to a Microsoft Office SharePoint Server 2007 based infrastructure.
It was published on the MSPreview site. Check out the last answer on the page.
The following is the most relevant text.
"In the background we are beginning to migrate much of Microsoft.com to a new platform based on Microsoft Office SharePoint Server 2007. Using Office SharePoint Server 2007 will bring us a broad range of new capabilities that will help you more easily find the information, products, and services you're looking for across our site. Microsoft.com is the 5th most visited Web site on the Internet, hosting hundreds of thousands of pages of content. Running our site on Office SharePoint Server 2007 goes a long way in demonstrating to customers worldwide that the product is reliable and provides an effective solution for managing vast amounts of content."
Now THIS is what I call eating your own dog food! J

20 December 2006

Configuring two Linksys WRT54GL routers on the same home network

In today's world of wireless routers, 802.11g is the new standard, but 802.11n is poised to take over in the near future, if they can ever ratify the standard. J
Of course, manufacturers have focused on making router setup really easy.
Router security is a whole different ball game all together…
If your house is like mine, you have your high speed internet modem and the main wireless router setup somewhere in the house.
For most people, the coverage a standard 802.11g router provides, and their usage model, makes it a very acceptable solution.
Of course, I'm not most people… and my needs and setup isn't standard either.
OK, some history first. My main router is setup in my server room in the basement.
It worked well at first, at least for most things.
See, I'm a Madden gamer and playing Madden with my friends require the fastest possible connection.
Because of the fall off in signal strength and quality over distance, I was only getting about a 20 megabit connection with 40% signal strength.
As any Madden baller will tell you, that makes for a really jerky and unenjoyable game.
So, for a long time I was stuck trekking down to the basement when I wanted to play.
Then I got my Replay TV's. Of course I had to soup up my Replay TV's before using them, but the point just being that I had to find a way to stream my shows between the 2 Replay TV's I had as well as the DVArchive I had running on my data server.
At first I tried the wireless route but no matter what I did, I simply could not get the wireless access points to work with the wireless extender which I needed to get a strong signal from the back of the basement to the front of the living room which, of course, are on exact opposite sides of the house.
In the end, I returned the extender and access points and went the old fashioned way by running a hard wire CAT6 cable all the way through.
So now I had my DVArchive server in the server room in the back of the basement, my Replay TV in the media room in the front of the basement and my Replay TV in the living room on the main level all connected together.
Then it dawned on me… I have a connection (to the Replay TV) right there in the living room where we spend most of our time.
If I simply hooked up a wireless router and then connected the Replay TV via hard line to the router, I would have the best signal strength and quality possible, given the 10 feet to the couch.
Of course, it was easier said than done. There were a couple of snags I had to work through first, most notably the fact that Linksys had changed the firmware on the WRT54G wireless routers to a proprietary format, as opposed to the Linux based firmware which allowed users to flash their routers with all kinds of cool firmware updates.
Fortunately, hearing the outcry from the community, Linksys released the WRT54GL which was again Linux based. OK, enough background, let's actually get this thing working by following these steps…
  1. Our starting point assumes that the first wireless router is already setup on the network.
  2. Connect the second wireless router to the network.
  3. Power up the second wireless router.
  4. On your laptop, go to the Wireless Network List and ensure the new router is picked up in the list.
  5. The new router should show up as "linksys".
  6. Select the router and click the "Connect" button.
  7. You will get a warning dialog window stating that the network is unsecured.
  8. Click the "Connect Anyway" button.
  9. Your system should now connect to the router and start pulling an IP address.
  10. Once your system has successfully acquired an IP address, the status should change to Connected.
  11. Open a command window.
  12. Do an ipconfig.
  13. All things being equal, the router would have assigned you the default IP address of
  14. Open Internet Explorer.
  15. Navigate to which is the IP address of the router itself.
  16. You will be presented with a logon dialog window.
  17. The default UserID/Password combo for the Linksys WRT54GL is used to logon.
  18. Leave the User name field blank.
  19. Enter "admin" into the Password field.
  20. Click OK to logon.
  21. On the /Upgrade.asp page, click the "Administration" menu tab.
  22. Click the "Firmware Upgrade" sub menu option.
  23. Click the Browse button to locate your choice of firmware and conduct the upgrade. My preference has been the Tarifa version b009. You can get your firmware of choice from the Linksys Info site.
  24. Once the firmware upgrade is complete, click Continue to proceed to the next step.
  25. You will notice in the top right hand corner that the firmware version has been updated.
  26. Now that we have updated the firmware, it is time to secure the router. Click on the Administration tab again.
  27. It should default to the Management sub tab, but if not, click the Management sub menu option to navigate to the desired page.
  28. Start by entering a new Router Password.
  29. Enter the same password in the Re-Enter to Confirm box.
  30. For added security, you should not allow the router's admin pages to be accessed over standard HTTP so select the HTTPS check box and ensure that the HTTP check box is unselected.
  31. Ensure that Wireless Access Web is enabled.
  32. Ensure that Remote Management is disabled.
  33. Select Enable for the UPnP option.
  34. Select Disable for the Telnet option.
  35. Before you save your changes, remember that you are currently logged into the router via HTTP. Once you save your changes, the router will no longer recognize your session. Save your changes.
  36. You should end with a Page Cannot be Displayed page.
  37. Change the URL of the page from to
  38. You will be prompted to logon again.
  39. The User Name field now becomes "admin".
  40. Enter the password you used in the Password field and click OK to logon.
  41. Because you are now accessing this router via SSL, it will attempt to give you a certificate. You will receive a warning dialog window.
  42. Click the View Certificate button.
  43. In order to avoid having to deal with the SSL certificate issue each time you logon to the router, click the Install Certificate button.
  44. The Certificate Import Wizard will open.
  45. Click the Next button.
  46. You will be prompted to select a certificate store.
  47. This is Greek to most people, so just ensure that the Automatically option is selected.
  48. Click Next.
  49. On the final screen, click the Finish button to complete the import.
  50. You should be presented with a confirmation dialog stating the import succeeded.
  51. You will be returned back to the logon screen.
  52. Enter "admin" in the User Name field.
  53. Enter the password you previously selected in the Password field.
  54. Click OK to logon.
  55. You may now be presented with the following page.
  56. As you can see, the page did not render properly. The reason for this is because IE treats the same page over SSL as a unique version so you have to reset your security settings in IE again.
  57. In IE, click the Tools menu option.
  58. On the dropdown menu that pops up, select the Internet Options item.
  59. You will be presented with IE's Internet Options dialog window.
  60. Click on the Security tab at the top.
  61. Select the Local Intranet icon.
  62. Click the Sites button.
  63. You will be presented with the window to add sites.
  64. If the router URL is not automatically entered into the first edit box, enter the full value of "" into the edit box.
  65. Click the Add button.
  66. The site should now be listed in the Web Sites list below.
  67. Click Close to close the dialog window.
  68. Click OK to close the Internet Options window.
  69. Now click the refresh button to reload your router admin page.
  70. You should now see the normal page loaded successfully.
  71. You should notice the security zone indicator in the bottom right of the page indicating "Local Intranet".
  72. The next step in securing your router is to turn on MAC address filtering. The MAC address is a unique serial number that is given to each wireless network card. No two in the world are identical.
  73. In order to get your MAC address, return to your command window. If you had closed it, open another command window.
  74. Use the "ipconfig /all" command.
  75. You will notice some hex numbers for the Physical Address.
  76. Write down this value.
  77. Go back to your router admin page.
  78. Click the Wireless tab.
  79. Click the Wireless MAC Filter sub tab.
  80. Select Enabled for the Wireless MAC Filter option.
  81. Select the Permit Only option. This option will only permit computers with the MAC addresses you specify to access the network.
  82. Click the Edit MAC Filter List button.
  83. The Add MAC Address Filter List window will open.
  84. Enter your MAC address that you had previously written down in one of the open edit boxes.
  85. NOTE: Replace the "–" characters in the value with ":" characters instead i.e. 13-57-90-AB-CD-EF would be entered as 13:57:90:AB:CD:EF instead.
  86. Save and close the window.
  87. Next we need to configure wireless security. Click on the Wireless Security sub tab under the Security tab.
  88. Select WPA Personal for the Security Mode field.
  89. Select TKIP for the WPA Algorithms field.
  90. Now enter a WPA Shared Key value. This is essentially your password for the wireless network.
  91. Click the Save Settings button.
  92. Once you save the settings, you will once again be disconnected from the network.
  93. Go back to your wireless network list.
  94. Your router should be listed.
  95. Select your router and click the Connect button.
  96. You will be presented with a logon dialog window.
  97. Enter the value you used for the WPA Shared Key in step 90 into the Network Key edit box.
  98. Re-enter the same value in the Confirm Network Key edit box.
  99. Click the Connect button.
  100. Now that your router is secured, we need to hide it for extra security.
  101. Click the Basic Wireless Settings sub tab under the Wireless tab.
  102. Select a Wireless Network Mode. I prefer G-Only as it forces the fastest connection and will generally not connect me if I'm too far away and the signal is too weak.
  103. Now the important setting is to change the Wireless Network Name(SSID) value, which defaults to WRT54GL to something that makes sense to you. This is important when you have multiple routers so you can distinguish which router you're logged onto and administering e.g. you might use "ComputerRoom" and "LivingRoom".
  104. Select the Wireless Channel you wish to use. I would just let it default to the 6-2.437 GHz value.
  105. Ensure that your Wireless SSID Broadcast option is still set to Enabled. We will need this in order to logon to the new network SSID.
  106. Save your settings and click OK.
  107. Because you just changed the SSID of the network, you will now be disconnected from the network again. Go back to your Wireless Network List. Your new SSID should be listed.
  108. Select your new network and click the Connect button.
  109. When presented with the logon dialog, use the credentials you used earlier to logon again.
  110. Click the Basic Wireless Settings sub tab under the Wireless tab.
  111. Here's the important part, change the Wireless SSID Broadcast setting from Enable to Disable. This is important because it keeps snoops at bay. By already changing the SSID you not only identify your router better, but it also makes it harder for someone to attempt to logo to your network because they have to know your SSID to do so. By turning the SSID broadcast option off, nobody can see your network. That's OK because you've already configured your computer for it. It just keeps war drivers and nosy neighbors from trying to use your network.
  112. You can leave the other options as is and save your settings.
  113. Your network will now no longer show up in the available network list of other computers in the vicinity. It will still show up in yours because your computer has been configured to access it.
  114. Now that we have the router configured, we need to make it work with the original router. The problem using this router at this point is that you can get an IP address, but you cannot get any internet connectivity.
  115. Click the Setup tab.
  116. It should default to the Basic Setup sub tab, but if not, just click the Basic Setup sub tab.
  117. I'm going to assume that your original router does not operate on the default 192.168.1.x range because changing the second and third nodes adds yet another layer of security, this time security through obscurity. Anyway, let's assume the original router has it's IP set to It would be configured to hand out IP addresses starting at 100 i.e. the first computer connecting to it would get as an IP address. That makes the range below 100 safe. If you have configured it to start handing out IP's starting at 2, you need to change it to 3 or more.
  118. Change the Local IP Address of the second router to
  119. Ensure that you select the Disable option for the DHCP Server setting. This will allow the second router to serve as the slave to the first router. It will pass your computer's IP request over to the first router who will return an IP which the second router will give your computer. In this way, the second router acts as a relay between your computer and the first router. The advantage to this is that it will relay internet URL requests to the first router which is connected to the outside and will process the request sucessfully.
  120. Save your settings.
  121. Comparing these settings with the first router:
  122. You will notice that that IP is different and that the first router is set as the DHCP Server.

And that's all there is to that.
Quite a lengthy walk through, but it covers EVERYTHING! J
Anyway, with my new setup I can play Madden at full speed, 54 megabit @ 100% signal strength!

18 December 2006

X1 is in… WDS is out…

I'be been documenting my woes with Windows Desktop Search indexing seemingly not ever getting done. It seems like WDS would index the files and then when I reboot my computer and restart Outlook, WDS starts the indexing processing all over again. On 12/16, there was only 7,407 items left to scan. But then on 12/18 the count has again increased to 131,687. So, I finally gave up. I originally used X1 Desktop Search when I started on the Office 12 beta cycle and had to install WDS. I did not want to have 2 indexers running on my computer so I went with WDS for the past 15 months. Two years ago when I bought X1 it was $80 for a client license. Today it is now the X1 Enterprise Client and it is FREE! Anyway, I had experimented and found out that I can actually uninstall WDS so I decided to at least try something different. I uninstalled WDS and installed XEC. X1 began indexing right away… And within less than 1 day, a work day with a heavy work load, indexing was complete. The X1 indexer also is much less resource intensive and allows much better flexibility in configuration to make it less obtrusive. So, I'm back using X1 again… at least until WDS gets fixed. J Later C

SharePoint Remote Event Receivers are DEAD!!!

 Well, the time has finally come.  It was evident when Microsoft started pushing everyone to WebHooks, but this FAQ and related announcement...