Re: Network problem

From: Leonard Isham (leonard.isham_at_gmail.com)
Date: 02/23/05

  • Next message: Mike Carifio: "binfmt_misc" 
    Date: Wed, 23 Feb 2005 07:46:25 -0500
To: For users of Fedora Core releases <fedora-list@redhat.com>

    On Wed, 23 Feb 2005 07:58:45 +0000, Paul Howarth <paul@city-fan.org> wrote:
    > On Wed, 2005-02-23 at 02:11 +0100, Mats Erlandson wrote:
    > > What is so strange, is that the computer can talk to all local addresses
    > > except the switch (192.168.0.1) and two other computers on the local
    > > network can talk to it, all obviously through the switch both ways.
    > > This shows that the cabling is OK, and that the problem is probably in
    > > the routing on the computer (not allowing it to connect directly to the
    > > switch) or in the switch, not accepting communication from the
    > > computer. The switch routes properly for the other computers on the
    > > network and can be managed from either one (tested) but not from the
    > > problem child. If I change the configuration on the computer to use
    > > DHCP (and rebooting) the computer does not get (receive/accept) the DHCP
    > > configuration and is thus 'dead', i.e. no communication to nor from any
    > > computer. Therefore, until the communication to/from the switch is OK I
    > > am using a static address. To eliminate hardware faults possible in the
    > > ethernet port on the motherboard (eth0) I installed a network card,
    > > tested to perform OK in another computer, and disabled the motherboard
    > > port using the BIOS. With only an expansion ethernet card active in the
    > > computer I made the same tests with the same results. This seems to
    > > eliminate network card problem in the computer. My current setup is, as
    > > per the first paragraph above, motherboard ethernet port only with
    > > static address. Still no joy. I am at a loss.
    >
    > Desperate times call for desperate measures. Have you tried a different
    > cable and a different switch port?
    >

    I would also move it to a working where you have a working computer.

    Power down the working computer.

    Connect the computer with the problem.

    Power up the computer and test.

    You could also do it the otherway around and move a working computer
    (laptop maybe?) to the connection you are having problems with.

    Can also try setting the switch port and ether net to full 100 and
    avoid any autosensing problems. 

    -- 
Leonard Isham, CISSP 
Ostendo non ostento.
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Mike Carifio: "binfmt_misc"

    Relevant Pages

    • Re: Network monitoring tools
      ... > Can anyone recommend a good, free network monitoring tool? ... > dramatically, and I believe its related to the network, as all the home ... It depends on the switch. ... You can then monitor the traffic on every switch port. ...
      (RedHat)
    • Re: Cannot ping outside of localhost
      ... >> switch at 100mbit I believe, ... > It will be worth your time to talk with your network administrators. ... Hopefully they also set the switch port to auto/auto, ... Other machines in the same subnet seem to work fine. ...
      (comp.unix.solaris)
    • RE: IP address conflicts
      ... If you get a network vendor like Network Hardware Resale ... >> It's amazing how money will appear out of thin air if certain oxen get ... the switch you are suggesting I cannibalise uses the EtherToken ... When dealing with a bureaucracy I have found the most effective method is ...
      (freebsd-questions)
    • Re: ConnectComputer Problem
      ... I'm a little confused by your network configuration. ... Switch2 --- SBS Server ... switch has internet access all the time, the second switch has the client ... NICs ...
      (microsoft.public.windows.server.sbs)
    • Re: Help with long term network problem
      ... Using a CNET network switch connected to a CNet Wireless G router Model ... Having the chart listing all of the computers is a great start. ... /all" shows only an Intel 2200BG WiFi connection - no Ethernet is apparent. ...
      (microsoft.public.windowsxp.network_web)