Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 4 subscribers
  • Views 8980 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Client Firewall on Windows 10 causing "missing network protocols" error

LloydMatthews

Hi.

I'm using the home-use version of Sophos Endpoint and Control. I installed it along with the Client Firewall on an Intel PC which had a clean install of Windows 10 Home 64-bit. After the Sophos install I could not connect to the Internet, and Network Troubleshooting said "one or more network protocols are missing". After I uninstalled Client Firewall (but left Sophos AV and Auto-Update), I had normal network connectivity again. I have no problems with Client Firewall on another (AMD) Windows 10 Home 64-bit PC that I had upgraded from Windows 7.

The Windows 10 missing protocols issue seems to be fairly common, but I could not find anyone who fixed it the same way I did. Does anyone have any ideas about what might be causing the problem?

 -Thanks! LloydM



This thread was automatically locked due to age.
Parents
  • 0

    The Network protocols error is popping up quite a bit, however 90%+ of the users experiencing this error don't actually have the problem the error is referring to.  The normal reason for the error is twofold, either the TCP/IP network stack options have been corrupted in the registry and/or a specific group policy has been configured. 

    • It seems the network protocols error on Windows 10 is most likely related to some code within Windows that believes a specific group policy has been set, even though that specific policy is set to it's default, non-configured state.  There seems to be a correlation between third party programs that affect networking, such as VPN software and stateful firewalls, on Windows 10 and this specific error.

    There are a minute amount of users who are actually receiving this error on Windows 10 because the TCP/IP network stack in the registry has become corrupted.  Specific users with this actual issue have found exporting the TCP/IP registry keys from Windows 7, then importing into Windows 10 solved their issue... however, unless one is 100% sure they're one of the minute percentage of users with actual corruption within their TCP/IP stack, performing this step is overkill.

    First, verify your DNS and DHCP settings are correct for the interface connected.  Try releasing leases and flushing the dns cache via:

    1. ipconfig /release
    2. ipconfig /flushdns
    3. ipconfig /renew
    4. ipconfig /registerdns

    Most likely, users experiencing the network protocols error aren't actually having an issue with network protocols, but with network settings for their interface(s) (for some reason, and only within specific environments, Windows 10 is changing interface options during third party network software installations).

    SilverStone DS380 | AsRock C2750D4I | Alienware 18 | In Win Chopin | SuperMicro A1SRi-2758F
    2.4gHz 8C C2750 ; 32GB ECC | 2.5gHz 4C i7 4710MQ ; 32GB | 2.4gHz 8C C2758 ; 32GB ECC
    Vantec 4C USB3 PCIe UGT-PCE430-4C | 8GB AMD SLI R9 M290x |
    SSD  | 850 EVO: 120GB | 1TB ; mSATA: 1TB (2) | 850 Pro: 128GB ; 850 EVO: 1TB
    HDD | Seagate: { ST4000VN000 (8) } Z2 ; { HGST HTS721010A (3) } Z2 |
    FreeNAS 11.2 | { PNY Turbo USB3 32GB (2) } Mirror | Win 10 Pro | ESXi 6.7: Sophos UTM 9.6

    Various Wikis, Scripts, & Configs | Prebuilt OpenSSL Config

Reply
  • 0

    The Network protocols error is popping up quite a bit, however 90%+ of the users experiencing this error don't actually have the problem the error is referring to.  The normal reason for the error is twofold, either the TCP/IP network stack options have been corrupted in the registry and/or a specific group policy has been configured. 

    • It seems the network protocols error on Windows 10 is most likely related to some code within Windows that believes a specific group policy has been set, even though that specific policy is set to it's default, non-configured state.  There seems to be a correlation between third party programs that affect networking, such as VPN software and stateful firewalls, on Windows 10 and this specific error.

    There are a minute amount of users who are actually receiving this error on Windows 10 because the TCP/IP network stack in the registry has become corrupted.  Specific users with this actual issue have found exporting the TCP/IP registry keys from Windows 7, then importing into Windows 10 solved their issue... however, unless one is 100% sure they're one of the minute percentage of users with actual corruption within their TCP/IP stack, performing this step is overkill.

    First, verify your DNS and DHCP settings are correct for the interface connected.  Try releasing leases and flushing the dns cache via:

    1. ipconfig /release
    2. ipconfig /flushdns
    3. ipconfig /renew
    4. ipconfig /registerdns

    Most likely, users experiencing the network protocols error aren't actually having an issue with network protocols, but with network settings for their interface(s) (for some reason, and only within specific environments, Windows 10 is changing interface options during third party network software installations).

    SilverStone DS380 | AsRock C2750D4I | Alienware 18 | In Win Chopin | SuperMicro A1SRi-2758F
    2.4gHz 8C C2750 ; 32GB ECC | 2.5gHz 4C i7 4710MQ ; 32GB | 2.4gHz 8C C2758 ; 32GB ECC
    Vantec 4C USB3 PCIe UGT-PCE430-4C | 8GB AMD SLI R9 M290x |
    SSD  | 850 EVO: 120GB | 1TB ; mSATA: 1TB (2) | 850 Pro: 128GB ; 850 EVO: 1TB
    HDD | Seagate: { ST4000VN000 (8) } Z2 ; { HGST HTS721010A (3) } Z2 |
    FreeNAS 11.2 | { PNY Turbo USB3 32GB (2) } Mirror | Win 10 Pro | ESXi 6.7: Sophos UTM 9.6

    Various Wikis, Scripts, & Configs | Prebuilt OpenSSL Config

Children
No Data
Unfiltered HTML