Re: Ethernet issue: works one way but not another

From: Greg Barniskis (nalists_at_scls.lib.wi.us)
Date: 03/18/05

  • Next message: cpghost_at_cordula.ws: "Re: ssh security"
    Date: Fri, 18 Mar 2005 07:15:50 -0600
    To: Abu Khaled <khaled.abu@gmail.com>
    
    

    Abu Khaled wrote:
    ...
    > Am I the only one interested in this topic? Where is the rest of our
    > lovely community?
    > Come on guys let's scratch those gray cells and help John out.
    >

    Although progress is being made on getting detail, it's still
    insufficient (and, not entirely consistent? if the connection in
    question is *wired* then probably the fact that a wireless access
    point exists on the same subnet is not likely relevant). Anyway, I
    do not have a clear vision of what connects to what, how.

    The relevant portions of rc.conf, ifconfig output (and ipconfig
    output from the M$ box), the syntax of the tcpdump, the specs of the
    box, and other relevant details might spur more response. A simple
    ASCII representation of the network might help.

    FWIW, I've seen tcpdump behave poorly if the box or card just
    doesn't have the horsepower required to parse the volume of all the
    packets being seen on the network.

    re: can't ping M$ box... M$ firewall sounds like the most likely
    culprit. If you try to ping and get no response, does the M$ box
    nevertheless show up in FreeBSD's arp table (compare arp -an before
    and after the ping test)? If the MAC address shows up, you've got
    connectivity just fine, but something's dropping the ICMP packets.

    PS to Abu -- your written English is as good or better than many
    native speakers of the language, so don't apologize for it. =)

    -- 
    Greg Barniskis, Computer Systems Integrator
    South Central Library System (SCLS)
    Library Interchange Network (LINK)
    <gregb at scls.lib.wi.us>, (608) 266-6348
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: cpghost_at_cordula.ws: "Re: ssh security"

    Relevant Pages

    • Re: Mshome is not accessible
      ... Windows Network, and select the workgroup I get: ... Mshome is not accessible. ... All computers are running Windows XP SP2 and are members of the MSHOME ... Computer A can ping using ping hom100fr001. ...
      (microsoft.public.windowsxp.network_web)
    • network slowness/freez-up since update 10/11
      ... network problems: first the network is slow (even within a few ... network - but not the rest of the system - just locks up (can't ping ... OHCI version 1.0, legacy support ... <Parallel port bus> on ppc0 ...
      (freebsd-current)
    • network slowness/freez-up since update 10/11
      ... network problems: first the network is slow (even within a few ... network - but not the rest of the system - just locks up (can't ping ... OHCI version 1.0, legacy support ... <Parallel port bus> on ppc0 ...
      (freebsd-current)
    • Re: Networking problem
      ... I finally got it to the point that from the desktop i can ping the ip ... of the laptop and get a response. ... It seems some network configuration is not ok on the laptop. ... each machine hooked to ethernet ports of wireless router. ...
      (microsoft.public.windowsxp.general)
    • network slowness/freez-up since update 10/11
      ... network problems: first the network is slow (even within a few ... network - but not the rest of the system - just locks up (can't ping ... OHCI version 1.0, legacy support ... <Parallel port bus> on ppc0 ...
      (freebsd-current)