He's exactly right!!! That is how you fix it. Also you can have a WINS
server on both subnets and you need to setup replication between the two.
Although this doesn't always work like you want it to. Sometimes it takes a
long time to update the browse list depending on how big your network is.

"Timothy Metz" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I had the same problem and fixed it with ip helper-address. Your goal here
> is to get netbios broadcasts forwarded to the destination network. I don't
> quite remember if the helper address in this case should be the network
> address or the broadcast address (I'm not at work to check) but someone
will
> correct me if I'm wrong.
>
>
> Network A 192.168.10.X/24
> Network B 192.168.20.X/24
>
> on the interface that is directly connected to network A type
>
> (config-if)#ip helper-address 192.168.20.0
>
> and on the interface that is directly connected to network B type the
> opposite
>
> (config-if)#ip helper-address 192.168.10.0
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > The.rock
> > Sent: Thursday, March 15, 2001 4:52 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Browsing across subnets...
> >
> >
> > Its also a known problem that Win9x clients are not able to browse
across
> > different subnets...I can't remember the article ID, but if I find it
i'll
> > post it.
> >
> > "Rizzo Damian" <[EMAIL PROTECTED]> wrote in message
> > 49C181ACF35ED311A7DC00508B5AF61102E524E3@NAEXCHANGE">news:49C181ACF35ED311A7DC00508B5AF61102E524E3@NAEXCHANGE...
> > > Here's an interesting problem...We have two routers on their own
subnet,
> > > with Windows NT and 9x Clients. We setup WINS servers on each subnet
to
> > > resolve Netbios names. On one subnet we can see everyone in network
> > > neighborhood (both subnets), but on the other subnet, we can only see
> > > machines on that particular subnet. Both routers are identical in
model
> > and
> > > configuration. I used the "ip forward-protocol udp 137 & 138"
> > command, but
> > > that did nothing. Any thoughts?
> > >
> > > _________________________________
> > > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> > >
> >
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>


_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to