From: Randall Parker 

I put the Win2k machine into the same Workgroup name as the NT machine and
rebooted. Still no joy.

The guy who usually uses the Win2k machine says he's used it with network
neighborhood. But maybe he has it configured with a different protocol for
it?

I went into the Win2k Network and Dial-up Connections, right clicked on
Local Area Connection, chose properties. There are 4 options in the list
and all are checked:
   Client for Microsoft Networks
   File and Printer Sharing for Microsoft Networks
   3Com BCAITDI DMI TDI
   Internet Protocol

The "Client for Microsoft Networks" has a properties dialog that
shows only an RPC Service tab with "Name service provider" as
"Windows Locator". The "Network address" control is
greyed out.

But choosing the checked "File and Printer Sharing for Microsoft
Networks" results in the Properties button becoming greyed out. Why is
that?

Is he lacking NetBEUI protocol on the Win2k machine? Are there different
ways to configure Network Neighborhood using different underlying
protocols?

On Wed, 22 Jan 2003 11:02:28 -0800 esteemed Randall Parker did hold forth thusly:
> Hello. Long time no see and all that. Been blogging my brains out.
> http://www.futurepundit.com if you want to see what I've been up to as a huge
> use of my recreational time.
>
> I have  Win2k machine and an NT machine that I've plugged into a hub. I see
> lights on the hub connection and on the NICs. I figure I have electrical
> contact at least. Now some dumb questions since its been a while since I've
> done this.
>
> 1) Do machines have to be in the same group name to see each other?
>    On the Win2k machine I can do a search for a computer by name but there is
> no way to tell it to search in a different workgroup name. I'm guessing that
> the difference in workgroup names is the cause of the no-see no-find by the
two
> computers.
>
> 2) WHere do you change the workgroup name in Win2k?
>
> 3) Can one make a Win2k machine be in two groups at once? If so, how?
>
> 4) Is there some other command that is like netstat that tells more stuff? Or
> should I be using netstat with some command line option? Isn't there some
> command for seeing the NICs and their bindings? I think I've learned and
> forgotten that command a half dozen times over the years.
>
> 5) Is there a way to know whether a ping command is really going out a
> particular NIC?
>
> 6) Is there a superping command that basically amounts to saying "Send this
> ping out this particular NIC"?
>
> 7) Is there a way to verify some machine's ability to even respond to a ping
in
> the first place? How can I know if there is no ping response that it isn't
just
> because one of the machines has pings filtered in its firewall settings? I
have
> ZoneAlarm on one of them with settings I can't remember since its been so
long
> since I messed with it. The other machine (the Win2k machine) was lent to me
> for a project (cool Borland C++ Builder graphics app that I'm writing that's
> fun to write) and I have no idea what its settings are for.
>
> 8) Any handy tools for picking apart these sorts of problems that I ought to
be
> using?
>

--- BBBS/NT v4.01 Flag-4