Can anyone check if Windows 8.1 RTM can see Ad-Hoc wireless networks?

Discussion in 'Windows 8' started by sciencefair, Sep 10, 2013.

  1. sciencefair

    sciencefair MDL Novice

    Sep 10, 2013
    1
    0
    0
    Hello,
    In Windows 7 and Windows 8, I was able to tether a Nokia phone to my Thinkpad X220 through the creation of an ad-hoc wireless network on the phone. The phone cannot create an infrastucture wireless network like iPhones and androids do so this is my only way to tether.

    It seems that in the Windows 8.1 Preview upgraded from the windows store, I can no longer see ad-hoc networks in the list of wireless networks to connect to. Can anyone tell me if the RTM of 8.1 restored this feature? If not, is it possible to restore the feature somehow?
     
  2. bootstap

    bootstap MDL Member

    Mar 25, 2012
    122
    40
    10
    hi,
    i'm using ad-hoc to connect 2 laptops (win7 and win8.1).
    unfortunately win8.1 preview and rtm are no more showing ad-hoc networks, so i use shortcuts in order to connect/disconnect.
    some choose third party solution.

    good luck.
     
  3. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    #3 david_xross_2, Sep 14, 2013
    Last edited: Sep 14, 2013
    Can you explain how do you use shortcuts in order to connect/disconnect?..I too am using adhoc networks with some devices and find it ludicrous that windows 8.1 can't even "see" these adhoc networks

    Regards :D
     
  4. bootstap

    bootstap MDL Member

    Mar 25, 2012
    122
    40
    10
    #4 bootstap, Sep 15, 2013
    Last edited by a moderator: Apr 20, 2017
    hi,
    with pleasure.
    let's assume that you have already manually created (on both computers separately) an ad-hoc network named XXXXX and stored its password.
    in case you need to know how to do that, let me know.

    1. shortcut to connect:

    Target:

    Code:
    C:\Windows\System32\netsh.exe wlan connect name=XXXXX interface="WiFi"
    where XXXXX is your ad-hoc network name.

    2. shortcut to disconnect:

    Target:

    Code:
    C:\Windows\System32\netsh.exe wlan disconnect interface="WiFi"
    Note: this shortcut disconnects all connected wifi networks.

    3. Bonus: auto connect ad-hoc at startup:

    as you know Windows does not support automatic connection to ad-hoc networks.
    but one can use a 'trick' to do that.
    a- open regedit,
    b- navigate to HKLU/Software/Microsoft/Windows/CurrentVersion/Run,
    c- add this string value (name it whatever you want, e.g. ad-hoc):
    netsh wlan connect name=XXXXX interface="WiFi"

    Note: to set autoconnect for all users just replace HKLU with HKLM.

    good luck.
     
  5. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    #5 david_xross_2, Sep 15, 2013
    Last edited by a moderator: Apr 20, 2017

    Hi,
    Thanks very much for your response :biggrin:

    How can we manually create (on both computers separately) any ad-hoc network named XXXXX and store its password..As the GUI for Manage Networks has been removed from Networking and Sharing Center in Windows 8.1..

    Regards :)
     
  6. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,644
    15,564
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
  8. bootstap

    bootstap MDL Member

    Mar 25, 2012
    122
    40
    10
    #9 bootstap, Sep 15, 2013
    Last edited by a moderator: Apr 20, 2017
    hi david,

    you understood that i didn't meant the conventional method mentioned by tito (many thanks to him), because as you know it suppose that the adapter supports hosted network. (not my case)
    now let's suppose we have two computers Comp1 & Comp2 (not supporting hosted networks) to connect via ad-hoc, named for example DAVADHOC.

    here are the steps to do:

    Code:
    
    
    Phase 1: setting Comp1
    
    Step0: switch on Comp1 wifi and switch off Comp2 wifi.
    
    Step1: cleaning
    
    1-on comp1 open elevated cmd,
    2- type:
    netsh wlan delete profile DAVADHOC
    
    Step2: creating wireless profile (DAVADHOC)
    
    1- open network and sharing center,
    2- setup new connection or network,
    3- manually connect to a wireless network,
    4- enter network name (DAVADHOC), security type, encryption type and the password, (better to use WPA2 - personal)
    5- uncheck both checkboxes : 
        -Start this connection automatically
        -Connect even if the network is not broadcasting
    Note: this is very very important.
    6- next & close.
    
    Step3: Creating Ad-hoc network:
    
    1- open elevated cmd,
    2- type:
    netsh wlan set profileparameter name=DAVADHOC connectiontype=IBSS
    
    at this step you successfully created (on Comp1) an ad-hoc network and stored its password.
    
    Phase2: setting Comp2
    
    Step0: switch off Comp1 wifi and switch on Comp2 wifi.
    
    redo Step1 to Step3 on Comp2. (ad-doc specs must be same as those entered in Comp1)
    
    Step4: switch on comp1 wifi
    
    ./.
    
    now you are ready to connect computers 1&2 via DAVADHOC.

    Notes:

    * i'm using ad-hoc network to share Internet connection over it.
    *on win8.1 you may use shortcuts to connect/disconnect, as i described it above.
    *you can autoconnect to DAVEADHOC (see my last message)
    *on win7 and win8 just use GUI to connect/disconnect.
    *through Ad-hoc you may:
    -share internet connection,
    -share files;
    - etc.
    * by default windows sets ad-hoc network to public type. on win8 and win8.1 you have to change it manually (regedit).
    * for those who share an internet connection through ad-hoc, if they are experiencing an issue browsing ftp sites, let me know, i'll tell you what to do.
    *step2 can be replaced by a cmd instruction.
    *this config does not need hosted network support.
    * this method was tested (by me) on Win7 Win8 & Win8.1 (Preview & rtm).
    * i'm not interested in Win XP SPx, because this OS supports only WEP ad-hoc, and this encryption is easily c-r-@-c-k-a-b-l-e.

    hope it's clear enough and good luck to all.
     
  9. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    #10 david_xross_2, Sep 15, 2013
    Last edited by a moderator: Apr 20, 2017

    Thank you very much bootstap.:hug2:

    This was exactly what I was looking for...:)

    Best Regards :D
     
  10. bootstap

    bootstap MDL Member

    Mar 25, 2012
    122
    40
    10
    hi david,

    you are welcome brother. glad for you.
    ---

    if administrators allow me, i would like to say this
    - there is no knowledge without sharing,
    - many many thanks to all people, who are supporting sharing, special thanks to those 'heroes' of the years: 2001-2009.
    many thanks to all.
     
  11. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    Well Said...:good3:
     
  12. Aden Tengoku

    Aden Tengoku MDL Junior Member

    Aug 28, 2013
    63
    14
    0
    :biggrin: I already found a great software to be able to see adhoc connections again
    wefi.com/download enjoy!:dance:
     
  13. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    #14 david_xross_2, Oct 14, 2013
    Last edited: Oct 14, 2013
    Can you verify if the software download is clean?..Read many reviews saying "This is malware that copies itself when you uninstall."
     
  14. Aden Tengoku

    Aden Tengoku MDL Junior Member

    Aug 28, 2013
    63
    14
    0
    malware :confused:?? its safe am already using it I have windows 8.1 RTM + zemna antiloger + bitdefender works great trust me :hug2:
     
  15. hb860

    hb860 MDL Addicted

    May 7, 2010
    996
    1,808
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. TreyG

    TreyG MDL Novice

    Oct 31, 2013
    1
    0
    0
    #17 TreyG, Oct 31, 2013
    Last edited: Oct 31, 2013
    I'd say 'No' to the original question that titles this thread.

    There is an issue if your Win8.1 box is a client and your virtual router is a WinXP box [Not capable of hosted networks]. In such a case, the adhoc wireless network beamed out from the WinXP box does not come up in the list of visible networks in the Win8.1 box.

    I cannot change the virtual router [much like the OP's Nokia phone], but only the client [Win8.1].

    Haven’t found any workaround to this problem yet; any help would be appreciated.

    The preceeding discussion has been helpful, thanks to all who have been participating. However, I feel the problem for the OP hasn't been resolved.
     
  17. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    6,680
    10,126
    210
    I made a post about setting up tethered wifi using commands:
    http://forums.mydigitallife.net/thr...stuff-for-Win8-x-(Share-your-WiFi-connection)

    Try setting your network up in that manner and see if you can see it again.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    #19 david_xross_2, Oct 31, 2013
    Last edited by a moderator: Apr 20, 2017
    Unfortunately there's no workaround to using adhoc networks through GUI..You can manually connect to them via appropriate netsh commands or create shortcuts to easily connect to them.

     
  19. david_xross_2

    david_xross_2 MDL Senior Member

    Aug 31, 2012
    272
    299
    10
    #20 david_xross_2, Nov 16, 2013
    Last edited: Nov 16, 2013
    @bootstap,

    Hi..Your method here is working really well..Thanks for that :D...Is there a way that we can save the Adhoc Network Profile?..Because, Every time I log out of the current session..I have to recreate the network profile again from the command prompt and the GUI..Have a Great Day man...Cheers :biggrin: