HAHAHAHA! AAHAHAHAHAHAHAHAHAHAHAHA!!! HAHAHAHAHAHAHAHAHAHAasr$#!^T!$%#D@# -- NO CARRIER.

And yes, I'm running five boxen at home. Seven when teh wife and I curl up in front of the TV with our work laptops in the evening.

~
There is absolutely no correlation or causation amongst intelligence, power, talent and wealth.
Kha-Nyou

I've got my main server and my work laptop. Not sure if the latter counts. Then there's my wife's MacBook that last night decided it wanted to boot to a terminal screen (probably because the FoML knocked it off a table a couple days ago.) Then there's the old iBook that is in theory the FoML's, though it only gets used every now and again. There's the Windows box which hasn't been on in two months, but which I've long intend to get working properly "tomorrow". There's the NAS, which one could easily argue actually is a computer as it runs linux. Finally, there's the Playstation 3, which has more computing power than any of the boxes I just listed.

So depending on how you count, it could be anywhere from 1 to 7.
----
_{ウセーバラケダ}

Don't they have a system administrator that knows how to check for network problems? You know with a network sniffer gizmo or something? Could it be that they don't want to check for network problems because they are trying to cover up their asses for having 60% of the network cables being connected incorrectly?

Let me tell you from experience how it goes:

#1 Employee tries to run $OurBigApp and it does not connect to the server. Calls the help desk.

#2 Help desk answers, asks questions from a script and wastes a lot of time checking system settings, etc. The script does not have an answer so they babysit the Employee for a while and create a trouble ticket and mark it as a "software error" and not a "network error" because they really don't know the difference between them. After all when an Employee gets a "File FUTZ1234.DLL is missing or invalid" it is an obvious system problem that a technician should handle and check the FUTZ1234.DLL file, but the help desk doesn't know their ass from their head and write it up as a "software error" anyway. Basically no critical thinking here at all, everything is a software error and woe be to the programmer when that happens.

#3 Help desk writes a "please assist" form email to the programmer.

#4 Programmer gets email, writes back that it is a "network error" and 60% of the traceroutes fail as well.

#5 Help desk writes to system administrator, who covered his ass and blames the software and blows off the whole trouble so he can surf the web.

#6 Help desk writes a "please assist" to the programmer, who forwards it to a manager that it is a "network problem" and the system administrator isn't doing his job.

#7 manager writes back to programmer that it is a "communication issue" with the programmer and just fix the software. Then the manager goes to check her stock portfolio on the Internet.

Now you have to play "Sherlock Holmes" and solve the mystery. Gather up evidence that proves 100% that it is indeed, yes, a fact, that the network has connection problems, and by process of elimination it cannot be the software, but the network who done it!