tonygamble wrote:I'm bumping this old thread as it refers to DHCP errors when I tried to register the newly created network on the card... I am sure a lot of the problems that people are having with getting their new cards to recognise an ad-hoc or Connectify access point are due to their ignorance that these options are there.
To be fair, I would expect any DHCP issues encountered during adding the profile to persist when connecting to an ad hoc network for transferring the media, too, so while selecting "Other network..." and setting the checkbox to indicate that the network is "out of range" will avoid DHCP (or link-level IP address assignment) problems when setting up the profile, I'm not sure if it would be a real solution.
When adding a true ad hoc network, the Eye-Fi Card has the smarts to not do the final step of end to end network connectivity verification ("Contacting the Eye-Fi server..."), but it does expect to at least succeed in getting an address via DHCP or discovering its peer with link-level IP address assignment.
If, however, a "software AP" solution is used to create an infrastructure network for "peer to peer" use and there is no broadband connectivity offered by the computer, then I can see how choosing "out of range" would help to avoid doing the end-to-end connectivity verification, but those would be cases where the IP address negotiation via DHCP is working and it is only the last step of the network profile addition process that's failing ("Contacting the Eye-Fi server...").
Given that Connectify, to the best of my understanding, uses Windows 7's software AP features (and therefore deploys an infrastructure network), I would expect any issues related to it to fall into the latter category, but I wanted to clarify that it should not be DHCP issues that are addressed by this approach and, that the issues are somewhat different between the ad hoc and Connectify cases.
Thank you for taking the time for your helpful post,