First, that calibre debug log isn't complete. According to it neither the content server nor the wireless device are started, which according to the CC debug log isn't true. It might be useful to get a complete log, especially given what I see in the CC debug log.
The CC debug log says that CC can locate calibre and get an IP address, both for the content server and the wireless device, which rules out problems with the WiFi router. However, CC cannot actually connect to either of them. The usual reasons for failing to connect after successfully locating calibre are the firewall and the antivirus SW on the computer running calibre. Paragraph #1 in the FAQ
How do I setup Calibre Companion to connect to calibre? discusses how to check the firewall. NB: a complete calibre debug log would almost certainly verify what CC is saying, that during a wireless device connection attempt calibre responds with the IP addresses but does not receive the subsequent connection request.
As mentioned in paragraph #2 of our FAQ, many antivirus packages, sometimes called network security suites or other things, prevent CC from connecting to calibre. We have seen problems with (at least) Norton, ESet, Malwarebytes, and McAfee. We have not seen problems with Windows Defender, called Security Essentials in Windows 7. If you are running an AV program other than Microsoft's then you need to tell it to allow calibre to send and receive information over the network. Exactly how you do that depends on the program.
It is usually possible to verify that the problem is the AV software by starting windows in "safe mode". See paragraph #7 in the above-mentioned FAQ for more details.