Re: Help requested with RIPv1 lan issues (UK school)

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: andy (andy_at_login2.net)
Date: 12/11/04


Date: Sat, 11 Dec 2004 10:59:05 -0000


"Bill Grant" <not.available@online> wrote in message
news:#asx0Gy3EHA.1292@TK2MSFTNGP10.phx.gbl...
> RIP Listener is an option in XP that allows the client machine to
listen
> for RIP messages from routers. It is installed from the Windows Add
Software
> | Networking window. It is not usually installed by default.
>
> As a first step, check one machine each which does/doesn't do this and
> check that RIP Listener is present/absent. At least then you will know
what
> is causing the problem.
>
> I don't really know whether this can be controlled by group policy or
> something similar. I would certainly want it turned off. I like the
routers
> to do the routing, not the clients!
>

I think we have clients with the RIP option installed that are not creating
storms of RIP v1 requests. Really what I am after an answer to is whether
this is normal behaviour for the XP RIP Listener. Probably the fact that all
our RIP enabled clients don't do this is significant but I could be wrong.

Should RIP requests v1 from a single listener have the effect of slowing
pings from 1-4pms up to 170ms on a fully switched network? Should a single
client saturate the LAN for 3 to 4 seconds at a time with this traffic?

What are the circumstances when a XP listener would feel the need to
Broadcast (I presume it is a broadcast) this traffic to the world?

Regards,

Andy.

> "andy" <andy@login2.net> wrote in message
> news:ehZlphx3EHA.3120@TK2MSFTNGP12.phx.gbl...
> > Hi,
> > I am looking for some guidance and comments on a issue we are seeing on
> > our
> > school network.
> >
> > Scenario: 9 servers, 3 DC's all Server 2003 standard or Enterprise. One
> > ISA
> > 2000 server, Exchange 2003 server, SMS 2003, MOM 2005. Full SP. 650 XP
Pro
> > clients some SP2 others SP1.
> >
> > Clients are grouped together in sets of 15 or 30 depending on room size,
> > each room is connected via a 100MB (cat 5e) switched network to a
gigabit
> > backbone (all fibre). We have two sites linked by Gigabit fibre. Our
core
> > switches are 3Com with DLink switches in the classrooms.
> >
> > We use addresses in the range 192.168.x.y on our network where x =
> > classroom
> > number and y=pc within the classroom, we have a persistent route
> > configured
> > on each client that points to the 192.168.2.0 subnet which is where our
> > servers live.
> >
> > Our servers have static routing entries to all our subnets.
> >
> >
> > We have suffered several network issues over the last three months:-
> >
> > AD replication issues, high packet loss, loss of mapped user drives.
> >
> > So we replaced our Allied Telesyn switches with new 3Com, replaced our
> > site
> > to site fibre and have had new links pulled in from the cabs to our
server
> > rooms.
> >
> > We rebuilt AD and the servers are replicating perfectly, however we
still
> > have odd students who fail to have their drive mapped at login or who
> > loose
> > access to their drive whilst logged in. There appears to be no pattern
as
> > this occurs at random. Logging out and logging back in always restores
the
> > users access to mapped drives. The event log on the clients indicate
that
> > the share is offline.
> >
> > So, I have been monitoring our LAN using Ethereal and I am seeing bursts
> > of
> > RIP v1 request traffic from our clients that cause our normal client to
> > server pings to rise from <4ms to around 170ms with the occasional
> > 'request
> > timed out' occurring. Watching the wire it seems that each RIP request
> > lasts
> > around 3 or 4 seconds. Sometimes in the space of 1/2 hr we may see 4 or
5
> > clients making similar broadcasts, sometimes we see several clients
making
> > the same broadcast at the same time. We have no idea why some clients
send
> > the RIP request traffic and others don't.
> >
> > Could this be the cause of students loosing their mapped drives by
hogging
> > the network? Do we need to setup RRAS on a server to deal with these
> > requests? or should we just disable RIP on the clients?
> >
> > Is there a easy way to disable RIP where it installed using group policy
> > or
> > similar without visiting each XP client?
> >
> > I did Google for answers and tried Usenet too. Any help is gratefully
> > received.
> >
> > Andy.
> >
> >
> >
> >
>
>



Relevant Pages

  • Re: Help requested with RIPv1 lan issues (UK school)
    ... > for RIP messages from routers. ... > check that RIP Listener is present/absent. ... I think we have clients with the RIP option installed that are not creating ... >> AD replication issues, high packet loss, loss of mapped user drives. ...
    (microsoft.public.windows.server.networking)
  • Re: Help requested with RIPv1 lan issues (UK school)
    ... RIP Listener is an option in XP that allows the client machine to listen ... to do the routing, not the clients! ... > Our servers have static routing entries to all our subnets. ... > AD replication issues, high packet loss, loss of mapped user drives. ...
    (microsoft.public.windows.server.networking)
  • Re: Help requested with RIPv1 lan issues (UK school)
    ... RIP Listener is an option in XP that allows the client machine to listen ... to do the routing, not the clients! ... > Our servers have static routing entries to all our subnets. ... > AD replication issues, high packet loss, loss of mapped user drives. ...
    (microsoft.public.windowsxp.network_web)
  • How to prevent RIP service from starting?
    ... I am looking for help in stopping the RIP service starting on our LAN ... clients as the RIP broadcasts are taking our pings from 1ms to 170ms. ... I have looked at GP on our 2003 server and browsed through computer ...
    (microsoft.public.windows.group_policy)
  • Window add/remove components wizard
    ... RIP Listener does not update the route table with new route ... ... 2.Route Table on a Windows XP-Based Computer That Is Configured As a ... ... Routing Information Protocol Listener, ...
    (microsoft.public.windowsxp.help_and_support)