Re: problem with NDIS test

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks for the info. It is very helpful. It appears that the test client and
server uses UDP port 25000 to coordinate startup and shutdown. They use IP
multicast address 234.13.X.X to talk to each other. However, both the client
and server has multiple network interfaces and there is not a route for this
address. Furthermore, the default gateway may change during WHQL tests since
drivers and loaded/unloaded. As a result, these packets sometimes go out of
the "wrong" interface and never reach the other party. The solution is to
manually add a persistent route on client and server for the above address
that routes these packets through the "messaging" interface.


"Stephan Wolf [MVP]" <stewo68@xxxxxxxxxxx> wrote in message
news:1137423225.156271.305280@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Yes, I seem to remember we had the same problem years ago, i.e.
> NDISTest claims to complete immediately.
>
> Check the test log file(s). There should be some hints.
>
> Also check the debug output with a tool like DebugView, see my 2003
> article on NDISTest:
>
> "Testing Network Drivers with NDIS the Test Tool"
> http://www.wd-3.com/archive/NDISTest.htm
> (Some links are broken, but it's still worth reading I guess.)
>
> See also:
>
> "Using NDISTest During Driver Development"
> http://www.microsoft.com/whdc/DevTools/tools/NDIStest.mspx
>
> Stephan
> ---
> ning wrote:
>> Hi,
>>
>> I posted this message on the winlogo news group but that group seems to
>> have little activity. I have a strange problem with NdisTest. The
>> problem is that when I click start, the Test GUI does not show any
>> process
>> (Loading scripts, etc) and it displays "Test complete" after about 10
>> seconds. No logs are generated. It only occurs with
>> two machine setup. The problem sometimes goes away if I reboot the
>> switch/test machines. But then it can only be fixed by
>> uninstall/reinstall
>> HCT.
>>
>> Client and server are both directly plugged into one NetGear Hub. The
>> support card on the server is plugged into another hub. Client test
>> adapter
>> access the support adapter through VPN software.
>>
>> It appears that the test server (or client) would ignore the UDP packet
>> send
>> from the
>> client during initial test start. It is almost like that the server keeps
>> the client information in some file or registry and doesn't clean them
>> up.
>> But deleting NDTEST related registry key does not help.
>>
>> I wonder if anyone has seen this before and could offer some suggestions.
>>
>> Thank you,
>>
>> Ning
>


.

Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)
  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)