It is not uncommon for developers new to using Virtual Machines to use Microsoft Virtual PC LAN connectivity in a manner that inhibits their development goals. This practice can not only lead to personal frustration by forcing the developer to take more complicated steps than is necessary to accomplish common goals, but it may even cause the developer to lose valuable time and peak development capabilities, resulting in slowed productivity, reduced 'eureka' moments and even one's job in extreme cases. This article pursues positive solutions to the problems posed by bad LAN connectivity practices in multiple examples.