TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: Rich
from: Glenn Meadows
date: 2003-01-25 21:42:40
subject: Re: Stupid Network Neighborhood Questions

From: "Glenn Meadows" 

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C2C4BA.AFE3FAB0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Update on what I've changed.

Today, I disabled Netbios over TCPIP on ONE of the two NICS.  Rebooted =
all machines, and all are still able to see shares off of the server.  I =
also saw a big increase in transfer speed to/from the server.  I've been =
moving some large files around (full resolution CD Audio files), and =
noted that transfer over our 100mb network was agonizingly slow going =
only to the server.  Transfers to other machines on the lan were about = as
fast as I would expect.  I suppose the two NICS seeing each other, = that
was causing the error I was seeing, could have been doing something = to
slow things down.  Not sure, the only way to know would be to = re-enable
the second NIC for netbios and try again.

Since we only have 3 computers still on the lan running Win98, I've =
thought about just loading HOSTS files on those three machines, since =
they only need to get to the server (no access to other workstations on =
the network).  Then put in a Hosts file on each machine that defines the =
server, and split the machines between the two IP's for the server, sort =
of a poor mans load balancing act.

There are probably some serious holes in this theory, so I've got the =
bullet proof vest on to take the shots .

--=20
Glenn M.


  "Rich"  wrote in message news:3e2f53a7{at}w3.nls.net...
     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/ntb=
rowse.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

    --=20
    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=3Dkb%3ben-us%3b160177 and =
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/prjj_ipa_kop=
f.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.as=
p.

      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=20
        rebooted. Still no joy.=20

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

        I went into the Win2k Network and Dial-up Connections, right =
clicked on Local=20
        Area Connection, chose properties. There are 4 options in the =
list and all are=20
        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=20
        RPC Service tab with "Name service provider" as "Windows =
Locator". The "Network=20
        address" control is greyed out.=20

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

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

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








Update on what I've changed.
 
Today, I disabled Netbios over TCPIP on ONE of the two NICS.  =
Rebooted=20
all machines, and all are still able to see shares off of the =
server.  I=20
also saw a big increase in transfer speed to/from the server. 
I've = been=20
moving some large files around (full resolution CD Audio files), and = noted that=20
transfer over our 100mb network was agonizingly slow going only to the=20
server.  Transfers to other machines on the lan were about as fast
= as I=20
would expect.  I suppose the two NICS seeing each other, that was
= causing=20
the error I was seeing, could have been doing something to slow things=20
down.  Not sure, the only way to know would be to re-enable the =
second NIC=20
for netbios and try again.
 
Since we only have 3 computers still on the lan running Win98, I've =
thought=20
about just loading HOSTS files on those three machines, since they only = need to=20
get to the server (no access to other workstations on the =
network).  Then=20
put in a Hosts file on each machine that defines the server, and split = the=20
machines between the two IP's for the server, sort of a poor mans load = balancing=20
act<grin>.
 
