From: nagamati@caldera.usc.edu (Romklau Nagamati)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Does PC/TCP 2.11 work with DESQview/X?
Date: 12 Dec 1992 21:28:59 -0800
Organization: USC - Netlab
Distribution: usa
NNTP-Posting-Host: caldera.usc.edu

In article <9935@fs3.cam.nist.gov> crosson@cam.nist.gov (Robert Crosson) writes:
>[.................]
>to add the TCP/IP networking facility by installing PC/TCP
>version 2.11.  In setup, I've installed the DV/X drivers, but
>I get an error message that it was "inable to access FTP's
>TCP/IP services."  It says to check for improper
>ifcust.sys/ipcust.sys installation, invalid local host address,
>invalid local host name, or a mismatch of the local host name
>and the name server information about this machine.

The error message is pretty much self-explanation. The first thing 
you should check is whether you have properly configured the IPCUST.SYS 
and IFCUST.SYS. Simply loading them in CONFIG.SYS doesn't mean anything
if you haven't configured. The PC/TCP 2.1x installation, that I ran,
left them un-configured. Use the following two lines to check them
out. If it's necessary to configure them, consult the "green giant"
for details.

	ifconfig IFCUST.SYS show
	ipconfig IPCUST.SYS show

If you haven't check your CONFIG.SYS, there should be two lines that
look pretty much like the following. If there ain't any, add them.

	device=c:\pctcp\ifcust.sys
	device=c:\pctcp\ipcust.sys

The second thing would be to check your host file. Check the one that
DV/X is using, i.e. the one listed in /DVX/NETWORK/INETD.CFG. If it's
not the same one listed by "ipconfig IPCUST.SYS show", then ask yourself
why they are not. Obviously your own machine should be in your own host
table, for example;

	128.125.051.007  yourhostname  localhost

The first part is your machine's IP address. It should be the same one
listed in IPCUST.SYS. The second part is your machine's name. Again, it
should match IPCUST.SYS. Don't use the IP address I showed in the example.
It's not available for you to use. Ask you network administrator for one.

The third thing to check is your pctcp.ini. If you know about 
"use-old-init-scheme" in the section [pctcp general], then you may
set it to "yes" if you have a good reason why you want to. I've never
set mine. Use FTP's editor to edit it if you have to. Here's how.

	confedit

Since you're going to edit your pctcp.ini anyhow, you might as well
check for some other things in there. Setting "use-emm" in the
[PCTCP kernel] to "yes" help reduce the foot print in conventional
memory or high RAM.

>[....................]
>problem that there are no files 'ifcust.sys' and 'ipcust.sys'
>anywhere on my system because PC/TCP went to a new configuration

They're on PC/TCP disk #1.

>[....................]
>Bob Crosson
>crosson@cam.nist.gov

By now, you should already have made you DV/X and PC/TCP 2.1x work
together in harmony. But, you should also do some fine-tuning with
something like "socket" and "buffer". Adjust the latter if and
only if you know what you're dealing with because if thing stops
working right, you did not hear about it from me!

Finally, start your DESQview/X and check for normal operation, like
qconnect, telnet, ftp, rsh, and rexec. Quarterdeck has a great technical
note on "Troubleshooting IPX remote computing (technote #253)". Though,
it's not for TCP/IP, but it gives you a general idea of what could go wrong
and what you should look for. They, probably, would come up with one
for FTP...

Have fun.
Ron/Kor

-- 
-----------------------------------------------------------------------
   Romklau Nagamati   | 
   nagamati@usc.edu   |
-----------------------------------------------------------------------
Newsgroups: comp.os.msdos.desqview