[Macola]

One of my clients made the mistake of trying a firmware upgrade on his SMC 7004AWBR from an XP machine and had to reboot halfway through. I ended up getting him a new router, but I'm now trying to salvage the SMC for my own use, if I can. I cannot get into the admin page (either on the standard IP or the factory default), and have tried resetting (both the rest button and COM port methods), cycling power, etc. The router still works in the sense that it's locked into the last configuration, which is to use a dynamic address on the WAN side and act as a DHCP server on the LAN. However, it does not work in other situations (for example, with a static IP).

Any other ideas would be welcome.

[ghporter]

It strikes me that if the LAN side still works, then there must be some firmware running, and the router must have its own IP in the LAN's subnet range. Also, the hardware reset (with pins 3 & 8 on the com port shorted as you turn on the router) should give you a stable situation and let you try to upload the firmware via an FTP option. Since you haven't had any luck, try posting your situation on Broadband Reports SMC Forum They may have some help for you.

There's a technique for restoring a Linksys router with a failed firmware upgrade that may work for you. Disconnect everything from the router except one LAN side computer. Manually configure your computer for an IP of 192.168.123.1 (the SMC's default address is 192.168.123.254), subnet 255.255.255.0, 10Mbps, half duplex. At this point you should be able to ping the router (1t 192.168.123.254), verifying that the router is actually working. Now run the firmware updater (Linksys used to provide a link to a Mac TFTP program, but it's not there anymore-I don't know what SMC provdes...) Hopefully, something like this will help you out.

[John Strung]

I had the same problem. SMC tech support had me unplug the router for 5 minutes, then press the reset button on the back for 5 seconds. Still no go. Then the tech suggested I try logging into http://192.168.2.1:88 instead of http://192.168.2.1/ and bingo it worked.

[Macola]

Originally posted by John Strung:
I had the same problem. SMC tech support had me unplug the router for 5 minutes, then press the reset button on the back for 5 seconds. Still no go. Then the tech suggested I try logging into http://192.168.2.1:88 instead of http://192.168.2.1/ and bingo it worked.

Thanks--forcing the port did the trick! Now I have another functional router in my collection

[ghporter]

I have had a related problem accessing my US Robotics router. It needed the port to be forced as well. Since US Robotics and SMC (and Asante', and some others) use the same OEM manufacturer for a lot of their products, I guess it makes sense that they should behave similarly.

By the way, did you reflash the router with the new firmware, use the old firmware, or just find out that the customer made the box mess up for a while?

[Macola]

Originally posted by GHPorter:
By the way, did you reflash the router with the new firmware, use the old firmware, or just find out that the customer made the box mess up for a while?

After I logged in, I checked the firmware version and it showed the latest revision, so I didn't mess with it any further. All other functions of the router seem to be fine...I haven't got WEP configured yet to work with an Airport card and a Skyline USB adapter, but that's another story. My client is happy with his new router, and I've warned him not to try any more firmware upgrades.

[ghporter]

How strong a warning did you give your client? As my telco repair guy said to me while repairing my buried line after the builder next door cut it, "The first fix is on the house; after that, I get $65 an hour and we bill that day." That sort of "warning" would sure get MY attention, and it did get the builder's attention.

[Macola]

Originally posted by GHPorter:
How strong a warning did you give your client?

I "neglected" to give him the admin password for the new router