From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_002F_01C2C229.6E516170
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Broadcast or Hybrid are both fine.  To test name resolution you can =
use NET VIEW \\machinename or even PING machinename.  If these work, = even
if you get access denied, then name resolution is working OK.  I = would
verify that first before considering browser issues.

Rich

  "Randall Parker"  wrote in message =
news:MPG.1898b64f8ee9aafd98c43c{at}news.barkto.com...
  Rich,

  I verified my NT machine and cables and hub by connecting the NT =
machine to=20
  another NT machine thru the hub with the exact same cable as I had =
connected to=20
  the Win2k machine. Network Neighborhood works fine between the NT =
machines. So=20
  I think all that is good.=20

  My NT Machine's IPCONFIG /ALL is:

  [j:\doc\winclients\iocomp]ipconfig /all

  Windows NT IP Configuration

          Host Name . . . . . . . . . : talldog
          DNS Servers . . . . . . . . : 4.2.2.1
                                        205.254.224.2
                                        216.144.8.10
          Node Type . . . . . . . . . : Broadcast
          NetBIOS Scope ID. . . . . . :
          IP Routing Enabled. . . . . : No
          WINS Proxy Enabled. . . . . : No
          NetBIOS Resolution Uses DNS : No

  Ethernet adapter Lne100tx3:

          Description . . . . . . . . : Linksys LNE100TX Fast Ethernet =
Adapter
          Physical Address. . . . . . : 00-A0-CC-E7-AE-29
          DHCP Enabled. . . . . . . . : No
          IP Address. . . . . . . . . : 4.40.49.194
          Subnet Mask . . . . . . . . : 255.255.255.248
          Default Gateway . . . . . . : 4.40.49.193

  Ethernet adapter RTL81392:

          Description . . . . . . . . : NDIS 4.0 driver

          Physical Address. . . . . . : 00-50-BF-04-E7-1A
          DHCP Enabled. . . . . . . . : No
          IP Address. . . . . . . . . : 207.105.135.10
          Subnet Mask . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . :

  PPP adapter NdisWan6:

          Description . . . . . . . . : NdisWan Adapter
          Physical Address. . . . . . : 00-00-00-00-00-00
          DHCP Enabled. . . . . . . . : No
          IP Address. . . . . . . . . : 0.0.0.0
          Subnet Mask . . . . . . . . : 0.0.0.0
          Default Gateway . . . . . . :



  Note the Broadcast node type. Its the RTL81392 adapter that is =
connecting to=20
  the local net.=20

  The Dell Win2k machine has only one ethernet adapter and its Node Type =
is=20
  Hybrid. I can't tell whether Hybrid is the equivalent of m-node or =
h-node. But=20
  shouldn't Hybrid be compatible with Broadcast? I assume that Broadcast =
is b-
  node.=20

  NetBIOS over TCP/IP: One of them could be using it and the other might =
not be.=20
  I can't figure out how I'd make them be the same in this respect. I =
can see=20
  which prootocols are enabled on which adapter on NT. But where is the =
choice of=20
  NetBIOS over TCP/IP made on NT and on Win2k? I can't find it.=20


  On Wed, 22 Jan 2003 13:19:13 -0800 esteemed "Rich" 
did hold forth =
thusly:
  >    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.
  >=20
  >    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.
  >=20
  >    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.
  >=20
  > Rich
  >
------=_NextPart_000_002F_01C2C229.6E516170
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Broadcast
or Hybrid are =
both=20
fine.  To test name resolution you can use NET VIEW file://\\machinename">\\machinename or
even PING=20 machinename.  If these work, even if you get access
denied, then = name=20
resolution is working OK.  I would verify that first before = considering=20
browser issues.
 
Rich
 

  "Randall Parker" <rgparker{at}west.net>">mailto:rgparker{at}west.net">rgparker{at}west.net>
wrote in =
message news:MPG.1898b64=
f8ee9aafd98c43c{at}news.barkto.com...Rich,I=20
  verified my NT machine and cables and hub by connecting the NT machine =
