legg@sirius.ucs.adelaide.edu.au (Christian Legg) (07/11/90)
Hello everyone. I'm having a problem that I'm hoping someone may have
come across and tackled before.
I'm using the NI5210 packet driver, v6.2.1 to access Netware. That
works fine.
Telnet has been configured to use this packet driver to communicate
with the world. That works fine, provided I hardwire the IP number into
the config.tel. This I would rather not do, but...
Attempting to use RARPing with the packet driver fails with a
'Warning, packet driver vector invalid, using default search'
message, with TELNET halting sometime after that with a RARP failed
message.
Telnet will correctly RARP when I use the hardware directly rather than
through the packet drivers, but of course Telnet then munges Netware.
So, it's not a problem with our nameserver.
Frustrating, eh? It should work (so I've been told). Is there a more
recent version of the NI5210 driver available? Alternatively, is anyone
out there using the NI5210 packet driver and successfully RARPing? Could
it be that the version of Telnet (2.3b5) doesn't handle RARPing to a
packet driver?
Thanks in advance for any help that may come my way.
christian legg
Christian Legg **********************************
University Computing Services, * This message has been brought *
University of Adelaide, South Australia. * to you today by the letters *
Phone : (08) 228 5549 * B, M and by the number 9 *
Email : legg@ucs.adelaide.edu.au **********************************peiffer@umn-cs.cs.umn.edu (Tim Peiffer (The Net Guy)) (07/13/90)
In article <5621 comp.dcom.lans> legg@sirius.ucs.adelaide.edu.au writes:
Attempting to use RARPing with the packet driver fails with a
'Warning, packet driver vector invalid, using default search'
message, with TELNET halting sometime after that with a RARP failed
message.
Try using interrupt 0 in the config.tel file. I had the same problem
earlier when configuring packet drivers for SLIP. Buried deeply in the
docs there is a note as to why you have to do this, and I do not remember
why. This seems to force it to find the packet driver in the correct
vector path.
Tim Peiffer
--
-----------
Tim Peiffer peiffer@cs.umn.edu or
Computer Science Dept ..!rutgers!umn-cs!peiffer
University of Minnesota