dixon@gumby.paradyne.com (Tom Dixon) (06/14/89)
I am running NCSA Telnet ver2.2d, the one that comes from clarkson.edu and communicates with a packet driver for a WD8003e. Everything works fine except RARP. I have determined that my RARP server is returning good packets but the Telnet quits trying and complains about no response. If I specify the IP number in the config file, it works and I can connect to any machine just fine. (So ARP works, just not RARP). I have no Bootp server so thats out (if you have info on bootp, I'll read it....). Anyone see anything like this with this software/hardware before care to offer suggestions as to possible problems to check for and possible fixes? Tom Dixon uunet!pdn!dixon
bkc@sun.soe.clarkson.edu (Brad Clements) (06/21/89)
From article <6186@pdn.paradyne.com>, by dixon@gumby.paradyne.com (Tom Dixon): > I am running NCSA Telnet ver2.2d, the one that comes from clarkson.edu > and communicates with a packet driver for a WD8003e. Everything works > fine except RARP. I have determined that my RARP server is returning > good packets but the Telnet quits trying and complains about no response. > If I specify the IP number in the config file, it works and I can connect > to any machine just fine. (So ARP works, just not RARP). > > I have no Bootp server so thats out (if you have info on bootp, I'll read > it....). > Well, I made a mistake. The packet driver has to explicitly request each ethernet type field that is to be used by the client. NCSA always requests IP, and ARP. But RARP slipped my mind. You can get a bootp server from lancaster.andrew.cmu.edu or write to ww0n+@andrew.cmu.edu "Its fixed in the next release" Of course, the built in WD8003 driver correctly handles rarp, but then you can't use it w/ Novell etc. Brad Clements Network Engineer Clarkson University