HDTenEightyP/NetNews huggingface dataset:
From: pcg@aber.ac.uk (Piercarlo Grandi)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc.misc,comp.dcom.lans.ethernet,comp.os.msdos.programmer
Subject: BOOTP, pkt drivers, and ethernet board type
Date: 12 Jan 93 18:44:50 GMT
Reply-To: pcg@aber.ac.uk (Piercarlo Grandi)
Organization: Prifysgol Cymru, Aberystwyth


Suppose you had hundred of PCs running MSDOS attached to a various
number of Ethernets, by way of a dozen different types of cards (ISOLAN,
WD, 3COM, ...).

Managing all these one by one would be terrible; it would be much nicer
if you had a RARP/BOOTP/TFTP server with a centralized list of all
machines (IP addresses,FQDNs, and so on).

It would be wonderful if the root partition (C:) on all these PCs were
*absolutely identical* on all those PCs, so that it could be installed
and made read only without hassle.

The problem is those dozen or so types of cards. In order to start the
whole process the right driver (and its configuration) must be
individuated (once this is done, everything becomes easy; we get the
ethernet card address, we use that as key for a broadcast, and some
RARP/BOOTP server notices it and then tells us everything we need to
know).

I have thought about three possible solutions:

	1) Have some program that probes around and determines
	   the type of network card installed in the machine.

This looks rather a formidable task, so probably it is more sensible
to consider:

	2) Use 4-6 spare bits in the CMOS configuration bytes to
	   record the network card type, just as there are two
	   fields for the drive type.

	3) Use some spare byte in the hard disk VTOC (all those
	   machines have an hard disk) to record the network card
	   type, just as there are fields to record partition types;
	   this could be done creating a fake partition, whose numeric
	   type were the card type, just using normal fdisk.

In other words I'd rather like two new DOS commands, 'nifset <number>'
to record somewhere safe the type of the card in a machine, and
'niftype' that returns the same <number> in the 'errorlevel'.

