Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Another Problem with WinQVT/Net
Message-ID: <9103192222.AA00129@asylum.sf.ca.us>
Date: 20 Mar 91 06:22:01 GMT
References: <NELSON.91Mar19201442@sun.clarkson.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 24


   Date: 20 Mar 91 04:14:42 GMT
   From: Russ Nelson <decwrl!ucbvax.berkeley.edu!agate!bionet!uwm.edu!cs.utexas.edu!usc!rpi!clarkson!grape.ecs.clarkson.edu!nelson>
   Organization: Clarkson University, Potsdam NY

      >As I post this I've seen at least a half dozen "invalid port"
      >messages.  I have also noted this message (exactly one occurrence)
      >under NCSA telnet v2.3b14.  What's the relationship?

      I have the same problem when I use the clarkson ni6510-driver.
      If I instead use the ipx.com packet-driver wich was included
      with the Racal-Interlan Ni6510 Pc/tcp packet then I doesn't
      get any errors in the console-window in Winqvt/net.

   Interesting.  I also get these messages with the 3c503 driver.  Perhaps
   there's something wrong with *all* the packet drivers?  Or perhaps the
   message has nothing to do with the packet drivers at all?

It sounds more like winqvt's not coping with broadcast packets, like
rwho or routing packets. You'd be a lot less likely to see these over
an IPX link, but very likely over any ethernet with a UNIX system on
it. Do they appear periodically?
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	voice/fax: 415 594-1141