Hello,
I am working on a ndisim. It seems that I have a problem on some machines with
QoS service. When it is enabled, no more packets come from upper layers. Can
anyone tell me why, or at least heard of such thing? I repeat - this does not
happen on all machine - seems to be a random thing.
Thank you,
Andrei Ciubotaru
On Oct 15, 2005, at 4:31 AM, Andrei Ciubotaru wrote:
I am working on a ndisim. It seems that I have a problem on some
machines with
QoS service. When it is enabled, no more packets come from upper
layers. Can
anyone tell me why, or at least heard of such thing? I repeat -
this does not
happen on all machine - seems to be a random thing.
This obviously shouldn’t be happening; I have a few production IM
drivers and rarely hear of binding issues that don’t originate with
some pre-existing pathological state on the installation computer.
If you have any kind of repro, try building the latest unmodified
PassThru sample and see if it also reproduces. If you happen to catch
a broken instance, look at bindings in the debugger; that might give
you a clue as to what’s up.
I think the QoS driver concern is a red herring; removing it changes
bindings and could cure the problem, and it’s installed on a lot of
computers, so it’ll always seem to be there on the broken ones.
When it breaks, does it stay broken until something is done (i.e.
across reboots), or does it fix itself after a reboot?
Steve Dispensa
MVP - Windows DDK
www.kernelmustard.com
The problem dissapears only if I get into network properties and
uncheck the QoS
service or uninstall it. Even if I reboot I still have the same problem.
Quoting Steve Dispensa :
> On Oct 15, 2005, at 4:31 AM, Andrei Ciubotaru wrote:
>> I am working on a ndisim. It seems that I have a problem on some
>> machines with
>> QoS service. When it is enabled, no more packets come from upper
>> layers. Can
>> anyone tell me why, or at least heard of such thing? I repeat -
>> this does not
>> happen on all machine - seems to be a random thing.
>
> This obviously shouldn’t be happening; I have a few production IM
> drivers and rarely hear of binding issues that don’t originate with
> some pre-existing pathological state on the installation computer.
>
> If you have any kind of repro, try building the latest unmodified
> PassThru sample and see if it also reproduces. If you happen to catch
> a broken instance, look at bindings in the debugger; that might give
> you a clue as to what’s up.
>
> I think the QoS driver concern is a red herring; removing it changes
> bindings and could cure the problem, and it’s installed on a lot of
> computers, so it’ll always seem to be there on the broken ones.
>
> When it breaks, does it stay broken until something is done (i.e.
> across reboots), or does it fix itself after a reboot?
>
>
> ----------------------------------
> Steve Dispensa
> MVP - Windows DDK
> www.kernelmustard.com
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@icode.ro
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
On Oct 15, 2005, at 9:02 PM, Andrei Ciubotaru wrote:
The problem dissapears only if I get into network properties and
uncheck the QoS
service or uninstall it. Even if I reboot I still have the same
problem.
What happens if you add another component or change bindings in other
ways? Also, are there any funny entries under the network devices
section of device manager? That’s usually a dead giveaway when there
are binding problems. Are there any other IMs installed on these
boxes besides the QoS driver?
In my experience, 90% of these binding problems are due to a pre-
existing broken installation of some other network-related software
on the box.
One other point: if your installer is based on the old snetcfg code,
you might want to take the time to go through it again and compare it
with the bindview code. Also, you might try using the latest DDK’s
passthru INFs.
Steve Dispensa
MVP - Windows DDK
www.kernelmustard.com
I think my installation was the problem. Now it works. Thank you for
your help.
Quoting Steve Dispensa :
> On Oct 15, 2005, at 9:02 PM, Andrei Ciubotaru wrote:
>
>> The problem dissapears only if I get into network properties and
>> uncheck the QoS
>> service or uninstall it. Even if I reboot I still have the same problem.
>
> What happens if you add another component or change bindings in other
> ways? Also, are there any funny entries under the network devices
> section of device manager? That’s usually a dead giveaway when there
> are binding problems. Are there any other IMs installed on these
> boxes besides the QoS driver?
>
> In my experience, 90% of these binding problems are due to a pre-
> existing broken installation of some other network-related software
> on the box.
>
> One other point: if your installer is based on the old snetcfg code,
> you might want to take the time to go through it again and compare it
> with the bindview code. Also, you might try using the latest DDK’s
> passthru INFs.
>
>
>
>
> ----------------------------------
> Steve Dispensa
> MVP - Windows DDK
> www.kernelmustard.com
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@icode.ro
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>