I'd like to know if anybody has already thought along the same lines,
and has already done something like this, and I welcome anybody's
comments and suggestions on how to do this; in particular about:

	1) probing to determine the card type is feasible and how.

	2) which bits in the CMOS may be assumed to be usable.

	3) which bytes in the VTOC may be assumed to be usable.

	4) if any utilities like nifset and niftype already exists.

	5) once the nif type if obtained, how to configure LAN manager
	   (for packet drivers it's easy) for that device, *without
	   altering any file*.

Thanks in advance!
--
Piercarlo Grandi, Dept of CS, PC/UW@Aberystwyth <pcg@aber.ac.uk>
  E l'italiano cantava, cantava. E le sue disperate invocazioni giunsero
  alle orecchie del suo divino protettore, il dio della barzelletta
From: bo09+@ANDREW.CMU.EDU (Brock Eugene Organ)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Wanted: IBM PC TIFF MS FORTRAN code
Date: 6 Jan 93 22:17:18 GMT
Distribution: world
Organization: The Internet

I am currently involved in a project to implement
scanned bitmaps in a real time data collection program.
The program is written in MS FORTRAN on the IBM PC.

Does anyone know where I can find a TIFF reader,
or a good explanation on how to write one? (I have the
format,  but don't understand how it works.)

Thanks,

Brock
*****************************************************************************
Brock Organ -- bo09@andrew.cmu.edu, organ@ibalm.psy.cmu.edu
Department of Psychology,  Carnegie Mellon University

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: pwilson@world.std.com (Pete Wilson)
Subject: Need 3c509 Driver for KA9Q
Organization: The World Public Access UNIX, Brookline, MA
Date: Mon, 11 Jan 1993 02:30:31 GMT

I just installed KA9Q (920621) on a Toshiba 5200. This
machine comes with something called a 3Com 3c509 for 
which there is no driver in pub/msdos/pktdrvr at
oak.oakland.edu. 

Anybody know where I can find a driver for the 3c509?
--
Thanks, Pete Wilson (pwilson@world.std.com)


Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jntjkg@decwks.GSFC.NASA.Gov (Joel K Gallun)
Subject: SLIP compatibilty
Organization: Goddard Space Flight Center, Greenbelt, Md, USA
Distribution: comp
Date: Tue, 12 Jan 1993 15:31:50 GMT

Hi all,

I hope to use SLIP to communicate between a PC and a 3COM Netbuilder II.
Is this possible?  Has anyone done this before?  I am currently using
the etherslip packet driver to connect two PCs running WATTCP applications
and it works great, but I am concerned about the etherslip driver
talking to the SLIP software in the 3COM.

Thanks in advance,

--
Joel Gallun                        Internet: jntjkg@decwks.gsfc.nasa.gov
NASA Goddard Space Flight Center      Voice: (301) 805-4545
#include <std_disclaimer>             Snail: Code 735, GSFC, Greenbelt MD 20771
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mitton@dave.lkg.dec.com (Dave Mitton)
Subject: Re: NDIS/Netbios
Reply-To: mitton@dave.lkg.dec.com (Dave Mitton)
Organization: Digital Equipment Corporation, Littleton MA
Date: Wed, 13 Jan 1993 00:03:16 GMT


RE: NETBIOS vs NETBEUI
	Session API vs Transport Protocol

	Actually, IBM invented all this stuff and they are often the source of
the confusion between NETBIOS the API and the NETBIOS Frames Protocol
(aka NETBEUI).

	NETBIOS the API came on the scene with the first IBM PC Network
Program.  The hardware was a Sytek designed broadband card that used an
Ethernet data link chip and outboarded the transport protocol to the card's
processor.  

	When IBM finally launched their Token Ring hardware and the PC LAN
Program (note the subtle insertion of "LAN") this transport protocol got a
dose of 802.2 LLC type 2 connection oriented data link.  The original token
ring support software came with two primary files:
	TOKREUI.SYS and NETBEUI.EXE
where TOKREUI was the Token Ring card driver, and NETBEUI was the transport
TSR.  
	In the next version, IBM changed the packaging and created the
currently known LAN Support Program, and changed the software files to
the current DXMxxx.SYS scheme.

	If you read the IBM LAN Tech Reference (SC30-3383), the Transport 
protocol is described there as the "NETBIOS Frames Protocol".   Only the
industry has dubbed it "NETBEUI" after the original file name.

	NETBIOS the API has been alse defined on OS/2, and implemented
on many transports stacks: TCP/IP (RFC1001/1002), DECnet (in PATHWORKS),
NBP (from 3Com), SPX/IPX (Novell), OSI (TOP NETBIOS)...

	Dave Mitton
	"Former" DECnet-DOS Technical Lead Versions 1-3.
	Digital Equipment Corp.
	Networks Engineering
	Token Ring Program
From: boris@NETMAN-GATE.NETMANAGE.COM
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: RE: Wanted: NFS client
Date: 6 Jan 93 16:41:55 GMT
Distribution: world
Organization: The Internet


>
>	What NFS clients exist for the PC? Are there any free/shareware
>clients? So far, I've heard of PC/TCP by FTP Software and PC-NFS by Sun
>Microsystems.
>	Thanks.

To my knowledge there are no PD NFS clients available.  If you want to use
NFS on your PC you have to purchase it.  Other then the companies you 
mentioned the list of providers includes: B&W, Wollongong, NetManage.

***************************************
Boris Yanovsky
20823 Stevens Creek Blvd., Suite 100
Cupertino, CA 95014
phone: (408)973-7171
fax:   (408)257-6405
boris@netmanage.com
***************************************
From: backman@FTP.COM (Larry Backman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Problems with PC/TCP idrive and file locking
Date: 7 Jan 93 19:59:30 GMT
Distribution: world
Organization: The Internet


 >> 
 >> Hello net!
 >> I have a M88k based computer with UNIX sys V. rel 3. When
 >> I mount directories from this computer, with PC/TCP idrive,
 >> idrive reports that lockd doesn't support the proper
 >> protocol version, and file/record locking does not work.
 >> 
 >> I have contacted the computer vendor about this problem, 
 >> and they tell me to use SUN PC-NFS to get around this
 >> problem.
 >> 
 >> Is there a way to get around this problem without throwing
 >> away PC/TCP and Interdrive ?

 Sure; turn locking off...

 Your server does not support LockD Version 3 which has the extensions
 necessary to do PC based record level locking.  Your going to have the
 same problem and workaroudn with all the PC based NFS clients.

 At the same time I would suggest pushing hard on your SVR3 vendor to
 upgrade their lockd to the late 80's much less the 90's :-)


 Larry Backman
 FTP Software

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: per@teknologi.agderforskning.no (Per Sigmond)
Subject: Packet-driver for Xircom needed
Organization: Agderforskning
Date: Fri, 8 Jan 1993 13:41:14 GMT

Where can I find a FTP Packet-Driver for the Xircom pocket ethernet adapter
(parallell-port) ?

Per.
-- 
Per Sigmond
Agderforskning Teknologi
Televeien 1
4890 Grimstad
Norway

Internet: Per.Sigmond@teknologi.agderforskning.no
Xref: sparky comp.protocols.tcp-ip.ibmpc:7285 comp.protocols.tcp-ip:5850
From: black@ll.mit.edu (Jerry Glomph Black)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
Subject: Packet Driver or PCROUTE on PC-synch card NEEDED!
Date: 8 Jan 93 00:26:33 GMT
Organization: MIT Lincoln Laboratory
Originator: black@ll.mit.edu (Jerry Glomph Black)

I need to upgrade my Slip service to operate on a 56kB leased DDS line,
for which my CSU/DSU operates synchronously.  

Is there a PCROute driver, or a packet driver, which can talk to a PC
card which does synchronous serial?  

email to black@LL.MIT.EDU   Thanks!
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: beame@maccs.mcmaster.ca (Carl Beame)
Subject: Re: Awful NFS performance!
Organization: McMaster University, Hamilton, Ontario.
Date: Wed, 6 Jan 1993 03:52:22 GMT

In article <memo.842598@cix.compulink.co.uk> shaman@cix.compulink.co.uk writes:
>In-Reply-To: <C0C5vI.Hn@cmie.ernet.in> ajayshah@cmie.ernet.in
>
>
>>I just finished using Nortons `sysinfo' to measure the performance
>>of B&W 3.0 NFS and I get 80k/s on read and 10k/s on write.
>
>>This is on a 386@25.
>
>What was your server: This is about right for SCO Unix, but poor for 
>(say) a SUN.
>
>>Ouch!  What can one do about it?
>
>Not much. Prestoserve on a SUN. ask again in comps.protocols.nfs
>
	The write performance can be improved by setting the /W parameter
on BWNFS.COM to /W:8192 . The Read performance can be improved by increasing
the /R: parameter, BUT if you increase it past the maximum number of packets
the Ethernet card can receive in a row, the NFS will hang.

>>NFS has a serious problem being a credible approach for networking
>>PCs if this is all one gets by way of speed.  What does one get with
>>Novell Netware?
>
>In excess of 500Kbytes/Sec. If speed is all you want, forget NFS. 
>Netware caches its disk, and can give very near saturation of the 
>Ethernet with a good server - lets face it thats ALL the server CPU 
>and RAM does: Serve files :-) (NLM's excluded)

	Remember sysinfo uses variable read and write sizes, other performance
monitors use large read and write buffers which will cause the performance
to increase greatly. 

	One test we tried at Fall Interop was to run the Novell performance
monitor from a Compaq/486 (wd8013) to a Vax running TGV's Multinet Server 
running their NFS server and their Netware Server (both use the same underlying 
file server code). The Netware did about 430 KB/sec while BWNFS did about 
600 KB/sec.  When we reduced the buffer size, Netware did not degrade much 
while the NFS slowed down.

Carl Beame
Beame & Whiteside Software Ltd.
beame@bws.com
From: PALCHETTI%IROEC.DECNET@ICNUCEVX.CNUCE.CNR.IT
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Subscribe me.
Date: 11 Jan 93 08:09:21 GMT
Organization: The Internet


	Please subscribe me at your mailing list on the TCP/IP argument.
My address is "PALCHETTI@IROEC.CINECA.IT"
Regards
				Enrico Palchetti
				IROE-CNR via Panciatichi 64
				50127 Florence
					ITALY.

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: tkevans@eplrx7.es.duPont.com (Tim Evans)
Subject: Problems with Dell 466DE, 3c503, and PC/TCP
Reply-To: tkevans@eplrx7.es.dupont.com
Organization: DuPont Engineering Physics Laboratory
X-Newsreader: NN version 6.4.19
Date: Tue, 5 Jan 1993 20:25:57 GMT

I have a user who just replaced his Compaq 386/20 with a Dell
466DE (66MHZ DX-2, 16MB RAM, 320MB IDE drive) and who finds that
his PC/TCP will not work properly on the new machine.  We moved
his 3c503/16 to the new system, without changing any jumper settings
(base i/o 310, shared memory disabled) and have removed all other
add-in devices from the Dell system.

We're using the NDIS drivers, with NDIS-to-packet driver
(dis_pkt) shim and netbind.  protocol.ini specifies
interrupt vector 60H; we've tried others with no luck,
as well as having tried all the hardware IRQ possibilities.
The 3com board passes all diagnostics.

PC/TCP loads without complaint and you can ping the PC
from elsewhere on the network, as well as use PC/TCP's
ping to access other systems.  The problem comes with
ftp.  In ASCII mode, file transfers seem to work ok, but
in binary mode, anything other than a small file (10Kbytes
or so) results in a lockup of the PC.  This happens both in
DOS and in Microsoft Windows.

Prior to getting the new system, the user had no problems
whatsoever with PC/TCP on the Compaq.

If anyone is using this particular combination of hardware/
software and has everything working properly, could you
please e-mail me your autoexec.bat, config.sys, protocol.ini,
pctcp.ini, etc?  And, if anyone has any ideas, or knows anything
about the Dell-3c503 combination with PC/TCP, please let me
hear from you.  Thanks.
-- 
Tim Evans                     |    E.I. du Pont de Nemours & Co.
tkevans@eplrx7.es.dupont.com  |    Experimental Station
(302) 695-9353/7395           |    P.O. Box 80357
EVANSTK AT A1 AT ESVAX        |    Wilmington, Delaware 19880-0357
From: doyle@freya.cs.umass.edu (Jim Doyle)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Whats the scoop with Windows 3.1/WinQVTNet/SLIP
Date: 11 Jan 93 22:45:17 GMT
Organization: University of Massachusetts, Amherst


	
	What is the scoop w/ supporting SLIP8250 under Windows 3.1
using WinQVT - my attempts cause an error message reporting invladi
packet class.

	
       I am using:

WinQVT v3.03
SLIP8250 v0.6

..... Jim Doyle
From: d0mail@d0xs2.fnal.gov (D0 General User)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Need Advice/Help For Installing PC/TCP (for DOS)
Date: 6 Jan 93 21:49:52 GMT
Reply-To: d0mail@d0xs2.fnal.gov (D0 General User)
Organization: D0 Experiment
NNTP-Posting-Host: d0xs2.fnal.gov


In article <BzFJwK.32K@ecf.toronto.edu>, hujic@ecf.toronto.edu (HUJIC DAMIR) writes:
|> Newsgroups: comp.protocols.tcp-ip.ibmpc
|> Path: fnnews.fnal.gov!mp.cs.niu.edu!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!usc!cs.utexas.edu!torn!skule.ecf!hujic
|> From: hujic@ecf.toronto.edu (HUJIC DAMIR)
|> Subject: Need Advice/Help For Installing PC/TCP (for DOS)
|> Message-ID: <BzFJwK.32K@ecf.toronto.edu>
|> Organization: University of Toronto, Engineering Computing Facility
|> Date: Thu, 17 Dec 92 18:55:31 CST
|> Lines: 24
|> 
|> 
|> Hi,
|> 
|> I am currently volounteering at an organization in which I was asked
|> to try to connect a PC to an internet service, so that the
|> organization could have ftp access (and possibly telnet access).
|> 
|> We have PC/TCP version 2.05 and manuals, however I am having some
|> difficulty getting it to work properly.  If anyone with experience
|> with PC/TCP can help me out, I'd appreciate it.  I've outlined below
|> what I need to do.
|> 
|> Thanks,
|> Damir
|> --------------------------------------------------------------------
|> What needs to be done:
|> 
|> - our PC is supposed to be set up with ip address xxx.xxx.xxx.y
|> - we are supposed to connected via modem (using Slip I guess) to
|>   a host at the other end with ip address xxx.xxx.xxx.z, I need
|>   to set up this host with this address.
|> - access to internet should only be on demand, i.e. I need to 
|>   set up a simple way for the modem to dial and ftp (possibly
|>   telnet) access would be available.
|> 


I would also like help on this since we will be trying to implement pretty
much the same scheme. Its not necessary to do now but its something 
we'll be wanting to do in the near future. So if someone else already does
it then it will be much easier for us to follow.


Thanks for the help
			John
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: pjh@mccc.edu (P. J. Holsberg)
Subject: SLIPDIAL Bombs Out??
Organization: The College on the Other Side of U. S. 1
Date: Mon, 4 Jan 1993 19:54:18 GMT

I'm in the process of installing SLIPDIAL/SLIP8250/?? and have run into
a problem right off the bat. I edited the DEFAULT.SLP script to match my
modem, port and phone, and everything proceeds nicely through the
dialing. But as soon as the line starts to ring, something puts the line
back on hook.

Here's the log file:
Line   1: Parameters:  Com 2, Baud 9600, Par 0 Data 8, Stop 1, Str 0 Dtr 1
Line   2: Parameters:  Com 2, Baud 19200, Par 0 Data 8, Stop 1, Str 0 Dtr 1
Line   3: Sending  : <
Line   3: Expecting: 
Line   3: Received :  3: Sending  : <
Line   4: Waiting  : 1
Line   5: Sending  : <
Line   5: Expecting: 
Line   5: Received :  5: Sending  : <
Line   6: Waiting  : 1
Line   7: Sending  : AT&F9<
Line   7: Expecting: AT&F9
Line   7: Received : AT&F9 1
Line   8: Waiting  : 2
Line   9: Expecting: OK
Line   9: Received : OK 1
Line  10: Sending  : ATS0=1 S7=120 S48=0 S50=7 S51=254 S58=2 S59=15 S61=0 s63=1 s92=1<
Line  10: Expecting: ATS0=1 S7=120 S48=0 S50=7 S51=254 S58=2 S59=15 S61=0 s63=1 s92=1
Line  10: Received : ATS0=1 1
Line  11: Waiting  : 1
Line  12: Expecting: OK
Line  12: Received : OK 1
Line  13: Sending  : AT tq2x12 &c1 &d3 &s1 &w<
Line  13: Expecting: AT tq2x12 &c1 &d3 &s1 &w
Line  13: Received : AT 1
Line  14: Waiting  : 3
Line  15: Expecting: OK
Line  15: Received : OK 1
Line  17: Phone # 9210930
Line  18: Sending  : ATDT9210930
Line  18: Expecting: ATDT9210930
Line  18: Received : ATDT9210930 1
Line  19: Waiting  : 15
Line  20: Expecting: CONNECT
Line  20: Received : ERROR
Line  20: Match Error: Bad response.
====Program Prematurely Terminated====

Hope someone has some suggestions. I'd appreciate email on this as I
will be away for a week. I'll summarize responses if anyone's interested.

Thanks and happy New Year.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jverde@bugs.inescn.pt (Isidro Vila Verde)
Subject: Re: PD exp16 + NetWare Lite ?
Keywords: exp16, LSL, ipxodi 
Organization: Inescn-Redes
Date: Mon, 4 Jan 93 18:13:00 GMT

In article <jverde.1.0@bugs.inescn.pt> jverde@bugs.inescn.pt (Isidro Vila Verde) writes:
>From: jverde@bugs.inescn.pt (Isidro Vila Verde)
>Subject: PD exp16 + NetWare Lite ?
>Keywords: exp16, LSL, ipxodi 
>Date: Mon, 4 Jan 93 17:08:19 GMT
I am trying share CUTCP or WATTCP and NetWare Lite.
First I am trying this sequence:
      LSL
      exp16 0x61
      ipxpkt
      server
      client
      net login supervisor
on two Pc's, but the net login not see the other Pc.
Second I am trying use odipkt:
	LSL
	exp 0x61
	odipkt 0 97
and pc get me the message: 'A driver is already installed at this vector'
and if change the interrupt number to 96 get the message: 'Cannot get MLID 
control'

Thanks,
Isidro
jverde@porthos.inescn.pt
From: davew@viper.gvg.tek.com (David White)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: UTP && THINWIRE same card
Date: 7 Jan 93 17:39:01 GMT
Reply-To: davew@viper.gvg.tek.com (David White)
Organization: Grass Valley Group, Grass Valley, CA

In article <1265@alsys1.aecom.yu.edu>, reiner@medusa.bioc.aecom.yu.edu
(Peter D. Reiner) writes:
|>Does anyone know of a TCP/IP card having both unshielded twisted
|>pair and thinwire connectors? This is in anticipation of a future
|>addition of UTP to our net.  The card must also have a packet
|>driver interface.
|>Thanks
|>Peter Reiner
|>reiner@aecom.yu.edu

Cabletron offers a card, the E2112, that has both 10BASE-T (RJ-45) and
10BASE-2 (BNC) interfaces.  All the cards I have bought from them
have had a packet driver and have been very high performance cards.
According to the information I have, the E2112 is has 16kb and the
E2112-x has 64kb.  Not sure where you are located, so you may want
to try their corporate headquarters (603) 332-9400) to get the
number of the office that would serve your location.       

-----
Dave White	Grass Valley Group, Inc.  VOICE: +1 916.478.3052
P.O. Box 1114  	Grass Valley, CA  95945   FAX: +1 916.478.3887
Internet: 	David.C.White@tek.com	  UUCP:  uunet!gvgpsa.gvg.tek.com!davew
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: wcs@anchor.ho.att.com (Bill Stewart +1-908-949-0705)
Subject: Re: How to slow down Ethernet cards ?
Organization: Brought to you by the numbers 2, 3, and 7
Date: Tue, 12 Jan 1993 18:03:24 GMT

In article <1992Dec29.175813.13563@cli.di.unipi.it> luigi@iet.unipi.it writes:
   to slow down an Ethernet controller in order to work at a slower speed,
   say something between 500 Kbit/s and 2Mbit/s. At least the 82586 I know
.....
   [If you're curious why I'm asking this: it would make a cheap
   communication interface using medaia which cannot carry the full
   ethernet b/w. And it would be less time consuming for the PC than

The old AT&T StarLAN 1 network ran CSMA/CD at 1 Mb/s, using twisted pair.
Worked fine, and you got distances up to something like 1000m.
It was slow, but it had some real advantages, like supporting
daisy-chaining without hubs for small configurations.
We all moved up to 10 Mb/s when it became affordable.

That was in the old "We're the Phone Company.  We're not compatible -
we don't have to be" days, so it ran a variant on Datakit URP protocols
instead of TCP/IP over top of it, (TCP was ported soon enough.)
Had a nice direct interface into the Datakit wide-area-networks.
This and the 3BNet (different framing over thick Ethernet) 
products encouraged the USG folks to avoid supporting TCP/IP until
they'd missed their ability to make TCP/IP a standard part of the
System V Release N environment, contributing to the non-winningness of
that world for business.  Nice stuff, though.


--
#				Pray for peace;      Bill
# Bill Stewart 1-908-949-0705 wcs@anchor.att.com AT&T Bell Labs 4M312 Holmdel NJ
Bush's pardon of his co-conspirators shows that he is, in the end, still a wimp.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: fury9600@mcshh.Hanse.DE (Kai Heinecke (Neuhaus))
Subject: Need a ftp to X.400 connection
Reply-To: chip@drnhh.neuhaus.de
Organization: Point of Presence & MCS Hamburg
Date: Mon, 11 Jan 1993 15:32:45 GMT
Keywords: X.400, tcp-ip, ftp

Hello netters,

I've got a project where I need to connect a Unisys host to the outside
world. On the host there is tcp-ip, and I was thinking of using ftp to
a front end PC which then has software for further communication. One of
the main goals is to be able to access X.400 mailboxes, but I also will
need to connect with external systems (PCs and others).

Do any of you know of products which would offer me this ftp to X.400
gatewaying on a PC? Is this a reasonable way to be going anyway? The 
reason for not getting X.400 right on the host is price. It's quite
expensive.

I would be using a public X.25 network between X.400 installations.

Thanks in advance for any help.

Chip
Newsgroups: comp.protocols.tcp-ip.ibmpc