Windows 10: BSOD when using ad-hoc

Discus and support BSOD when using ad-hoc in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello all, I originally ran into a bsod that pointed to a video driver. Jumped on NVidia site got the driver. That worked well until recently. Haven't... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by yodasdaddy13, Feb 20, 2018.

  1. BSOD when using ad-hoc


    Hello all, I originally ran into a bsod that pointed to a video driver. Jumped on NVidia site got the driver. That worked well until recently. Haven't changed any settings since but now i'm getting one related to Memory failure. I've ran memtest several times, no faults found on any of them. Chased a few more threads, nothing really helped...so, here I am.
    I used bluescreenview to capture the offending driver and it comes up with "ntoskml.exe" and "ndis.sys" as the culprits. Now I've uninstalled and reinstalled most of my drivers trying to chase down the last bsod epidemic I encountered. I'm hoping everything was properly reinstalled and I don't look foolish. I can't seem to locate the problem though. The only correlation I've found that causes it is while ad-hoc'ing my phone to watch youtube using landline internet instead of my data(wifi is disabled for phones, so that's my workaround). Anyway, I've attached the zip file y'all requested below though. Any help would be much appreciated. Thanks in advance

    :)
     
    yodasdaddy13, Feb 20, 2018
    #1
  2. korhore Win User

    Start an ad-hoc WLAN, Nokia 5630

    I have same problem with E7. It connects fine to some other device in ad-hoc mode, I even can create new ad-hoc setting, but I can't find a way to set it into ad-hoc mode as first device in ad hoc network. I always wants to scan network and wants to join
    into existing ad-hoc network. So there is no way to set up ad-hoc network where is only E7 phones. You can't set up first device into ad-hoc mode, others could join if there is one already in ad-hoc mode, but you can't set first one into ad-hoc mode :smileymad:
     
    korhore, Feb 20, 2018
    #2
  3. CJLim Win User
    wifi connection

    I presume you are using Joikuspot. Joikuspot requires Ad-hoc mode to enable connection. Your tab will only work if it supports ad-hoc mode. Otherwise, it will not connect. Please check to see if your tab support ad-hoc.
     
    CJLim, Feb 20, 2018
    #3
  4. BSOD when using ad-hoc

    Hi there,

    My bluescreen analysis is showing an probem with the Intel Wifi driver. I think it has something to do with the adhoc connection:

    Code: 0x0000001A: MEMORY_MANAGEMENT (2018-02-21 19:59:53) [Windows 10] CAUSED BY: Netwbw02.sys [2016-10-09] * Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter * => Drivers & Software nvlddmkm.sys [2018-01-23] * nVidia Video drivers * => Download Drivers | NVIDIA PROCESS: System Usual causes: Device driver, memory, kernel[/quote] Code: Name [00000004] Intel(R) Dual Band Wireless-AC 7260 Adapter Type Ethernet 802.3 Product Type Intel(R) Dual Band Wireless-AC 7260 Installed Yes PNP Device ID PCI\VEN_8086&DEV_08B1&SUBSYS_C0708086&REV_BB\4&33C74B69&0&00E2 Last Reset 2/21/2018 2:44 PM Index 4 Service Name NETwNb64 IP Address 192.168.10.52 IP Subnet 255.255.254.0 Default IP Gateway 192.168.10.1 DHCP Enabled Yes DHCP Server 192.168.254.200 DHCP Lease Expires 12/31/1969 11:02 PM DHCP Lease Obtained 12/31/1969 7:02 PM MAC Address ‪A4:C4:94BSOD when using ad-hoc :DB:33:FF‬ Memory Address 0xED200000-0xED2FFFFF IRQ Channel IRQ 4294967292 Driver c:\windows\system32\drivers\netwbw02.sys (18.33.5.1, 3.36 MB (3,525,896 bytes), 11/9/2016 10:15 PM)[/quote]
    Please run those two setups to update you Intel drivers:

    https://downloadmirror.intel.com/274...et64_Win10.exe

    https://downloadmirror.intel.com/274...0_64_Win10.exe
     
    BSODHunter, Feb 21, 2018
    #4
  5. Upgraded both drivers but am now getting a crash with no bluescreen. This is the same chasing I did earlier with the video card. Do have the new dump file below. Thank you for your previous help.
     
    yodasdaddy13, Feb 21, 2018
    #5
  6. Will check tommorow morning
     
    BSODHunter, Feb 21, 2018
    #6
  7. Did u run memtest in the correct version for minimum 8 passes?

    But its surely something with the adhoc connection:

    Code: 0x00000133: [SPECIAL] DPC_WATCHDOG_VIOLATION (2018-02-22 18:37:37) [Windows 10] CAUSED BY: Netwbw02.sys [2017-10-31] * Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter * => Drivers & Software nvlddmkm.sys [2018-01-23] * nVidia Video drivers * => Download Drivers | NVIDIA PROCESS: System[/quote]
    In eventlog u can see following:

    At 11:35:37 theres an warning the network driver is beginning to reset

    Code: Event[11130]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2018-02-22T11:35:37.638 Event ID: 10400 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: Yodasdaddy13 Description: The network interface "Intel(R) Dual Band Wireless-AC 7260" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver requested that it be reset. This network interface has reset 3 time(s) since it was last initialized.[/quote]
    After this theres is an message which is shown up 50 times in a row something with the network adapter/driver:

    Code: Event[11131]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.638 Event ID: 5010 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11132]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.638 Event ID: 5010 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11133]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.638 Event ID: 5010 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11134]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5000 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11135]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11136]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11137]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11138]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11139]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11140]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11141]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11142]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11143]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11144]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11145]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11146]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11147]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11148]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11149]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11150]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11151]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11152]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11153]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11154]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11155]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11156]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11157]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11158]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11159]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11160]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11161]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11162]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11163]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11164]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11165]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11166]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11167]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11168]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11169]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11170]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11171]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11172]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11173]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11174]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11175]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11176]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A Event[11177]: Log Name: System Source: NETwNb64 Date: 2018-02-22T11:35:37.972 Event ID: 5002 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: N/A[/quote]
     
    BSODHunter, Feb 22, 2018
    #7
  8. BSOD when using ad-hoc

    But as u can see theres also the nvidia driver shown up. U should reinstall it using DDU:


    BSOD when using ad-hoc [​IMG]
    Display Driver Uninstaller: How to use
    Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.


    Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
    You can upload it to an cloud service like dropbox or onedrive.
     
    BSODHunter, Feb 22, 2018
    #8
  9. zbook New Member
    1) Please increase the free space in drive C: so that there is 30 GB or more free space.

    Drive: C:
    Free Space: 16.5 GB
    Total Space: 121.3 GB
    File System: NTFS
    Model: SanDisk SD7SB3Q128G1002

    Code: Event[11244]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-02-22T11:41:02.463 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Yodasdaddy13 Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote]
     
    zbook, Feb 22, 2018
    #9
  10. Well, i cleared out enough space to capture a dump file but haven't crashed since doing so. Will continue to observe and report findings tomorrow if unchanged.
     
    yodasdaddy13, Feb 22, 2018
    #10
  11. Well, since the storage has been freed up i've had two system hang-ups. Neither have created a bluescreen and neither have created a minidump. I have searched the event viewer but don't see anything that is presenting a stop error except where i have to power cycle the machine. Any ideas where to look?
     
    yodasdaddy13, Feb 25, 2018
    #11
  12. Please upload a new log collector log
     
    BSODHunter, Feb 26, 2018
    #12
  13. BSOD when using ad-hoc

    Where do i find the log collector? Also I have a new/old bluescreen error. Back to watchdog violation which points towards graphics driver. I did get on Asus website and they have a driver for mine dated back to 2015. Anyone think that driver would help or is it too outdated to even bother with? Also, i have a full windows dump file. I just dropped it in the folder so it may take a while to sync. 870,613kb is the size i have listed for it.
    Dropbox - MEMORY.DMP Latest minidump attached.
     
    yodasdaddy13, Feb 26, 2018
    #13
  14. Wifi driver again:

    Code: 0x00000133: [SPECIAL] DPC_WATCHDOG_VIOLATION (2018-02-26 21:16:41) [Windows 10] CAUSED BY: Netwbw02.sys [2017-10-31] * Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter * => Drivers & Software PROCESS: System[/quote]
    Stack is also showing those NAT messages which refer to the adhoc connection:

    Code: ffff8504`0245f858 fffff801`e5c8955a ipnat!NatLookupRedirect+0x76 ffff8504`0245f8a8 fffff801`e5c8a935 ipnat!NatpRedirectQueryHandler+0x5f5 ffff8504`0245f8b8 fffff801`e5c9f130 ipnat!WPP_GLOBAL_Control ffff8504`0245f918 fffff801`e5c71983 ipnat!NatLookupAndReferenceDirector+0x23f ffff8504`0245f950 fffff801`e5c93306 ipnat!NatReverseTcpStateCheck+0x15a ffff8504`0245f968 fffff801`e5c8fd9a ipnat!NatpDirectPacket+0x18a ffff8504`0245fa38 fffff801`e5c92c0a ipnat!NatpSendPacket+0x2de ffff8504`0245fb08 fffff801`e5c933f0 ipnat!NatTranslatePacket ffff8504`0245fb28 fffff801`e5c9401d ipnat!NatTranslatePacket+0xc2d ffff8504`0245fb88 fffff801`e5c987ee ipnat!NatShimFreeBuffer+0x7e ffff8504`0245fbd8 fffff801`e5c98b13 ipnat!NatShimTranslatePacket+0x113 ffff8504`0245fbf8 fffff801`e5c933f0 ipnat!NatTranslatePacket ffff8504`0245fc30 fffff801`e5c9d948 ipnat!WPP_d020a5fa1f1a317ec270dc4d44811cd5_Traceguids ffff8504`0245fc38 fffff801`e5c9f130 ipnat!WPP_GLOBAL_Control[/quote]
    Did the adhoc connection ever worked without problems?
     
    BSODHunter, Feb 26, 2018
    #14
  15. Honestly I havn't used Ad-hoc in years. This was just one of those, "I'll try it and see scenarios". And it does work great for about an 30mins to an hour at a time.
     
    yodasdaddy13, Apr 5, 2018
    #15
