Re: error after installing switch...

From: Stefaan A Eeckels (tengo_at_DELETEMEecc.lu)
Date: 12/18/04

  • Next message: Dave Hinz: "Re: error after installing switch..." 
    Date: Sat, 18 Dec 2004 00:18:34 +0100

    On Fri, 17 Dec 2004 22:54:31 GMT
    "Joe" <joe@epix.net> wrote:

    > Just thought I could get some UNIX help here?

    The point is that what you report is not typical
    (apart from the network hardware, the machine isn't
    aware of the change from a hub to a switch, and I've
    never seen the error message you've seen as a result
    of such a change), plus obviously not related to the
    change. As far as I can tell from the info you gave,
    you've got a problem with a serial line, not your
    network.

    Now if you me to do a better stab at diagnosing what
    ails your Unix box, please provide the following
    information:

    1. Details on your Unix box: brand, OS, age etc.
       Are you accessing it from a terminal?
    2. Details on the error: does it happen when you
       rebooted the machine, have you rebooted th
       machine at all, what exactly do you mean with
       "can't access" (from the network, from the
       console, does it boot and then freeze, etc.)
    3. Details on your network: do you have any special
       network devices such as ethernet serial ports,
       older devices that might have problems when
       connected to a 10/100Mb/s switch instead of (what
       I surmise to be) a 10Mb/s hub. How recent is
       your cabling, have you tried other cables, etc.
    4. Anything else _you_ can think of that might be
       relevant to your problem. Remember I don't know
       your network at all.

    Just remember that the message you've shown can most
    definitely not be caused by replacing a hub by a
    switch, unless there's some hardware connected to
    your Unix box that provides serial ports over
    Ethernet.

    And just one thing it could be - if the switch
    can do 100Mb/s, and your Unix box can do 100Mb/s,
    and your cable is not cat5, your "can't access"
    might be caused by a failure to communicate, and
    the tty error might be something you've been having
    since a long time, it just wasn't noticed.

    Take care, 

    -- 
Stefaan
-- 
As complexity rises, precise statements lose meaning,
and meaningful statements lose precision. -- Lotfi Zadeh
  • Next message: Dave Hinz: "Re: error after installing switch..."

    Relevant Pages

    • 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)
    • Re: LAN ip subnet is moving off from a bigger enterprise
      ... The host company runs Cisco ... Connect your switch to this ... At the CBO the network is 10.23.1.x and the gateway ... WS1 WS3 SBS HP4000 ...
      (microsoft.public.windows.server.sbs)
    • Re: Ethernet network wiring ?s
      ... >> the planned network is designed correctly and for my own education on ... >> find I that I have a hub in my office that I used at some point in the ... > A switch is an active device. ... > the ports that have the ethernet address the message is intended ...
      (comp.sys.mac.hardware.misc)