after all, I could migrate to the i6xx-branch with NDIS 6.
Some time ago, during the 2.3.5 ages, I simply couldn't get the tunnel to pass traffic and keep alive also just failed.
Even in Windows 8.1, only NDIS 5 worked flawlessly, let alone 2k8 R2 and Win 7, like stated by one fellow in bug #316.
Since 2.3.7i603, NDIS 6 has become a charm on 90 Percent of all clients and the server, but there are 2 Win 8.1 Clients that Just. Won't. Do. Shit.
Bug #430 is reported closed, but the symptoms are mentioned there.
We had flooded logs only once, it's more a question of "i/o operation aborted" and "route deletion failed" heading for "closing tap interface".
A reboot fixes the issue in most cases.
It just happens with a cold boot.
<edit> Having said and read that again, I will have an eye on quick start. I just have no own Windows and tried to automate stuff in order not to see it to often. Server is 2k8R2 and can't control all the Win 8.1 stuff by GPO </edit>
Yeah, I installed "as administrator".
The client is run as a service during startup, enabling domain controller connectivity.
Another Win 8.1 Client works great.
In dark memories, it was likely also affected by the problem and showed some command line for a shut of the lid when having a chicken-based ritual in device manager, but I wouldn't swear.
I tried the following solution from bug #316 setting tap interface to "always connected" and appending
Code: Select all
route-method exe
route-delay 5 120
tap-sleep 5
I just did that and people must try and notify me on results before I can judge the step.
I just can't get the point of it.
It has nothing to do with hibernation AND: no windows logs. Windows logging just doesn't say a single word or digit and network and sharing center and "adapters" state an active tap adapter with properties pretending "device works, no faults" (sorry, I have no clue about what English GUIs would state).
Everything permission-related or UAC-like is defined in GPOs and should be the same for all clients.
To make a summary: a year ago, NDIS 5 Tap was the only thing that worked on all machines including Win 7, 2k8R2 and 8.1.
Now, NDIS 6 seems to be picky about machines, not operating systems.
No, the two delinquents are each way different one from the other, different manufacturers, different networking hardware, nothing shady left preinstalled, but error logs clean, working great - and did so with NDIS 5 Tap. On Windows 8.1.
If anyone had a suggestion, I would appreciate that very much and be thankful, but I already plan to buy a goat for another ritual in device manager and then try out vegan sacrifice.
I admit I'm not uber-admin, I use linux exclusively for 10 years now (which accepts commands and doesn't require sacrifice) and came to manage a windows corporate network by hilarious circumstance.
So, don't think your suggestion would be to stupid to me.
Maybe I just already considered what you suggest.
Thanks a lot, in advance.
addi
