Charles,<br><br>If the box has a CMOS battery to hold RTC/configuration info, you might try removing the battery/clearing the CMOS. I have seen this help with motherboards that wouldn't act right.<br>GC <br><br><div class="gmail_quote">
On Fri, Jan 21, 2011 at 12:15 PM, Charles Shapiro <span dir="ltr"><<a href="mailto:hooterpincher@gmail.com">hooterpincher@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Ouch dang it. Seems like this one is a brick.<br>
<br>
I let it sit for 30 minutes and watched the LINK/ACT light go from<br>
flickering to steady ( I presume lookin' for a dhcp server and<br>
failing, then falling back to the default static address of<br>
192.168.11.150). Then I plugged its ethernet port up to my IBM<br>
Thinkpad 600x running Ubuntu 9.10 and set my ethernet device to an<br>
address of "192.168.11.17". I then ran "route -n" and verified that<br>
the default route was "192.168.11.0". ping(1) never got any packets<br>
back, and telnet(1) reports that the port is closed. When I try to<br>
ping(1) a random address (e.g. "192.168.11.88") I get the proper<br>
"Destination host unreachable" error.<br>
<br>
So I ran nmap(1) against it ("nmap -n 192.168.11.150"). nmap(1)<br>
reports the correct MAC address (as printed on the bottom of the<br>
machine), but says that every single port of the 1,000 it tried is<br>
filtered. According to nmap(1)'s documentation, this means that the<br>
packet it sent to that port was dropped. Pressing the <reset> button<br>
on the back of the box had no effect on this behavior. Restarting<br>
with the reset pin held down gives me a series of tones (presumably<br>
complaining about the reset pin) but also no change in behavior.<br>
<br>
Short of breakin' out the soldering iron and trying to contact the<br>
UART on the board, I am a little out of ideas here.<br>
<br>
-- CHS<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
On Thu, Jan 20, 2011 at 1:21 PM, Raylynn Knight <<a href="mailto:seca900rider@gmail.com">seca900rider@gmail.com</a>> wrote:<br>
> I had no problem pinning the Kurobix once it finished it's startup. It takes several minutes from bootup before it responds.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 20, 2011, at 10:12 AM, Charles Shapiro <<a href="mailto:hooterpincher@gmail.com">hooterpincher@gmail.com</a>> wrote:<br>
><br>
>> Hmm. I tried ping(1) but didn't get anything. Maybe that just means<br>
>> it won' respond to ping(1) though. Thanks for the tip!<br>
>><br>
>> -- CHS<br>
>><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br>