From: Ken Yeo (kenyeo@xxxxxxxxxxxxxxx)
Date: Wed Apr 25 2001 - 19:04:56 GMT-3
Zorro,
The customer want to be able to go to network neighborhood and look for any
workstation in the networks and map a drive.
In summary, to run Microsoft Peer to Peer networking aross multiple subnets
in a pure Netware environment is a pain.
Ken
----- Original Message -----
From: "Mask Of Zorro" <ciscokid00@hotmail.com>
To: <kenyeo@on-linecorp.com>; <Aaryn.Pickell@getronics.com>;
<vijay.venkatesh@usa.net>; <ccielab@groupstudy.com>
Sent: Thursday, April 19, 2001 1:25 PM
Subject: Re: [Network Neighborhood - Multiple Subnets - Workgroup only - No
Domain.]
> Obviously there is a solution to this, but before we go into that, I have
a
> question:
>
> Do you intend to use peer-to-peer networking services among your Windows
> clients? The origninal post indicates that these systems are clients of
> Netware 5 servers. The question is, why browse the clients at all? If
there
> will not be any client-to-client file or printer sharing, then all you
> should really need to see are the Netware servers.
>
> Quite frankly, in a Netware environment, there is really not much sense to
> running peer-to-peer Microsoft networking. If you need to share files or
> devices among small logical groups of clients, you'd be better off doing
it
> with the Netware servers and services. You get much greater flexibility in
> terms of security and administration that way. I can't see any
justification
> for Microsoft networking in a stricly Netware environment. If you add NT
> servers, then things start to change, but without them, there just isn't
any
> point.
>
> If you are not running peer-to-peer connectivity, then you'd be better off
> disabling File and Printer Sharing and making all your clients disappear
> from Network Neighborhood.
>
> Z
>
>
> >From: "Ken Yeo" <kenyeo@on-linecorp.com>
> >Reply-To: "Ken Yeo" <kenyeo@on-linecorp.com>
> >To: "Pickell, Aaryn" <Aaryn.Pickell@getronics.com>, "'Vijay
> >Venkatesh'" <vijay.venkatesh@usa.net>, <ccielab@groupstudy.com>
> >Subject: Re: [Network Neighborhood - Multiple Subnets - Workgroup only -
> >No Domain.]
> >Date: Thu, 19 Apr 2001 12:51:04 -0500
> >
> >Since there is not NT server available, NT domain is not an option.
> >Another thought is install NETBEUI on all workstations and bridge NETBEUI
> >traffice across the serial link and route IP. But as you said, it is not
a
> >good design because it forwards broadcasts across the serial link.
> >
> >Attached is the ip helper portion of the config, it is not working. Any
> >ideas?
> >
> >R1:
> >interface Ethernet0/0
> >
> >ip address 172.30.1.1 255.255.255.0
> >
----- Original Message -----
From: "Mask Of Zorro" <ciscokid00@hotmail.com>
To: <kenyeo@on-linecorp.com>; <Aaryn.Pickell@getronics.com>;
<vijay.venkatesh@usa.net>; <ccielab@groupstudy.com>
Sent: Thursday, April 19, 2001 1:25 PM
Subject: Re: [Network Neighborhood - Multiple Subnets - Workgroup only - No
Domain.]
> Obviously there is a solution to this, but before we go into that, I have
a
> question:
>
> Do you intend to use peer-to-peer networking services among your Windows
> clients? The origninal post indicates that these systems are clients of
> Netware 5 servers. The question is, why browse the clients at all? If
there
> will not be any client-to-client file or printer sharing, then all you
> should really need to see are the Netware servers.
>
> Quite frankly, in a Netware environment, there is really not much sense to
> running peer-to-peer Microsoft networking. If you need to share files or
> devices among small logical groups of clients, you'd be better off doing
it
> with the Netware servers and services. You get much greater flexibility in
> terms of security and administration that way. I can't see any
justification
> for Microsoft networking in a stricly Netware environment. If you add NT
> servers, then things start to change, but without them, there just isn't
any
> point.
>
> If you are not running peer-to-peer connectivity, then you'd be better off
> disabling File and Printer Sharing and making all your clients disappear
> from Network Neighborhood.
>
> Z
>
>
> >From: "Ken Yeo" <kenyeo@on-linecorp.com>
> >Reply-To: "Ken Yeo" <kenyeo@on-linecorp.com>
> >To: "Pickell, Aaryn" <Aaryn.Pickell@getronics.com>, "'Vijay
> >Venkatesh'" <vijay.venkatesh@usa.net>, <ccielab@groupstudy.com>
> >Subject: Re: [Network Neighborhood - Multiple Subnets - Workgroup only -
> >No Domain.]
> >Date: Thu, 19 Apr 2001 12:51:04 -0500
> >
> >Since there is not NT server available, NT domain is not an option.
> >Another thought is install NETBEUI on all workstations and bridge NETBEUI
> >traffice across the serial link and route IP. But as you said, it is not
a
> >good design because it forwards broadcasts across the serial link.
> >
> >Attached is the ip helper portion of the config, it is not working. Any
> >ideas?
> >
> >R1:
> >interface Ethernet0/0
> >
> >ip address 172.30.1.1 255.255.255.0
> >
> >ip helper-address 172.16.0.9
> >
> >ip helper-address 172.30.0.255
> >
> >no ip directed-broadcast
> >
> >ipx helper-address 1000.0000.f4af.003c
> >
> >ipx network 2502C01
> >
> >
> >
> >R2:
> >
> >interface FastEthernet1/0
> >
> >ip address 172.30.0.1 255.255.255.0
> >
> >ip helper-address 172.16.0.9
> >
> >ip helper-address 172.30.1.255
> >
> >no ip directed-broadcast
> >
> >duplex auto
> >
> >speed 10
> >
> >ipx helper-address 1000.0000.f4af.003c
> >
> >ipx network 2501C01
> >
> >!
> >
> >
> >
> >----- Original Message -----
> >From: "Pickell, Aaryn" <Aaryn.Pickell@getronics.com>
> >To: "'Vijay Venkatesh'" <vijay.venkatesh@usa.net>; "Ken Yeo"
> ><kenyeo@on-linecorp.com>; <ccielab@groupstudy.com>
> >Sent: Wednesday, April 18, 2001 3:30 PM
> >Subject: RE: [Network Neighborhood - Multiple Subnets - Workgroup only -
No
> >Domain.]
> >
> >
> > > As far as getting all routers to see each other in Network
Neighborhood,
> > > using ip helper-address is the cisco-centric fix. Per Microsoft, the
> >fix
> >is
> > > to use a domain model instead of a workgroup model.
> > >
> > > Ip helper was meant to forward UDP broadcasts, including but not
limited
> >to
> > > bootp. By default, there are a bunch of ports that will be forwarded
> >(tftp,
> > > netbios, bootp, etc.), and you can add more ports (or remove existing
> >ports)
> > > to the list with the ip forward-protocol command.
> > >
> > > By using this for windows browsing, though... you're going to consume
a
> >lot
> > > of your WAN bandwidth, because all windows netbios traffic is going to
> >be
> > > forwarded in all directions, not just the master browser elections.
> > >
> > > Ken, what you wrote should have worked. The theory is sound, anyway.
> >If
> > > you forward me your configs, maybe we can figure out what was missing.
> > >
> > > Aaryn Pickell - CCNP, CCDP, MCSE
> > > Senior Engineer - Routing Protocols
> > > Getronics Inc.
> > > Direct: 713-394-1609
> > > Email:aaryn.pickell@getronics.com
> > >
> > > This e-mail message and any attachments are confidential and may be
> > > privileged. If you are not the intended recipient, please notify me
> > > immediately by replying to this message and please destroy all copies
of
> > > this message and attachments. Thank you.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Vijay Venkatesh [mailto:vijay.venkatesh@usa.net]
> > > > Sent: Wednesday, April 18, 2001 3:01 PM
> > > > To: Ken Yeo; ccielab@groupstudy.com
> > > > Subject: Re: [Network Neighborhood - Multiple Subnets -
> > > > Workgroup only -
> > > > No Domain.]
> > > >
> > > >
> > > > Old issue -
> > > > see the archives -
> > > >
> > > > Solution: Use WINS
> > > > ip helpers are for DHCP only. read up on the standards doc.
> > > >
> > > > Regards,
> > > > Vijay.
> > > >
> > > >
> > > > "Ken Yeo" <kenyeo@on-linecorp.com> wrote:
> > > > > Question:
> > > > >
> > > > > 4 subnets seperated by Cisco routers. Running Netware 5.1
> > > > servers in all
> > > > > location. No NT servers. All windows 95 workstations in all
> > > > branches are
> > > > setup
> > > > > with the same workgroup name, WORKGROUP. All workstations
> > > > use the same WINS
> > > > > server. Netbios name resolution to IP is fine.
> > > > >
> > > > > How need to be done so that if I open network neighborhood,
> > > > I can see all
> > > > > Windows 95 workstations in all locations?
> > > > >
> > > > > Here is my understanding:
> > > > >
> > > > > Browser election will occur in each subnet and one of the Windows
95
> > > > > workstations will become master browser for the WORKGROUP
> > > > on the local
> > > > > subnet.
> > > > >
> > > > > Since browser elections are broadcast, the are blocked by
> > > > router and thus
> > > > each
> > > > > master browser does not know about other master browsers in
> > > > all other
> > > > subnets.
> > > > > So we can only see local workstations in network neighborhood.
> > > > >
> > > > > So I tried these:
> > > > >
> > > > > Enable ip helpder-address 172.16.1.255 (LAN masks are
> > > > 24-bit)in all LAN
> > > > > interfaces and point to each other. I hope that ip
> > > > helper-address will
> > > > forward
> > > > > netbios broadcast to all subnets and trick the workstations
> > > > there is only
> > > > one
> > > > > network. So only one master browser instead of four master
> > > > browsers were
> > > > > elected. But it does not work and workstations from another
> > > > subnets will
> > > > not
> > > > > showing in network neighborhood.
> > > > >
> > > > > I have not tried browstat.exe yet..
> > > > >
> > > > > What do you think? Please advice,
> > > > > Ken
> > > > > **Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:56 GMT-3