iPad to Win7 ad hoc does not work

After purchasing Lemur I tried to connect to Win7 and had no success. Knowing that i had an old out of date network card in my desktop, i replaced it and was successful! All seemed good until the computer was rebooted the next day. Then the same issue returned. "Can not connect to network blablabla."

No mater if I turn the wep on or off it does not matter.

After much searching of the net and this forum, I am completely frustrated. I have now discovered that iOs has a known issue with ad hoc connections. REALLY!?! Doesn't that completely defeat the usefulness of Lemur? Did I just spend $50 on a useless software package?

I have an iPad 3 I'm trying to connect to Windows 7 home addition. I have several computers in the house all running Win 7 and iOS refuses to connect to ad hoc connections on all of them. I have tried turning all firewalls off. I have tried rebooting all devises. I have made sure the network adapters are working correctly.

I read that some folks have had success with creating a static IP address connection via ad hoc but is is not an option in the Win7 networking options.

Is there anyone out there that can help me out? Thanks in advance.

Hello! Keep calm and dont get upset! Im currently using Lemur with TWO Windows machines, one Win 7 32bit and one Win 7 64bit - both succesfully.

First, you need to set up static IPs and contrary to what you believe, it is posible....

To find the settings (on Windows side) you have to find the "adapter settings" (network and sharing -> change adapter settings -> choose your network -> right click -> properties -> select "Internet Protocol version 4 (TCP/IP v4) -> click on "properties" button

Now there, be cautious not to change the default settings as this will cause your computer to stop connecting to the Internet when desired. Instead use the "alternate settings" and insert the IP - subnet mask settings there.

(the names of windows and properties may appear slightly different - Im only making guesses as Im using a localized language on my Windows machines


Second AND VERY IMPORTANT, for some reason the connection with the iPad is very inconsistent if you have connected to the Internet beforehand - I believe this has something to do with the fact that we set up "secondary - alternate" settings in the steps above. So to recap, if you boot your windows machine, connect to the internet (via your router) and then you want to connect to your ad-hoc network (iPad - Lemur) its best if you restart your computer.
I know it sounds cumbersome, but frankly, with my laptop-gig machine, if Im going to perform live I dont connect to the internet beforehand - I connect to ad hoc first thing and everything works perfectly, consistently and with no problems.

Thank you so much. I'll try your suggestions ASAP and report back. I've had a few hours away from the devices in question so I'm in a much better mood now

Thanks again!

I tried you suggestion and am still having the same problem

Steps followed.

1. Set up alternate static IP of 192.168.64.1 on windows side under tcp/ip v4 with a subnet of 255.255.255.1
2. reboot computer with wireless adapter set to NOT auto-connect to the internet gateway router.
3. Build ad hoc connection as described in tutorial through the network and sharing center
4. Choose ad hoc connection on ipad after setting the IP of 192.168.64.2 with a subnet of 255.255.255.1

I did notice that the ad hoc WPA Personal security key I chose "11111111" (which I had set to be able to view the letters) was not represented properly when the final screen showed up

I saw:
"lemur network is ready to use... ect"

Wireless network name: lemur
Network security key:******

notice the 6 dots for the key where I had chosen a total of eight 1's typed 11111111

This makes me wonder if there isn't another issue at play here. I noticed the same thing on one of my laptops too. Any further ideas?

I think I have read somewhere that noone has managed to create ad hoc on Windows succesfully with WPA encryption. Try with no encryption at all first, just to be sure that you indeed can have a consistent connection - I personally use WEP not WPA!

It does not connect with out security. The iPad indicates it is connected with only an ip and subnet showing. On the computer side it shows an ip and subnet but not network connection under ipv4.

It does the exact same thing with WEP. I'm at a total loss.

Try changing the subnet mask to 255.255.0.0

And definitely no WPA2 between Win 7 and iOS(n?) - though I've confirmed that the shit sandwich that is WEP does work. Which is trivial to bypass, so it's debatable whether it provides any protection against intrusion except against the most casual would-be ingress.

On the subject of improving (security, performance / latency) matters . . . does anyone here present have any experience with rolling back iOS from 6.01 (or whatever) to iOS 5? Getting a 3**4 error (not precise, because I didn't note it down - but it's one of the errors that point to non-timely contact to Apple's auth servers).

Well, I gave up on ad hoc connections tonight. I tried everything suggested here as well as suggestions from other sources. I'm at a total loss. I should also mention that I have a background in network trouble shooting for what ever it's worth.

I finally just connected directly with through my wireless router and said the hell with it. It works great with no noticeable glitches as far as I can tell. Now maybe I can get on with building a template for my Johnson JCM 150 and my XP-80.

Thanks for all the help anyway guys. Hopefully Apple will address the issue in an upcoming iOS update.

I was having very similar issues. From my understanding it has to do with iOS devices 'needing' an internet connection to properly connect over wifi, team this with the following (taken from Windows Help and Support):

ICS (Internet Connection Sharing) and ad hoc networks: If you share your internet connection on an ad hoc network, ICS will be diabled if:
- You disconnect from the ad hoc network
- You create a new ad hoc network without disconnecting from the ad hoc network for which you enabled ICS
- You log off and then log back on (without disconnecting from the ad hoc network)

And obviously it leaves us in a situation where if we do not follow the appropriate steps (pretty much amounting to recreating a new ad hoc network) everytime our iOS device disconnects from the network (which may occur frequently for legitimate reasons) things just are not going to work....

The first time I created an ad hoc network on my Windows 7 desktop, everything worked properly, subsequently I've never been able to reproduce these results...

My current solution is to use Connectify Hotspot (or similar) to make a wifi network on my Windows 7 desktop. With that I've been successful at connecting both my iPad2 and MBP to said network and was able to get a proper connection with the Lemur Daemon on both computers. With that said, I haven't gotten the appropriate responsiveness from said connections that I would desire, but that was using TouchOSC to control TotalMix FX on my Win7 PC (it would just sometimes take a while to respond, as if there was a network bottle neck) and I still have to delve deeper into using Lemur on said network.

WiFi does not need internet connection. That is a wrong assumption based on some problems after the introduction of iOS 6, and it was quite popular.

If you have connection problems make sure to not to read stuff from September 2012. Many things written at that time where everybody was confused are simply wrong assumptions. Sometimes you just had to reboot the computer and everything was working normally.

I was also writing wrong things at that time, saying that ad-hoc is no more possible after iOS 6, but of course it always was. You just can't use a different subnet in the IP addresses anymore, that's all.

Remember to have your network card updated to the latest firmware. I even heard of one case from a network specialist where he had to downgrade (a router in this case).

73rd wrote:I was having very similar issues. From my understanding it has to do with iOS devices 'needing' an internet connection to properly connect over wifi, team this with the following (taken from Windows Help and Support):

ICS (Internet Connection Sharing) and ad hoc networks: If you share your internet connection on an ad hoc network, ICS will be diabled if:
- You disconnect from the ad hoc network
- You create a new ad hoc network without disconnecting from the ad hoc network for which you enabled ICS
- You log off and then log back on (without disconnecting from the ad hoc network)

And obviously it leaves us in a situation where if we do not follow the appropriate steps (pretty much amounting to recreating a new ad hoc network) everytime our iOS device disconnects from the network (which may occur frequently for legitimate reasons) things just are not going to work....

The first time I created an ad hoc network on my Windows 7 desktop, everything worked properly, subsequently I've never been able to reproduce these results...

My current solution is to use Connectify Hotspot (or similar) to make a wifi network on my Windows 7 desktop. With that I've been successful at connecting both my iPad2 and MBP to said network and was able to get a proper connection with the Lemur Daemon on both computers. With that said, I haven't gotten the appropriate responsiveness from said connections that I would desire, but that was using TouchOSC to control TotalMix FX on my Win7 PC (it would just sometimes take a while to respond, as if there was a network bottle neck) and I still have to delve deeper into using Lemur on said network.

Just to reinforce what Phil said here - the above post is full of misinformation (to put it politely).

One thing though Phil - it was ALWAYS correct practice to have your ad hoc network within the same subnet. Frankly I'm surprised anyone ever got it to work otherwise?

And because the page wrapped around I'll post this link again, this time with some explication.

http://www.intel.com/content/www/us/en/wireless-products/my-wifi-technology.html

That's free, and allows one to connect both an ad hoc network AND a WLAN (internet) connection simultaneously. NB: This is exactly the technology that Connectify and other apps leverage to acheive this trick and it's heavily dependent on your WiFi chipset. There's a list of supported hardware on the Intel site linked from that page.

As covered previously in other related posts on these connection issues, this ability can be set from the cmdline (netsh) too . . . it's basically enabling virtualisation of the network hardware. Yay! \o/ Moar vT-D pls!

Another fairly important one is to disable Bluetooth on your iDevice and computer as it's known to cause problems for WiFi.

Joe Soap wrote:One thing though Phil - it was ALWAYS correct practice to have your ad hoc network within the same subnet. Frankly I'm surprised anyone ever got it to work otherwise

yes. It was a bit complicated. First I had everything on the same subnet, but couldn't connect for some reason. That was in the beginning where I had zero experience, January 2012. Then I tried Connectify and had my first success. Later I used the subnet that was automatically applied in dynamic IP mode, put that as static address, and it worked (maybe I updated the firmware in the mean time, I don't remember exactly). Leading me to the wrong assumption it had to be like this, a certain subnet for the LAN, and a different one for WiFi. Unfortunately nobody corrected this despite me posting all details in various forums (including this one), so I kept this error for months.

Phil999 wrote:

Joe Soap wrote:One thing though Phil - it was ALWAYS correct practice to have your ad hoc network within the same subnet. Frankly I'm surprised anyone ever got it to work otherwise

yes. It was a bit complicated. First I had everything on the same subnet, but couldn't connect for some reason. That was in the beginning where I had zero experience, January 2012. Then I tried Connectify and had my first success. Later I used the subnet that was automatically applied in dynamic IP mode, put that as static address, and it worked (maybe I updated the firmware in the mean time, I don't remember exactly). Leading me to the wrong assumption it had to be like this, a certain subnet for the LAN, and a different one for WiFi. Unfortunately nobody corrected this despite me posting all details in various forums (including this one), so I kept this error for months.

The whole thing's a drag.

Just to clarify things for anyone reading though - you can have a different subnet for your ad hoc network and your WLAN (internet) - the important thing to note is that for connecting the iDevice to the computer in ad hoc that they both be on the same subnet.

Hi All
Firstly I am not a network guru but . . .
Remember that your address is really two parts - IP address and subnet mask - they go together . .
Subnet masks define your sub networks network and host options and affect connectivity . ..
The 255s define what is the network part, and the 0's (or other numbers) define the host range

Just because two address are different in the 2nd or 3rd octets does not mean they are separate networks
So two addresses 169.254.9.252 and 192.254.193.18 may appear as separate subnets depending on subnet mask.
Using 255.255.0.0 will be fine as hosts in the 3rd and 4th octet are part of the same subnet
Using 255.255.255.0 will not be though because the network part is different
These numbers - the 255's define the network part and the others the hosts part
255.255.0.0 has over 65000 possible hosts - 255.255.255.0 only 254 . . .
It is even possible to split this even further via masking within the host octets
This can allow you to limit the number of possible hosts within a subnet

Of course DHCP makes it all far simpler by simply assigning addresses within appropriate ranges.

Also it is best to not worry about WLAN/internet connection when doing adhoc connection . . .
In fact it is best to be doing very little real network stuff whilst doing music stuff imho

hth
MM

PS Of course if you are writing a long forum reply and swapping network connections etc remember to switch back to your net network before trying to send your message . . .

Macciza, are you trying to confuse us or help us?

Just joking, it is of course helpful, but one has to decipher a bit the information. And if we need more info, there's always wikipedia and other sources.

Macciza wrote:Hi All
Firstly I am not a network guru but . . .
Remember that your address is really two parts - IP address and subnet mask - they go together . .
Subnet masks define your sub networks network and host options and affect connectivity . ..
The 255s define what is the network part, and the 0's (or other numbers) define the host range

Just because two address are different in the 2nd or 3rd octets does not mean they are separate networks
So two addresses 169.254.9.252 and 192.254.193.18 may appear as separate subnets depending on subnet mask.
Using 255.255.0.0 will be fine as hosts in the 3rd and 4th octet are part of the same subnet
Using 255.255.255.0 will not be though because the network part is different
These numbers - the 255's define the network part and the others the hosts part
255.255.0.0 has over 65000 possible hosts - 255.255.255.0 only 254 . . .
It is even possible to split this even further via masking within the host octets
This can allow you to limit the number of possible hosts within a subnet

Of course DHCP makes it all far simpler by simply assigning addresses within appropriate ranges.

Also it is best to not worry about WLAN/internet connection when doing adhoc connection . . .
In fact it is best to be doing very little real network stuff whilst doing music stuff imho

hth
MM

Nope, that won't confuse n00bs at all - not one bit.

Macciza wrote: PS Of course if you are writing a long forum reply and swapping network connections etc remember to switch back to your net network before trying to send your message . . .

Or trying to develop a Lemur template and access help / resources on the Web.