Network FUBAR

I'm trying to move my server to another system without reinstalling. The old
system is a cheap whitebox running generic components. The new system is an
IBM eserver 325. I did a deep copy of the entire old system harddrive and
put it in the new server, booted from a rescue CD, installed grub on the MBR,
then rebooted the new system. Everything seems to be working fine except for
networking, which is deeply and perplexingly hosed.

The current symptoms are that I have no connectivity. I can bring up the
interface and it shows connected. I can ping the IP assigned to the
interface from the computer. The input and output counters increment when I
show the interface. But I can't ping another computer on the same subnet
plugged into the same switch. I get "destination host unreachable" back from
the IP assigned to the interface.

The relevant subnet is in the server's routing table, as is a default route.
I've even tried adding static routers pointing directly to the IP of the
other machines.

The computer is plugged into a 16 port switch module installed in a Cisco
router. Looking at the interface from the router, it shows connected and the
counters on the interface increment as well. The IP address for the server
appears in the router's ARP table with a hardware address of "incomplete" and
blank under the associated interface. I have multiple devices plugged into
the switch, and I've swapped the cables and the switchports around. The
other devices have no connectivity issues, and this server has no
connectivity, regardless of where it's connected. That seems to pretty much
eliminate an external layer 1 issue or something silly like being in the
wrong VLAN. (For thoroughness, let me add that there are no access lists or
other configs on the router that could even conceivably interfere with the
server's connectivity.)

The server has two onboard Broadcom NetXtreme NICs, which both behave
identically. They may very well share common hardware, so I installed a
Netgear RTL81695 based NIC. Completely different hardware, using a
completely different driver. It behaves identically to the onboard NICs.
That seems to rule out a hardware issue, but I'm at a loss as to what
software issue could cause these symptoms either.

Anyone have any ideas before I wipe the hard drive and start from scratch?




--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Bridging and using the interfaces concurrently
    ... server also connected to the internet, ... provide only client-level connectivity to the "second" box (when it ... If you really want bridging, then the easiest thing will be to create ... you should bridge your "first"'s external interface with the second VLAN ...
    (freebsd-net)
  • shows the duplicate in ifconfig
    ... My server getting Ip via dhcp but I want to give my ... for static Ip in my interface. ... connectivity and in log it gives that bge0is already ...
    (comp.unix.solaris)
  • Re: What doesnt lend itself to OO?
    ... The whole idea that a subsystem is just ... > The first line exists in the server. ... objects between client and server i.e. as far as the client code is ... > external interface is the traditional input interface whose ...
    (comp.object)
  • Re: Brian Kernighan, maybe Im not worthy, maybe Im scum
    ... If you think I'm giving a verbose pseud write access to my server, ... interface appears in C Sharp as consisting of sbyte arrays. ... failed to see that a for loop is not just a while loop because a while ... chilling effect on freedom of speech. ...
    (comp.programming)
  • Re: Cannot get NAT to route in RRAS
    ... The basic problem is that you are using an ADSL modem on the server. ... I would suggest that you set up a demand-dial interface to act as the ... Static Route wizard, create a default route using this interface (ie put ...
    (microsoft.public.win2000.ras_routing)