Are you connected to port A1 with the correct IP settings on your computer ?
If so, you many need to use the recovery procedure, documented in the the knowledge base as article KB62388
Thanks for your reply. Yes I connected to port A1 and the IP for the computer was 192.168.0.2.
I did try the recovery procedure and it didn't work for me. After I put in the free IP address, it stayed at "listening for recovery request" stage.
Is it possible the reset process somehow can't reset the IP to default 192.168.0.1?
Message was edited by: jasonliu on 30/07/10 7:06:43 CDT AM
The next level down of diagnostics require a null modem serial cable, and when connected to a serial program, it will show the situation of the UTm.
connect the null model cable using 8n1 and power on the UTM while keeping reset down.
Thanks Ross. I actually tried this way but didn't get anything using Hyper Terminal. Is the com port enabled by default?
it is enabled by default IF powering on with the erase button pressed, for the boot loader only.
Hi Ross, I did get into the bootloader this time. I probably didn't do it right when I tried last time. It asked me for network, flash, or serial. I tried all 3 ways and didn't get anywhere. Is there a manual on how to use the bootloader? Thanks.
no manual. what happens when you select 'flash'?
1. I tried network and it just says getting DHCP then keeps printing dots on the screen.
2. I tried flash and the it seems sg580 just reboots and then all the lights flashing
3. I tried serial and it says "send file now", I tried using send file menu in Hyper Terminal and it says didn't get response from the server.
this proves the boot loader is intact, which is good.
if you select no options, it will default to 'network' which is what is used for the recovery boot method.
the fact the 'flash' optin reboots, indicates the flash contents is corrupt ( and possibly, but unlikely, the flash memory is faulty )
have a loock at kb article KB64630 titled "Problems that can Occur when Upgrading with the Windows Netflash Utility" as this can help you trouble shoot why the recovery boot is not working for you. Monitoring the serial port while attempting the recovery procedure may assist in tracking down the issue.