Jason Nadal

I've been looking into the inner workings of Longhorn 4074, and have discovered there's much more here than meets the eye (or keyboard).  I'm sure a lot of this is under wraps because it's not MS' way to put forth something that's not usable yet (see the hidden windows manager command for an example of this -- it's cool, but it's not working for all video cards, slow, etc...but still in development).

My saga with how to fix your network connection after it goes haywire in Longhorn.

I had read about network connections being broken under Longhorn, from builds 4051 through the current WinHEC 4074, but hadn't yet experienced the fun learning experience (spoken slowly through clenched teeth) that it would afford me further down the road. These are my experiences; I hope that they help someone else out as well.

I wanted to get to Longhorn remotely via terminal services, so I installed both Terminal Services, as well as the web server component that allows access from http://[ip]/tsweb .

I had a friend test out the connection, he said it was cool, so I had thought it was in the bag. Fast forward through headaches by the name of Magic Packet and VPN... finally success -- I can VPN remotely, and send a packet from within my network to the broadcast address. Only... I can't seem to get to the machine, even just to ping it. I get home, and the machine is turned on all right, and waiting at the login screen, but when I log in, there's no network connection... router's fine; even the machine works when I boot into XP instead of Longhorn.
Fastforward days ahead, many headaches, and I'll spare you the litany of “please work now” and various degrees of anguish, and head to the miracle cure.

I'm not a network guy; I just play one at home.

Sure, I can set up a fairly secure network at home, keeping my machines fairly happy with their little cable-modem tether, but as far as going into routing tables, I had a few things to learn, and still do. However it was checking the differences between the routing tables that led me to my solution. First off, I checked the properties of my LAN connection in network properties; good ip from the DHCP, and I can get to my router by going to my 192.168.0.1 address, but as far as going any further -- forget it. Manually setting IP, and DNS didn't help either. I could resolve the name, but not any hits from a "ping www.google.com". There's not a default gateway...instinctively, I know this is the problem -- 100% positive; but how to manually set the gateway?

Enter "route print". Here's the bad table;



It looks ok, but no gateway declared. I'll save you the why and how, but what I did was compare my working xp table w/ the nonworking Longhorn one, and was going to go 1-by-1 and make them match, but the first add was the one that did the trick. First off, the interface (the last number in this command) is the number of the LAN card when you type "route print". The command to fix it?

route add 0.0.0.0 mask 0.0.0.0 192.168.0.1 metric 20 if 3

Note that 192.168.0.1 needs to be changed to whatever the router address is. Then you should be golden. Here's what your router table should look like afterwards:



Enjoy being back connected!

This photo is priceless!

I say “optimization” because this may remove features that could be important to you if you are a developer, but the authors of the pdc Longhorn Optimization Guide, under the noms de plume Chris123NT and Nighthawk,  have written another one for build 4074.

Visual Studio 2005 Team System Documents

MS has just published a cache of useful info about visual studio team system 2005; check them out!

• Overview
• Microsoft Solutions Framework
• Software Project Management
• Enabling Better Software Through Better Testing
• Enterprise-Class Source Control and Work Item Tracking
• Designing Distributed Systems for Deployment
• Class Designer
• Extending VS System Suite
• Building Robust and Reliable Software

As Wally McClure posted first, the MS speech sdk version 1 is released, and is available here. The download ran me 295mb, and contains extensions for VS2003, enabling users to create SGXML (speech grammar xml files) therein.

With 4074, Terminal Services doesn't get it's own element in add-remove programs. However, since IIS is not installed by