Strange router/hub problem

OK, I'm currently stuck on this one, so here goes....

Basically, I am using a Netgear FR114P to try and share broadband round our
office (we have just moved, had no problem using the router in old
premises).

The problem I have is as follows: When the router is connected to our switch
(DLink 24 port unmanaged jobby, same type as in old office, only difference
is now we have 2 of them connected) and also connected to the ADSL 'modem'
supplied to us by our ISP (EasyNet) the connection to the router just dies
(ie. I can continuously ping the router, and after a few minutes, it will
slow down considerably, then just die altogether)

If I remove the ethernet connection between the router and the ADSL modem
then all is fine, and it will work perfectly for days on end.

If I plug the router into my PC only (no hub) then there is no problem, and
I can access the net through it without a hitch.

Oh, and the router is assigning address to the PC's on our network via DHCP,
although once it has died, it don't do a very good job of it lol. Once
again, there was no problem doing this at our old premises.

Does anyone have a clue what can be causing this damn annoying fault?

Cheers folks

Russ

"Rusty®" <rusty@NO_SPAMukmax.com> wrote in message
news:3feda2bc$0$399$(E-Mail Removed)...
> OK, I'm currently stuck on this one, so here goes....
>
> Basically, I am using a Netgear FR114P to try and share broadband round
our
> office (we have just moved, had no problem using the router in old
> premises).

How old is this Netgear router? I had an old Dlink router that used to do
this too, but it was one of the earliest routers Dlink made, and it locked
up good and tight if you put too much data through it. I have a new Dlink
wireless router that has been rock solid. The old router seemed to have a
processor that simply wasn't powerful enough compared to the modern one.
It's possible that the addition of the additional Dlink 24-port Ethernet
switch is overloading the traffic into the router.

How exactly are you connecting the computers vis-a-vis the etherswitches and
the router? Are the two etherswitches connected to two separate LAN ports on
the router? Have you tried cascading the secondary etherswitch to the
primary etherswitch, and only connect the primary etherswitch to the router?
It's possible that the amount of traffic flowing between the nodes across
the two etherswitches is overloading the router in between.

Yousuf Khan

"Yousuf Khan" <(E-Mail Removed) > wrote in
message
news:s5kJb.226579$(E-Mail Removed). cable.rogers.com...
> "Rusty®" <rusty@NO_SPAMukmax.com> wrote in message
> news:3feda2bc$0$399$(E-Mail Removed)...
> > OK, I'm currently stuck on this one, so here goes....
> >
> > Basically, I am using a Netgear FR114P to try and share broadband round
> our
> > office (we have just moved, had no problem using the router in old
> > premises).
>
> How old is this Netgear router? I had an old Dlink router that used to do
> this too, but it was one of the earliest routers Dlink made, and it locked
> up good and tight if you put too much data through it. I have a new Dlink
> wireless router that has been rock solid. The old router seemed to have a
> processor that simply wasn't powerful enough compared to the modern one.
> It's possible that the addition of the additional Dlink 24-port Ethernet
> switch is overloading the traffic into the router.
>
> How exactly are you connecting the computers vis-a-vis the etherswitches
and
> the router? Are the two etherswitches connected to two separate LAN ports
on
> the router? Have you tried cascading the secondary etherswitch to the
> primary etherswitch, and only connect the primary etherswitch to the
router?
> It's possible that the amount of traffic flowing between the nodes across
> the two etherswitches is overloading the router in between.
>
> Yousuf Khan
>

Right, should have posted this earlier, but I forgot lol.... the problem is
all solved... it was in fact down to some machines on the network having a
virus, which was caning the bandwith to the router, causing it to shut
down.... strange but true.

Cheers,

Russ