NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Web firmware upgrade for GS108Ev3 failing
I wante to upgrade to version 2.00.05 but don't have a Windows machine handy. So I thought I'd use the web interface. After entering "loader mode" on the switch, I uploaded the firmware, only to ...
And an update: Managed to borrow a Windows machine. The ProSafe utility (latest version) did not even find the switch. Nice!
Then I tried the firmware upgrade from chrome on the windows machine, and voila, that actually worked! What on earth could be the issue?
So to summarize: firmware upgrade from chrome or firefox on linux failed, Prosafe utility failed to detect switch, Chrome on Windows saved the day.
I'm leaving more confused than I was when entering.
if i use the arp command in cmd, it doesn't answer anything,
if i use the netsh command, i get "the object just exists"
sorry Eaglehawk, what should I put inside "Local Area Connection"?
I'm not an expert :(
I don't understand also because i can't access the browser interface from any pc/browser but i can with my phone :(
with the phone i can see the interface but it is stuck in loader mode and i can't exit that mode :(
i'm going to hate netgear for that, prosafe amazing software suggested my to upgrade the firmwire and it stopped at 50% - now i have to trash this new switch :(
In Control Panel, go to "Network and Sharing Center", then click the "Change adapter settings" on the left.
Identify the adapter that you should be using (sorry, I can't help you here) use the name (The top line) and use that in the "Local Area Connection".
Alternate:
In a command prompt, run: ipconfig /all and use the appropriate name for your active adapter.
Example:
Ethernet adapter <the name to use>
or
Wireless LAN adapter <the name to use>
This issue got me today, so it's still happening. Basically it appears that the Netgear firmware file upload only works on certain browser/OS combinations; however once in 'firmware upload mode' there's no way out without uploading firmware (a factory reset *does not* restore the device to default operation).
It can get particularly complicated to sort out if the switch gets an address via DHCP on a different network to the default (e.g. 192.168.1.x), since a reboot in firmware loader mode appears to result in it defaulting back to 192.168.0.239 and *not using DHCP* - giving the appearance of the firmware update having 'bricked' the device.
As others have noted, the fix is to use a Windows box with Chrome, and configuring networking as necessary to access the switch using 192.168.0.239.
First, thanks to those who were troubleshooting this before as it helped resolve my issue
Note: For systems with multiple interfaces or if you have renamed the interface
* Run this from a command prompt with administrator access
netsh interface ipv4 show addresses
* Find the interface with the appropriate network range for your switch (copy the portion after "Configuration for interface")
* Run this command with the name of the interface
netsh interface ipv4 add neighbors "<insert network interface name here>" "<insert switch mac address here>"
Example: netsh interface ipv4 add neighbors "LAN1" "192.168.2.40" "a0-63-91-bb-bb-bb"
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
