[chaley]

Intermittent connections are the hardest to debug. Thanks for being willing to take some more time to help work out what is going on.

Starting at the beginning with things that we know can cause problems:

1. IP addresses in the 10 range are a bit rare. Are you on a home network? What else is on the network?
2. What brand is your network router (the one that separates the internal network from the internet)?
3. Does your windows machine have a fixed IP address? In other words, is it always 10.1.1.3?
4. Is there more than one network router/switch between your nexus and your windows machine? If you are on a work network then this is very possible.
5. Have you verified that calibre is allowed through the firewall on your windows machine (see the faq for instructions)?
6. Are you running any "network security suite" on your windows machine, such as McAfee or Norton?
7. Is the windows machine managed by an IT group (a work machine)?
8. Are you running anything like a "virtual machine" such as Windows XP mode or virtualbox?
9. Do you have a VPN installed? These are usually installed to connect securely to work networks.
10. Does your windows machine have any other network interfaces? To check this, open a command box (Start, type cmd into the "Run" box, press return. When the command box opens, type "ipconfig /all". You will see something similar to what is under the spoiler. Look to see if more than one adapter has an IP address.
    
    Spoiler:

    C:\>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : wallaby
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Mixed
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    
    Ethernet adapter Local Area Connection 3:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : TAP-Win32 Adapter V9
       Physical Address. . . . . . . . . : 00-FF-06-42-41-63
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
       Physical Address. . . . . . . . . : 6C-F0-49-71-15-B3
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::1c6a:f6f5:6049:83f6%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.220.38(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 14 November 2012 16:35:01
       Lease Expires . . . . . . . . . . : 20 November 2012 20:44:54
       Default Gateway . . . . . . . . . : 192.168.220.1
       DHCP Server . . . . . . . . . . . : 192.168.220.1
       DHCPv6 IAID . . . . . . . . . . . : 242020425
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-27-DF-A2-6C-F0-49-71-15-B3
       DNS Servers . . . . . . . . . . . : 192.168.220.1
                                           8.8.8.8
                                           8.8.4.4
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.{9DF7F34A-A87B-4471-B7AE-B7BB272554EF}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Local Area Connection* 11:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:8fc:389e:b13f:4590(Preferred)
       Link-local IPv6 Address . . . . . : fe80::8fc:389e:b13f:4590%12(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled
    
    Tunnel adapter isatap.{06424163-4DB3-4ED8-BE4D-5D3292E52462}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

11. Are you running a firewall on your nexus such as droidwall?
12. Do you have any other devices plugged into the windows machine, perhaps only for charging?

It would be very useful to get some debug information from calibre. To do this, please:

1. Start calibre in debug mode. Do this by starting calibre, then clicking on the down-arrow next to preferences and selecting Restart in debug mode.
2. Wait a few seconds. Don't do anything with calibre.
3. Attempt to make a "wireless device" connection from your nexus. I assume this will fail. If it does not, then don't bother with the rest. Instead, disconnect and try again.
4. Quit calibre. A window will open containing the debug text.
5. Post the debug test here.
6. Start calibre (again).
7. Go to Preferences -> Miscellaneous and press Debug device connection. Post the results here.

As a further test, please check content server connectivity.

• On your windows machine running calibre, using a browser (internet explorer, firefox, etc) connect to 10.1.1.3:8080 assuming that your CS port is still 8080. You should see calibre's content server home page.
• If you have another computer such as a laptop, try the same thing from that machine. It would be best if this machine is connected wirelessly.
• Using chrome on your Nexus, attempt to connect to 10.1.1.3:8080. If it works, refresh the page a few times to be sure that it wasn't the "one off" success.
• If the above works, then using chrome on your nexus attempt to connect to 10.1.1.3:9090. It it works then it will sit and spin for around a minute and finally show some text containing things like "pubdateFormat", "timestampFormat", and a lot of other stuff.

If the first doesn't work, then there is something on your windows machine blocking internal network connections. CC will never work reliably in this case.

If the second doesn't work reliably then there is a problem at the edge of your windows machine preventing incoming network connections. This will almost certainly be a firewall, anti-virus, or over-aggressive network security program on your PC.

If the second works reliably but the third doesn't, then the problem is somewhere on your network between your nexus and your PC. What that might be depends on the topology of the network.

If the third works but the fourth doesn't then the problem is probably on your windows machine, probably (again) a firewall, anti-virus, or over-aggressive network security program. In this case we will need to try a few more experiments.

If the last two above work reliably but CC does not, then we have a problem with CC. What that might be is a mystery, but we will cross that bridge when we come to it.