After setting up a new laptop computer with Windows 7 Pro 64-bit, I found that I was unable to access any of my workgroup servers or access my Windows XP workstations. Each time I would attempt to make a connection either using the UNC name and path or using the IP address I would get an error indicating that the spelling was incorrect or that it could not find the location specified. One of the errors I receive is as follows:

Windows cannot access \\{ComputerName}

Microsoft Windows Small Business Server 2011 requires that you use the http://connect in Internet Explorer on all Windows systems. After upgrading a SBS 2003 system to SBS 2011 I needed to rejoin a Windows XP system to the new server, however, when I attempt to run the utility, I received several different message indicating the I could not connect.

One thing that was not mentioned in many of the other technical articles written about this issue is that this particular system was configured with a static IP address and no default domain. After setting the default domain, the http://connect process worked. Normally this would not be an issue if the workstation had been configured with a DHCP address.

Frequently we are called to a new client because of network performance or stability issues. These cases manifest themselves over time by inexperienced data cabling installers, typically the business owner or one of the employees, who attempted to save some money by doing the work themselves.

The installation of data cabling, also referred to as structured cabling, is almost as much an art form as it is a time tested trade that can most effectively be perfected through the training by one with years of experience and formal training in the field.

Have you had the need to test an outgoing port through a firewall to verify that the port was open for outbound traffic? There is a great tool called Outgoing Port Tester that will test any TCP port using a variety of methods. You can use your browser to test most ports using the following URL.

http://portquiz.net/

If you're having trouble getting your Cisco WAP (Wireless Access Point) to connect to its controller, you might notice these symptoms: Wireless device cannot connect, Blinking red, red/green LED, and the device not showing on the controller for Cisco WAPs that use a controller. The Cisco WAPs that have "CAP" in their model number require a controller.

Troubleshooting can be done in this order: reboot, reset to factory defaults, and booting to original firmware.