From: Ellen K. 

This is FASCINATING!

On Wed, 22 Jan 2003 18:37:48 -0800, "Rich"  wrote in message
:

>   First off, these are two different things.
>
>   NET USE and NET VIEW only require that name resolution is able to resolve
the server name.  Likely you are using broadcast resolution so as long as
the server to which you are attempt to connect is located within the scope
of a network broadcast the name can be resolved and the connection attempt
can move forward.
>
>   The network neighborhood, in a non-domain environment, there are two
different schemes.  One is where each server is configured to broadcast
it's presence and each client listens to the broadcasts and maintains its
own list of nearby servers.  These broadcasts are disabled by default in
Windows and have been for many years.  There is a checkbox somewhere to
enable this that makes reference to LAN Manager 2.0 compatibility.  The
other scheme is using browser masters.  Using an election process one
machine on the subnet is designated as the master browser and it maintains
the list of all servers. When your client wants to view the network
neighborhood it queries the browser master for the list.  If the master
goes off line the other machines eventually notice and a new master is
elected.  It can then take a bit of time for the master browser list to
repopulate.  There are options to control whether or not any particular
machine is allowed to be a browser master.  See
>http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse
.asp.
>
>Rich
>
>  "Glenn Meadows"  wrote in message
news:3e2f38f5{at}w3.nls.net...
>  I like this discussion.  Rich, why at certain times in the middle of the
day, I will lose access to browse the domain, BUT, form a command prompt, I
can do Net View \\server, net use \\server\resource, etc.  When looking in
the workgroup, I only see my local machine.
>
>  Same question for a Win98 machine.  I can select "Log On
Domain", provide
the Domain name (same as other Win98 machines on the Lan), and enter a
valid user name and password, the Domain is properly filled in, and get a
"No Domain Controller was available" error message.  So, I switch
to a NON domain login, using the Domain name as a Workgroup.  I get logon
to the local machine, AND network connections that were set to re-connect
at logon re-connect (I've remapped My Documents to a network folder unique
for each user), but there are NO computers visible in Network Neighborhood.
 Same thing though, from a command line, I can access the network
resources.  When using Network Neighborhood, I get "Network
unavailable".
>
>  I did a full re-install of Win98se today on the current machine that's
giving this problem.  Using DHCP, only TCPIP loaded as a protocol, and set
as the Default Protocol.
>
>  Very odd.
>
>  Any light that can be shed would be appreciated.
>
>  TIA
>
>  --
>  Glenn M.
>
>
>    "Rich"  wrote in message news:3e2f0900{at}w3.nls.net...
>       You don't need or want NetBEUI.  If you have no centralized name server
you should make sure that you have NetBIOS over TCP/IP enabled.  That's it
for protocols.
>
>       For name resolution, run IPCONFIG /all on both machines and check the
Node Type value.  See http://support.microsoft.com/default.aspx?scid=kb%3ben-us
%3b160177 and http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/prjj
_ipa_kopf.asp.
>
>       The network neighborhood behavior is something else.  For that you need
a browser.  See http://www.microsoft.com/technet/prodtechnol/winntas/reskit/net
/chptr3.asp.
>
>    Rich
>
>      "Randall Parker"  wrote in message
news:MPG.1898a015bc3404b998c43b{at}news.barkto.com...
>      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