to=20
  another NT machine thru the hub with the exact same cable as I had =

  connected to the Win2k machine. Network Neighborhood works fine =
between=20
  the NT machines. So I think all that is good. My NT =
Machine's=20
  IPCONFIG /ALL is:[j:\doc\winclients\iocomp]ipconfig=20
  /allWindows NT IP=20
 
Configuration       
Host =
Name . .=20
  . . . . . . . :
talldog       
=
DNS=20
  Servers . . . . . . . . :=20
  =
4.2.2.1          &n=
bsp;           &nb=
sp;           &nbs=
p;  =20
  =
205.254.224.2         &n=
bsp;           &nb=
sp;           &nbs=
p;   =20
 
216.144.8.10       
Node Type . =
. . . .=20
  . . . . :
Broadcast       
=
NetBIOS=20
  Scope ID. . . . . .
:       
IP =
Routing=20
  Enabled. . . . . :
No       
=
WINS Proxy=20
  Enabled. . . . . :
No       
=
NetBIOS=20
  Resolution Uses DNS : NoEthernet adapter=20
 
Lne100tx3:       
=
Description . . .=20
  . . . . . : Linksys LNE100TX Fast Ethernet=20
 
Adapter       
Physical =
Address. . . .=20
  . . :
00-A0-CC-E7-AE-29       
=
DHCP=20
  Enabled. . . . . . . . : =
No       
IP=20
  Address. . . . . . . . . :=20
 
4.40.49.194       
Subnet Mask =
. . . .=20
  . . . . : =
255.255.255.248       =20
  Default Gateway . . . . . . : 4.40.49.193Ethernet adapter=20
 
RTL81392:       
=
Description . . .=20
  . . . . . : NDIS 4.0 =
driver       =20
  Physical Address. . . . . . :=20
 
00-50-BF-04-E7-1A       
DHCP =
Enabled.=20
  . . . . . . . :
No       
IP =
Address. .=20
  . . . . . . . : =
207.105.135.10       =20
  Subnet Mask . . . . . . . . :=20
 
255.255.255.0       
Default =
Gateway .=20
  . . . . . :PPP adapter=20
 
NdisWan6:       
=
Description . . .=20
  . . . . . : NdisWan =
Adapter       =20
  Physical Address. . . . . . :=20
 
00-00-00-00-00-00       
DHCP =
Enabled.=20
  . . . . . . . :
No       
IP =
Address. .=20
  . . . . . . . :
0.0.0.0       
=
Subnet=20
  Mask . . . . . . . . : =
0.0.0.0       =20
  Default Gateway . . . . . . :Note
the Broadcast node =
type. Its=20
  the RTL81392 adapter that is connecting to the local net. =
The Dell=20
  Win2k machine has only one ethernet adapter and its Node Type is =
Hybrid. I=20
  can't tell whether Hybrid is the equivalent of m-node or h-node. But=20
  shouldn't Hybrid be compatible with Broadcast? I assume that =
Broadcast is=20
  b-node. NetBIOS over TCP/IP: One of them
could be using it =
and the=20
  other might not be. I can't figure out how I'd make them be the =
same in=20
  this respect. I can see which prootocols are enabled on which =
adapter on=20
  NT. But where is the choice of NetBIOS over TCP/IP made on NT and =
on=20
  Win2k? I can't find it. On Wed, 22 Jan 2003
13:19:13 -0800 =

  esteemed "Rich" <{at}> did hold forth =
thusly:>    You=20
  don't need or want NetBEUI.  If you have no centralized name =
server you=20
  should make sure that you have NetBIOS over TCP/IP enabled.  =
That's it=20
  for 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=
=20
  and 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.>=20
  >    The network neighborhood
behavior is =
something=20
  else.  For that you need a browser.  See http://www.microsoft.com/technet/prodtechnol/winntas/reskit/net/c=
hptr3.asp">http://www.microsoft.com/technet/prodtechnol/winntas/reskit/ne=
t/chptr3.asp.>=20
  >
Rich>

------=_NextPart_000_002F_01C2C229.6E516170--

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