I own a DLink DI-604 Four port Router. I use it to connect to PC's to a Sprint DSL Modem. Here are specs.
DSL Modem is connected to WAN side of router, It assigns IP, DNS and such to the WAN side of the router. The Modem Also handles the PPPoE connection used to access the internet.
LAN side of router is connected to two WinXP Home SP1 machines. The IPs of the PCs are static.
The problem comes when I try to go through the router. See whenever I try to browse to a highbandwidth site or page, or download a file, or prettymuch any other "heavy load" activity the router stops responding and reboots. Making it impossible to display many websites, download files, or use the internet in any other usefull way.
My question is thus: What could be causing the router to stop responding and reboot?
I suspect it might be a corrupt firmware file I rescently used to update the routers firmware. The .bin file used for this was downloaded to a machine that at the time was connected to the router with a frayed cable. I didnt find the damage until after the problem started.
Im not a network person and if this is something simple please forgive my ignorance.
DSL Modem is connected to WAN side of router, It assigns IP, DNS and such to the WAN side of the router. The Modem Also handles the PPPoE connection used to access the internet.
LAN side of router is connected to two WinXP Home SP1 machines. The IPs of the PCs are static.
The problem comes when I try to go through the router. See whenever I try to browse to a highbandwidth site or page, or download a file, or prettymuch any other "heavy load" activity the router stops responding and reboots. Making it impossible to display many websites, download files, or use the internet in any other usefull way.
My question is thus: What could be causing the router to stop responding and reboot?
I suspect it might be a corrupt firmware file I rescently used to update the routers firmware. The .bin file used for this was downloaded to a machine that at the time was connected to the router with a frayed cable. I didnt find the damage until after the problem started.
Im not a network person and if this is something simple please forgive my ignorance.