Weekend IT projects are so fun, especially when I get into uncharted territory. I am doing this myself partly to learn, and also to have some non-medical fun. So I configured my SBS Server, did a few tweaks as suggested by blogs and SBS MVPs, and was going through the steps suggested by the management console. I even signed up a new domain name through GoDaddy although that led nowhere since it takes 72 hours to propagate the new domain name. But there were glitches.
The server could not be seen on the network, nor connect to the internet. After much internet searching, I found that I missed a step the pros thought was obvious. The IP address ranges had to start with 192.168.x,n (and two others). That' not my existing network, so I had to reassign IP addresses to all my computers. Because I am in a production network and this process will likely take many weekends, I went with the non-best practice of keeping the router as the DHCP host instead of the SBS2008 server. The next step will be to individually upgrade all the client computers to Pro versions. I hope it's just going to be time consuming but not challenging, as I plan to do in-place upgrades dictated by the licenses and packages I already have on hand, from XP Home to XP Pro, Vista Home to Vista Pro and Windows 7 Ultimate.
However, I got adventurous and tried to have a spare computer that already has Vista Pro joint the server. Although the server can be seen now as 192.168.1.2, entering
http://connect on the client did not go anywhere. Bert is correct. Sometime even
http://connect is not obvious. Any ideas? Is there an actual IP address instead of the connect command that I can put in on the client?
