Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Kermit TCP/IP troubles
From: oursler@kenyon.edu
Date: 30 Sep 92 14:35:43 -0500
Organization: Kenyon College

Hullo,

	I seem to be having some trouble in getting Kermit to
	work in TCP/IP mode.  CUTE, WINQVTNET and other things
	works just fine, so my network is not a problem.
	Of course I *think* everything is correct, but if it were
	it would work wouldn't it?

	So if some kind soul, can tell me where I went wrong
	I'd appreciate it.

	The scenario is as follows:

   The packet driver I am using

	******************************************************************
	C:\QVT>\net\ne2000
	Packet driver for NE2000, version :.4.1
	Packet driver skeleton copyright 1988-92, Crynwr Software.
	This program is free software; see the file COPYING for details.
	NO WARRANTY; see the file COPYING for details.
                                                                                
                                                                                
	usage: NE2000 [-n] [-d] [-w] <packet_int_no> <int_level> <io_addr>
                                                                                
	C:\QVT>
	******************************************************************

   The version of Kermit I am using

	*******************************************************************
	C:\NEWKERMI>kermit
	IBM-PC MS-DOS Kermit: 3.11 7 Sept 1991 patch level 0
	Copyright (C) Trustees of Columbia University 1982, 1991.
                                                                                
	Type ? or HELP for help
                                                                                
	MS-DOS Kermit 3.11 initialization file...
	Smile!
	MS-Kermit>
        ********************************************************************

   The inportant bits from my MSKERMIT.INI file

	********************************************************************
	set tcp/ip domain kenyon.edu
	set tcp/ip address 138.28.1.11
	set tcp/ip gateway 138.28.1.254
	set tcp/ip primary-nameserver 138.28.1.2
	define kcvax3 set port tcp/ip kcvax3, connect
	********************************************************************

   My communications setup from within Kermit

	********************************************************************
	MS-Kermit>show comm
	  Communications port: TCP/IP           Speed: unknown
	  Local echo: off                       Parity: none (8-bit data)
	  Handshake used: none                  Flow control: xon/xoff
	  Duplex: full                          Display: Regular, 7-bit
	  Debug: off
	  Modem is not ready: DSR is off
	  no Carrier Detect:  CD  is off
	  no Clear To Send:   CTS is off
	  tcp/ip address: 138.28.1.11
	  tcp/ip subnetmask: 255.255.255.0
	  tcp/ip domain: kenyon.edu
	  tcp/ip gateway: 138.28.1.254
	  tcp/ip primary-nameserver: 138.28.1.2
	  tcp/ip secondary-nameserver: unknown
	  tcp/ip broadcast: 255.255.255.255
	  tcp/ip host: kcvax3
	  NetBios local name: mskermit.K
	MS-Kermit>
	********************************************************************

   And here's what I get everytime I try to connect to someplace

	********************************************************************
	MS-Kermit>kcvax3
	 Resolving address of host kcvax3 ...
	  trying name kcvax3
	  Cannot reach name server 138.28.1.2
	 Cannot resolve address of host kcvax3
	ERROR releasing Packet Driver for ARP
	ERROR releasing Packet Driver for IP
	ERROR releasing Packet Driver for RARP
	ERROR releasing Packet Driver for ARP
	ERROR releasing Packet Driver for IP
	ERROR releasing Packet Driver for RARP
	ERROR releasing Packet Driver for ARP
	ERROR releasing Packet Driver for IP
	ERROR releasing Packet Driver for RARP
	ERROR releasing Packet Driver for ARP
	ERROR releasing Packet Driver for IP
	ERROR releasing Packet Driver for RARP
	ERROR releasing Packet Driver for ARP
	ERROR releasing Packet Driver for IP
	ERROR releasing Packet Driver for RARP
	?Cannot start the connection.
	MS-Kermit>
	********************************************************************


	I don't know why it's unhappy.  I've stripped my CONFIG.SYS and
	AUTOEXEC.BAT to the bone checking for some conflict.  No luck.
	I was concerned about the default broadcast mask.  It seemed
	to me that it should have been 138.28.1.255, but that didn't
	make any difference.  From the error messages, I would guess
	that something in the packet driver isn't right, but what?

	Any help that anyone could provide would be GREATLY appreciated.

						- Miles -


	-------------------------------
	Miles Oursler
	Manager of Networks and Systems
	Kenyon College
	oursler@kenyon.edu
	-------------------------------