There are probably some serious holes in this theory, so I've got =
the=20
bullet proof vest on to take the shots <VBG>.
-- Glenn M.
 
 
"Rich" <{at}> wrote in message news:3e2f53a7{at}w3.nls.net... First off, these are two = different=20 things. NET USE and NET VIEW = only require=20 that name resolution is able to resolve the server name. Likely = you are=20 using broadcast resolution so as long as the server to which you are = attempt=20 to connect is located within the scope of a network broadcast the name = can be=20 resolved and the connection attempt can move forward. The network = neighborhood, in a=20 non-domain environment, there are two different schemes. One is = where=20 each server is configured to broadcast it's presence and each client = listens=20 to the broadcasts and maintains its own list of nearby servers. = These=20 broadcasts are disabled by default in Windows and have been for many=20 years. There is a checkbox somewhere to enable this that makes = reference=20 to LAN Manager 2.0 compatibility. The other scheme is using = browser=20 masters. Using an election process one machine on the subnet is=20 designated as the master browser and it maintains the list of all=20 servers. When your client wants to view the network neighborhood = it=20 queries the browser master for the list. If the master goes off = line the=20 other machines eventually notice and a new master is elected. It = can=20 then take a bit of time for the master browser list to = repopulate. There=20 are options to control whether or not any particular machine is = allowed to be=20 a browser master. See http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prods= pecs/ntbrowse.asp">http://www.microsoft.com/technet/prodtechnol/winntas/d= eploy/prodspecs/ntbrowse.asp. Rich
"Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net> = wrote in=20 message news:3e2f38f5{at}w3.nls.net... I like this discussion. Rich, why at certain times in the = middle=20 of the day, I will lose access to browse the domain, BUT, form a = command=20 prompt, I can do Net View \\server;, = net use \\server\resource;, etc. = When=20 looking in the workgroup, I only see my local machine. Same question for a Win98 machine. I can select "Log On = Domain",=20 provide the Domain name (same as other Win98 machines on the Lan), = and enter=20 a valid user name and password, the Domain is properly filled in, = and get a=20 "No Domain Controller was available" error message. So, I = switch to a=20 NON domain login, using the Domain name as a Workgroup. I get = logon to=20 the local machine, AND network connections that were set to = re-connect at=20 logon re-connect (I've remapped My Documents to a network folder = unique for=20 each user), but there are NO computers visible in Network=20 Neighborhood. Same thing though, from a command line, I can = access the=20 network resources. When using Network Neighborhood, I get = "Network=20 unavailable". I did a full re-install of Win98se today on the current machine = that's=20 giving this problem. Using DHCP, only TCPIP loaded as a = protocol, and=20 set as the Default Protocol. Very odd. Any light that can be shed would be appreciated. TIA -- Glenn M.
"Rich" <{at}> wrote in message news:3e2f0900{at}w3.nls.net... You don't need or = want=20 NetBEUI. If you have no centralized name server you should = make sure=20 that you have NetBIOS over TCP/IP enabled. That's it for=20 protocols. For name resolution, = run=20 IPCONFIG /all on both machines and check the Node Type = value. See http://support.microsoft.com/default.aspx?scid=3Dkb%3ben-us%3b160= 177">http://support.microsoft.com/default.aspx?scid=3Dkb%3ben-us%3b160177= and=20 http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/prjj= _ipa_kopf.asp">http://www.microsoft.com/technet/prodtechnol/winxppro/resk= it/prjj_ipa_kopf.asp. The network = neighborhood=20 behavior is something else. For that you need a = browser. See=20 http://www.microsoft.com/technet/prodtechnol/winntas/reskit/net/c= hptr3.asp">http://www.microsoft.com/technet/prodtechnol/winntas/reskit/ne= t/chptr3.asp. Rich "Randall Parker" <rgparker{at}west.net>">mailto:rgparker{at}west.net">rgparker{at}west.net> = wrote in=20 message news:MPG.1898a01= 5bc3404b998c43b{at}news.barkto.com...I=20 put the Win2k machine into the same Workgroup name as the NT = machine and=20 rebooted. Still no joy. The guy who usually uses the = Win2k=20 machine says he's used it with network neighborhood. But = maybe he=20 has it configured with a different protocol for it? I = went into=20 the Win2k Network and Dial-up Connections, right clicked on = Local=20 Area Connection, chose properties. There are 4 options in = the list=20 and all are checked: Client for Microsoft=20 Networks File and Printer Sharing for Microsoft=20 Networks 3Com BCAITDI DMI TDI = Internet=20 ProtocolThe "Client for Microsoft Networks" has a = properties=20 dialog that shows only an RPC Service tab with "Name service = provider" as "Windows Locator". The "Network address" = control is=20 greyed out. But choosing the checked "File and Printer = Sharing=20 for Microsoft Networks" results in the Properties button = becoming=20 greyed out. Why is that?Is he lacking NetBEUI protocol = on the=20 Win2k machine? Are there different ways to configure Network = Neighborhood using different underlying protocols?On = Wed, 22 Jan=20 2003 11:02:28 -0800 esteemed Randall Parker did hold forth=20 thusly:> Hello. Long time no see and all that. Been = blogging=20 my brains out. > http://www.futurepundit.com;">http://www.futurepundit.comhttp://www.futurepundit.com">http://www.futurepundit.com; if=20 you want to see what I've been up to as a huge > use of = my=20 recreational time. > > I have Win2k machine = and an=20 NT machine that I've plugged into a hub. I see > lights = on the=20 hub connection and on the NICs. I figure I have electrical = >=20 contact at least. Now some dumb questions since its been a while = since=20 I've > done this.> > 1) Do machines have to = be in=20 the same group name to see each other?> = On the=20 Win2k machine I can do a search for a computer by name but there = is=20 > no way to tell it to search in a different workgroup = name. I'm=20 guessing that > the difference in workgroup names is the = cause of=20 the no-see no-find by the two > computers.> = > 2)=20 WHere do you change the workgroup name in Win2k?> = > 3) Can=20 one make a Win2k machine be in two groups at once? If so, = how?>=20 > 4) Is there some other command that is like netstat = that tells=20 more stuff? Or > should I be using netstat with some = command line=20 option? Isn't there some > command for seeing the NICs = and their=20 bindings? I think I've learned and > forgotten that = command a=20 half dozen times over the years.> > 5) Is there a = way to=20 know whether a ping command is really going out a > = particular=20 NIC? > > 6) Is there a superping command that = basically=20 amounts to saying "Send this > ping out this particular=20 NIC"?> > 7) Is there a way to verify some = machine's=20 ability to even respond to a ping in > the first place? = How can I=20 know if there is no ping response that it isn't just > = because=20 one of the machines has pings filtered in its firewall settings? = I have=20 > ZoneAlarm on one of them with settings I can't remember = since=20 its been so long > since I messed with it. The other = machine (the=20 Win2k machine) was lent to me > for a project (cool = Borland C++=20 Builder graphics app that I'm writing that's > fun to = write) and=20 I have no idea what its settings are for. > > 8) = Any handy=20 tools for picking apart these sorts of problems that I ought to = be=20 >=20 using?>= ------=_NextPart_000_0017_01C2C4BA.AFE3FAB0-- --- BBBS/NT v4.01 Flag-4
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/1.45)
SEEN-BY: 633/267 270
@PATH: 379/1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.