Installation went pretty smoothly and everything looked fine – until I went to open the shared folders from my main PC -

Cannot Connect. The Network Path Was Not Found.

Interestingly the supplied “console” software would quite happily list the folders being shared, but connecting to them failed. It appears that MS is using newer web technologies to provide the information about what’s available, but use older local area network technologies to actually connect to the shared resources. This is fair enough – if it works!

I checked and discovered that Microsoft had supplied a connection troubleshooter with their Home Server Toolkit. I installed and ran that and it advised me -

No DHCP server, or DHCP server is not reachable

A DHCP server was not detected, or the test cannot communicate with the DHCP server.

By default, Windows Home Server gets its IP address configuration from a DHCP server that is on your home network. Normally, the DHCP server is located on your broadband router. Without the DHCP service, your computers cannot get their IP address configuration and cannot communicate with each other.

To fix this problem, ensure that your broadband router is powered on and is connected to the network. Also, ensure that your broadband router is configured as a DHCP server.

Alternatively, you can assign static IP addresses to all computers that are on your network, including your home server. You need advanced networking knowledge to do this. If you assigned static IP addresses to the computers that are on your home network, you can safely ignore this issue. Look for other others issues, particularly name-resolution issues.

For more information about Windows name resolution, NetBIOS, HOSTS files, and other name-resolution possibilities, see “Host Name Resolution” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=98161)

Okkayy … I understand that. I’ve been involved with TCPIP network for almost 20 years. I also know that their assumption “Normally, the DHCP server is located on your broadband router” is often false in this part of the world. I have a direct 100Mb ethernet connection to the ISP, as do many folk in the major cities of Sweden. The ISP, Bredbandsbolaget, supplied me with a wireless bridge to provide WiFi access and additional ports for my various PCs – but all of them get their IP addresses from the ISP’s DHCP server – not from the bridge or a router.

I understand all of this. But how many “normal” people do? So what would be the next step? Click on the link supplied for further help I guess. Go on, click on it – http://go.microsoft.com/fwlink/?LinkID=98161

Now seriously, how many “average” home users, the target group for Home Server, are going to understand even a few sentences of that? And even if they did, it doesn’t provide an answer! You need to be a network engineer to solve it.

Or if you’re lucky and googling “Windows Home Server” and “network path not found” you might find this post!

The solution is actually quite simple. When your PC connects to a DHCP server to get it’s internet address, it also gets some other settings. It’s more than possible those settings will not be appropriate for Windows Home Server. In particular, my error was caused because NetBios over TCP/IP was not enabled. This is a way for computers, usually on a local area network, to talk to each other over an “internet” based network. It’s set either via DHCP or in the “advanced” settings of network connections. In Windows Home Server you can reach it by clicking Start then going to Control Panel/Network Connections/Local Area Connection. Click Properties, then select Internet Protocol (TCP/IP) then click Properties and then Advanced. Once there, click on the tab labelled WINS. At the bottom you’ll find NetBIOS setting. The default is to get the setting from a DHCP server. If that’s not working, change it to Enabled and click OK.

You may need to make the same changes on your Client PCs, it will be in much the same place.

Hopefully that helps someone.

UPDATE: After a while the above “fix” stopped working for me. It appears, though I’m still not 10=% sure, that my Vista PC was deciding whenever it rebooted to be the Domain Master Browser and not doing the job properly – stopping itself and other PCs being able to connect to the Home Server. Setting the IsDomainMaster parameter in the registry to false seems to have solved it.

As always though, migrating websites to new servers can be challenging. In this case I was moving from IIS6 to IIS7 plus upgrading to the latest versions of PHP and MySQL. In addition, Asgard was using the Helm control panel for website management. The originally developers of Helm, WebHostAutomation, offered a free 5 client licence for Helm and this would have been ideal for maintaining my sites – but unfortunately Helm was bought out by Parallels and they’ve dropped this deal. While I could just maintain the sites through Windows, I liked the simplicity of a control panel and have decided to give DotNetPanel a go. DotNetPanel has a free 5 client licence!

DotNetPanel proved relatively easy to setup, though there was of course a learning curve . With PHP I was eager to test the new FastCGI capabilities of IIS7 and I found a great walkthrough on IIS.NET.  The first site I migrated was fittogether.eu, a new health based social network site based on Joomla we’re developing. It worked perfectly. I then migrated mlmfacts.net, a wiki I’m setting up to try and track all the different companies in the multi-level marketing world, and that’s where problems began – it simply wouldn’t work, complaining about not being able to load various “includes”. I then tried setting up a wordpress blog (this one!) at david.steadson.com and encountered almost the same issue.

After several hours of digging (and I’m not a PHP programmer) I eventually narrowed it down to a problem with the PHP function realpath() not providing the correct answer. I won’t go through the details here, you can read a bit about it on the iis.net forums where I reported the problem, but eventually I discovered the issue was actually with how DotNetPanel sets up websites. A site like this wordpress blog is installed in c:/HostingSpaces/David1/david.steadson.com/wwwroot. Various folders for logs and backups etc are placed in c:/HostingSpaces/David1/david.steadson.com. This isn’t a particular unusual setup, on Helm for example the site would have been in c:/HelmSites/david.steadson.com/wwwroot.

So what was the problem? Well, by default Helm gives access to the account folder, /david.steadson.com, to the user account the web service runs under. On a default IIS7 install folk tend to setup their sites under c:/inetpub and this directory also has read permissions for the web service. DotNetPanel on the other hand did not give this permission and I eventually found others who had reported similar problems. Adding the permission allowed the sites to work fine!

The only other “challenging” migration task was setting up “friendly URLs”. At Asgard we used a commercially IIS6 isapi module called isapi_rewrite that allowed websites to do URL rewriting using .htaccess and much the same syntax as used on *nix with mod_rewrite. This year though, Microsoft released a free IIS7 module, URL Rewrite, which does much the same thing, though with different syntax. Thankfully it comes complete with an “import” tool for importing mod_rewrite style rules and it’s working a charm.

So far I’ve migrated my various Amway hobby sites – www.amwaywatch.com, www.amwaytalk.com, www.thetruthaboutamway.com, and www.amwaywiki.com, next step is some of my other business sites and a handful of friends websites! I’ve requested Server Beach shutdown the server they’re on in the middle of next week, so I’m on a deadline ….