Hi Philip,
Well, I should be careful how I word things. I have had a couple of issues that support has been able to help me through. I don't want to say they can't. I am only saying that network issues are sometimes tougher than simply fixing AC issues, because they can sort of "get their hands around the AC program" while it is difficult for them to know exactly what the network is about.
Case in point. As you may know with some Microsoft servers and client OS, attaching the computer to the domain is a easy as opening your browser and typing
http://connect. It then does the rest, attaching it to the domain, setting up DNS, etc. Well, the other day, I set up a Windows 2008 Server as a "sandbox" to play in. I had to manually attach it to the domain. I did this, and it showed that it was attached to practice.local and its full DNS name was Sandbox.practice.local. It could see all the computers on the network including the production server, but it couldn't connect. It turns out that the default login screen was Sandbox\username which allowed me to log in, but it was really logging into the workgroup account. Once, I realized my mistake and logged in under Server_name\username, everything went fine. So you can imagine having AC on there and trying to connect to the server. Just an example. Maybe a poor one.
