Bad terminology on my part, the 'main' computer is the client computer that sits on my desk and I use the most thus labeled 'main'; in it's past life (like 3 weeks ago) when I ran a peer to peer network it was the AC server but alas, demoted to being a client with the privilege of being part of the servers domain . Thought about taking said 'main' computer out of the domain and then reconnecting it to AC on the server to see if unencumbered by domain policies AC would be faster but not that adventurous.

After I installed the server and loaded AC and AC database on server and before connecting any client computers to server I uninstalled AC and it's database from the 'main' computer, then reinstalled AC on 'main' computer then connected 'main' computer to server as part of servers domain.

The server motherboard has 4 NIC RJ-45 connectors(Intel i210-AT) (not using a separate card), only using 1 which connects the server to the switch so the hardwired 'main' client and the wireless non-domain client(Surface Pro 2) eventually come to the server via the same port.

Can't imagine the smart component of the Intel i210-AT decides to give a faster speed to requests it senses came from a wireless device than from requests from a wired device that has a gigabyte NIC connector(said 'main' computer) although checking the NIC on 'main' may be in order.

Well since the Nursing home called me twice in the middle of the night and couldn't get back to sleep did take a trip to the office and did take 'main' off the domain reconnected to AC on server no improvement in speed.

Then looked at the NIC on main, it is a gigabyte NIC with 'advanced options' component that allows different configurations speed packet size etc. played around with some settings still no better. Maybe it is the AMD CPU that is the problem?