Prev: NTStatus codes missing
Next: How to support multiple USB Driver, but does not modify the INF
From: spazekaat on 25 Mar 2010 22:27
John,

I just tried to put up a separate controller and client, and they couldn't
"find" each other as far as DTM was concerned.

My thinking is as follows:

Provide a tool whereby either/both the controller or client could bring up a
dialog where one could interrogate the network and the user could click on
the appropriate machine to talk to....sort of like MS Explorer's "Map network
drive" for a UI. The tool would then interrogate the selected machine to see
if a WTT service could be established between the two.

This may also be useful if one wants to switch a client between different
controllers.

Reinstalling the Client is a clumsy and somewhat unreliable way of doing
things, as I have discovered.

Does this sound reasonable and doable?

Thanks.


"spazekaat" wrote:

> Hi John,
>
> Yes, tried all that several times but to no avail.
>
> "John Garcia" wrote:
>
> > I'm interested in understanding this more. You said you uninstalled and
> > reinstalled DTM Client and it didn't show up. Did you refresh studio and
> > look in the “Default Pool” for your machine?
> >
> > John Garcia [MSFT]

From: Jeff Thiesen [MSFT] on 31 Mar 2010 13:50
there is a command line tool in the DTM client/controller directories that
uses the same communication protocal to check connectivitiy

try using "WTTCMD.exe ping <machinename>"
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"spazekaat" wrote:

> John,
>
> I just tried to put up a separate controller and client, and they couldn't
> "find" each other as far as DTM was concerned.
>
> My thinking is as follows:
>
> Provide a tool whereby either/both the controller or client could bring up a
> dialog where one could interrogate the network and the user could click on
> the appropriate machine to talk to....sort of like MS Explorer's "Map network
> drive" for a UI. The tool would then interrogate the selected machine to see
> if a WTT service could be established between the two.
>
> This may also be useful if one wants to switch a client between different
> controllers.
>
> Reinstalling the Client is a clumsy and somewhat unreliable way of doing
> things, as I have discovered.
>
> Does this sound reasonable and doable?
>
> Thanks.
>
>
> "spazekaat" wrote:
>
> > Hi John,
> >
> > Yes, tried all that several times but to no avail.
> >
> > "John Garcia" wrote:
> >
> > > I'm interested in understanding this more. You said you uninstalled and
> > > reinstalled DTM Client and it didn't show up. Did you refresh studio and
> > > look in the “Default Pool” for your machine?
> > >
> > > John Garcia [MSFT]
>
First  |  Prev  | 
Pages: 1 2
Prev: NTStatus codes missing
Next: How to support multiple USB Driver, but does not modify the INF