Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewse!tyc From: tyc@cbnewse.att.com (felix.a.lugo) Newsgroups: comp.sys.next Subject: Experiences with networking on the NeXT Message-ID: <1991May4.051554.27839@cbnewse.att.com> Date: 4 May 91 05:15:54 GMT Organization: AT&T Bell Laboratories Lines: 41 I've been having some trouble getting my NeXT to live in a non-NeXT network. I've followed the manuals to the letter and my machine cannot communicate with anything other than another NeXT on the same subnet. At my location we have a campus network composed of several sub- networks each combining different platforms (Suns, AT&T, Amdahl, IBM). My NeXT is configured as a non-Netinfo (local) system. Other systems ping my machine and they see it without problems, but if I try to ping them, I only get packets every once in a while (98% packet loss according to ping). The following is the output generated from "ifconfig en0": en0: flags=23 inet 135.1.156.2 netmask ffffff00 broadcast 135.1.255.255 My subnet router is set to IP 135.1.156.254 (which is correct). All the network hardware has been verified to be functional by my site's support staff and I've successfully used other systems on the same network. Another NeXT on the same network (IP 135.1.156.3) suffers from the same problem (although both NeXTs can easily communicate with each other). They just can't see anything that's not a NeXT. Has anyone encountered such a problem? Have I setup everything properly? HELP! If NeXT is reading this, I could certainly use their support! =============================================================================== Felix A. Lugo E-Mail: (NeXTmail preferred) AT&T Bell Laboratories, Naperville, IL Felix_A_Lugo@ATT.COM coco@ihcoco.att.com AT&T NeXT User Group nug@ihcoco.att.com T.Y.C. Software, Lisle, IL coco@ihtyc.att.com ===============================================================================