forum.excito.org

After a power outage, which the B3 was on battery, and I shut it off gracefully. I restarted the B3 and I am unable to reach it. After several reboots of the B3 it still won't connect. I tried using both IP, B3, name and in a web browser. So I figured I'd be smart and connect laptop to the LAN port directly using a crossover cable. I then did an arp -av to find the ip address of the physical address. no luck. Here are my ipconfig and arp results. I also used angry ipscanner and it only found the one interface on my computer for 169.254.*.*...yes I searched the whole 255.255 range. How can I find the physical addresses. Once I know those I can set my arp table.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
Windows IP Configuration
Host Name . . . . . . . . . . . . : XXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-1E-68-73-22-CF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::74b0:b4ce:aac0:118a%10(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.17.138(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 167779944
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-B6-AF-8E-00-1E-68-27-AD-79

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

arp -av

Interface: 127.0.0.1 --- 0x1
Internet Address Physical Address Type
224.0.0.22 static
239.255.255.250 static

Interface: 169.254.17.138 --- 0xa
Internet Address Physical Address Type
169.254.255.255 ff-ff-ff-ff-ff-ff static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

Interface: 0.0.0.0 --- 0xffffffff
Internet Address Physical Address Type
224.0.0.22 01-00-5e-00-00-16 static

Can you reach it from WAN?

Using easyfind?

Puma

169.254 means your windows computer did not receive a dhcp address. It will not find the b3 on that subnet.

If you know how your B3 was configured (what Ip-range) you could try setting you computer to a fixed IP-adress in that range. (I guess the standard adress is 192.168.1.10, so you should try 192.168.1.x for your computer).

Yours,

Martijn

to UBI: I intentionally did not hook up the windows to anything except to the B3 server with crossover, that way I could maybe arp it and maybe get the hardware address and reset it that way.

To Binkem: I know it was set with DHCP, thinking I might hard IP it from now on.

To Puma: didn't try WAN easyfind, what is that?

After too many runs up and down the stairs I finally brought it upstairs and hooked it to small switch on the network. Guess what it worked. I guess I should have figured out that the port on the router died. Should have tested that first. Looks like I'm gonna need a new router too.