Buffalo Forums

I have a TS-RVHLD9C that is about 3 years old now and once in a while, not often it would just lose connectivity and I'd have to reboot it to get it back. Well just recently I upgraded its firmware to 1.24 and now it's losing connectivity weekly. The front display will be showing the default Ethernet 2 IP of 169.253.115.62 and that's all. When I reboot then my fixed IP on Ethernet 1 will work again. I've replaced the cat5 cable and tried different switch ports and nothing else in my rack is having any connectivity problems.

Thanks for any ideas.

Andy

Same on LAN 2? First of all start by resetting the device.

I had not been using LAN 2, nothing plugged into it. Basically LAN 1 goes dead/unresponsive and so it displays on the front panel that Ethernet 2's IP is 169.x.x.x. which of course means you couldn't connect to it. I plugged into LAN 2 now so both ports are wired and I'll try to do a reset tonight. When you say reset you're talking about 'Restore' right?

It may be a problem with the firmware you recently update, there is a similar problem on the LS400 serie with the last firmware, the only way to solve it was to roll back to a previous firmware.

Quote from: Azasel on May 11, 2016, 12:28:37 AM
It may be a problem with the firmware you recently update, there is a similar problem on the LS400 serie with the last firmware, the only way to solve it was to roll back to a previous firmware.

2 completely different units with 2 completely different hardware and firmwares. The 2 are not in the slightest bit related.

Sorry for the slow reply but I got tied up with other issues. The problem is not fixed with the TS-RVHLD9C, I did a reset on the unit and nothing is better I'm afraid. After the reset I switched things around and used Ethernet 2 for my fixed IP on the unit and let Ethernet 1 grab an IP by DHCP. That lasted 2 days before the unit lost connectivity again and after I had to power cycle it to get connected again, when I went into the network settings Ethernet 1 was still on DHCP and Ethernet 2 was still set to static but the IP and subnet mask fields were empty. When it lost connectivity I tried to connect via browser to the DHCP address but it wouldn't, just times out.