Thema:

BSOD when using ad-hoc

Loading...
  1. BSOD when using ad-hoc - Similar Threads - BSOD using hoc

  2. Windows10 - Can't connect to ad-hoc network

    in Windows 10 Network and Sharing
    Windows10 - Can't connect to ad-hoc network: Hi, I created a network using an ad-hoc communication on a computer with Windows 7 in order to do some wireless printing (the buildings networks firewall would not allow the normal wifi connection to work). The printer can log into that network and the computer from which...
  3. How to set up an ad-hoc wireless network in Windows 10?

    in Windows 10 Customization
    How to set up an ad-hoc wireless network in Windows 10?: I want to set up an ad-hoc wireless network because I have computers with different OS (Linux, Windows 10) and think that mesh-network is the best way for communication in this case. I suppose I should start with Windows 10. Your tip? Thanks...
  4. Ad-Hoc Wireless Network

    in Windows 10 Network and Sharing
    Ad-Hoc Wireless Network: Aye! I have several computers with different systems, Windows 10, Linux, Android,... some have internet-access and may act as a gateway, some might act as an access point, some dont even have a keyboard/mouse - but all have a wireless network-interface-card. I dont use...
  5. creating an ad hoc Network?

    in Windows 10 Network and Sharing
    creating an ad hoc Network?: In Windows 10; how do i set up an ad hoc Network on my PC? https://answers.microsoft.com/en-us/windows/forum/all/creating-an-ad-hoc-network/9a3c93a5-dc3b-4881-b99a-d112bb92d9d7
  6. how to set up a ad-hoc network

    in Windows 10 Network and Sharing
    how to set up a ad-hoc network: since there is no more homegroups how to set up a ad-hoc network https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/how-to-set-up-a-ad-hoc-network/b759cfd1-5e6d-4426-997f-3978239590a2
  7. No Choice for Ad Hoc Network

    in Windows 10 Network and Sharing
    No Choice for Ad Hoc Network: As part of a practice I'm doing, I was going to set up an Ad Hoc wireless network on my Windows 10 Enterprise computer. But under Network and Sharing, like this: [img] why no ad hoc choice? 113515
  8. Ad hoc network..."Private" network doesn't stick

    in Windows 10 Network and Sharing
    Ad hoc network..."Private" network doesn't stick: I have a unique situation and I haven't been able to find the answer. I have set up an ad hoc network on the "host" computer (i.e. the netsh "hostednetwork" computer) so that I can remote into the host computer using another computer ("client" PC). What this does is...
  9. Connecting to ad-hoc issue

    in Windows 10 Network and Sharing
    Connecting to ad-hoc issue: Hello! Few days ago i runned ad-hoc acces point in my linux device. When i trying connect to it, gives me an error. Everything is fine On Windows 8. I tried many different options like connecting via cmd, turning off firewall but still nothing. Anyone knows solution...
  10. Ad Hoc (Or something similar) OFFLINE

    in Windows 10 Network and Sharing
    Ad Hoc (Or something similar) OFFLINE: Hi there folks. I'm sure you've heard the question about creating/joining ad-hoc networks before. I have. From the tutorials I've seen, it only explains how to create a network when you are already connected to a wireless network from a router. If that's the case you might as...