If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Initial invocation of MsMpEng.exe on new PC breaks PPTP
The W10's first invocation of MsMpEng.exe (Windows Defender Antivirus
Service) on a new PC uses so many resources when it initially runs that it breaks the PPTP client through starvation of resources. After approximately 30-60 minutes MsMpEng.exe drops lower on the Task List and W10's PPTP client starts to work. This anomaly was originally misdiagnosed and mistakenly attributed to KB4503327. Thank you, 73, -- Don Kuenz KB7RPU There was a young lady named Bright Whose speed was far faster than light; She set out one day In a relative way And returned on the previous night. |
Ads |
#2
|
|||
|
|||
Initial invocation of MsMpEng.exe on new PC breaks PPTP
Don Kuenz wrote:
The W10's first invocation of MsMpEng.exe (Windows Defender Antivirus Service) on a new PC uses so many resources when it initially runs that it breaks the PPTP client through starvation of resources. After approximately 30-60 minutes MsMpEng.exe drops lower on the Task List and W10's PPTP client starts to work. This anomaly was originally misdiagnosed and mistakenly attributed to KB4503327. Thank you, 73, https://en.wikipedia.org/wiki/Point-...eling_Protocol The Point-to-Point Tunneling Protocol (PPTP) is an obsolete method for implementing virtual private networks. PPTP has many well known security issues. ...tunnel to encapsulate PPP packets It's possible this is the "rasclient", which would also be tasked with making PPPOE termination work. PPPOE is used, when you connect an ADSL modem (no router) directly to a PC, so only the one PC can see the network, and there is hardly any protection from Internet-side attacks. The telephone company encapsulates in PPPOE (or PPPOA is an option), and OSes have had a terminator for this for ~19 years or so. https://blogs.technet.microsoft.com/...elated-errors/ ******* Take a look at this scheduled task design, which has a retry count, in an attempt to wait out whatever other service(s) haven't started yet. Perhaps "rasman" or equivalent. https://www.downloadsource.net/how-t...indows/n/9405/ If your PPTP isn't working, I would expect to see reports from people, that their PPPOE isn't working either. It's possible the authentication step is failing, either because something isn't ready, or there aren't enough retries set up in the thing. In the old days, PPPOE used to be able to generate a logfile, and in that you would see the negotiation steps, the selection of authentication protocol and so on, and you could get some hints from that, what is failing. But for actual services that haven't started, those are less likely to be logged properly. Sometimes a "delayed start" is called for, if it appears some structure needed by the thing you're doing, doesn't actually start properly at boot time. A "delayed start", might wait 120 seconds for the OS to settle down. It's possible the problem isn't MSMPENG entirely, and it's a "too aggressive" "starts too early" "VPN connector" that isn't patient enough and doesn't have enough retries with a sleep in between them. Summary: Jiggle the handle... Paul |
#3
|
|||
|
|||
Initial invocation of MsMpEng.exe on new PC breaks PPTP
Paul wrote:
snip If your PPTP isn't working, The builtin, native Microsoft W10P VPN PPTP client connection now works without a hitch. Many PC manufacturers ship factory fresh PCs with a cloned preinstall image on the hard drive. After a factory fresh PC is powered on and booted for the very first time the preinstall image creates a full blown Windows OS image on the hard drive. It takes a while for that to happen. After the process completes, the Windows OS boots for the first time. At that point the fresh Windows install spends a fair amount of time "getting its house in order" and it tends to display the circle of circles AKA "circle of death." A brand spanking new Windows install can spend a couple of days "getting its house in order" or "polishing up" as Redmond likes to say. Although you can logon during that period, updates and other initial setup takes priority. It was during this pre-dawn period with a lot of "runonce" processes in the background, that Microsoft W10P VPN PPTP client connection failed for the first and only time. BTW, Microsoft W10P VPN PPTP client connection works superbly to logon to remote Domains using AD credentials from anywhere in the world "on the fly." Redmond did good this time. The plot thickens. It turns out that VPN servers can only handle five concurrent VPN sessions by default. My three brand new factory fresh PCs may have demanded one too many concurrent VPN sessions on a busy production server. When a connection to a totally different VPN server was attempted, the builtin, native Microsoft W10P VPN PPTP client connection also failed. But my patience may have been too exhausted by that point to give it enough time to succeed. If exhaustion of available sessions is the true culprit, then this is yet another example of the chaos created by poor error handling coupled with an inadequate error message. For what little good it does, the "don't want good, want it Tuesday" mentality that pervades the industry can be scapegoated, in this case. BTW, anyone who knows and shares the registry key that controls concurrent VPN sessions on Windows Server20nn, rocks. Thank you, 73, -- Don Kuenz KB7RPU There was a young lady named Bright Whose speed was far faster than light; She set out one day In a relative way And returned on the previous night. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|