Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!usc!ucsd!rutgers!galaxy.rutgers.edu!andromeda.rutgers.edu!berger From: berger@andromeda.rutgers.edu.rutgers.edu (Theresa Berger) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: 3C501, packet drivers, and bootp Summary: Can I get all three to work? Message-ID: Date: 19 Feb 90 21:37:22 GMT Sender: news@galaxy.rutgers.edu Reply-To: berger@andromeda.rutgers.edu.UUCP (Theresa Berger) Organization: Rutgers University, Newark, NJ Lines: 15 I've got two Novell networks (ANetware '286 v.2.15C) using 3Com 3C501 cards in the workstations. These networks also talk to the rest of the world via NCSA Telnet. I'm using what I believe is the current Clarkson packet driver for the 3C501 (dated 11/15/89). Bootp does not work with the packet driver, as far as we can tell the request never hits the wire. If I boot the PC standalone without the packet driver, bootp works fine, so the bootp servers are doing their job. In labs that are configured the same except for NI5210 cards in the workstations, I can get the packet driver & bootp working together off the Novell server, so the problem is the 3C501. We absolutely can't afford to replace the 3C501 cards in the two labs. Is there any solution, such as an update to the 3C501 packet driver that will let it send bootps, or should I just give up and find a better workaround? BTW, why doesn't it work? Theresa Berger