*BSD News Article 53438


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!bga.com!ecpi.com!tushar
From: tushar@ecpi.com (Tushar Patel)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: TCP/IP stops comunicating
Date: 24 Oct 1995 14:47:30 GMT
Organization: Real/Time Communications - Bob Gustwick and Associates
Lines: 38
Message-ID: <46iua2$8iv@giga.bga.com>
NNTP-Posting-Host: ecpi.com
X-Newsreader: TIN [version 1.2 PL2]


Hi,
I have been working for two months to solve the TCP/IP problem
discribed below. I am running FreeBSD 2.0.5.  I would really appresiate 
if you could tell me how you managed FreeBSD's TCP/IP to talk to trumpet 
winsock's TCP/IP.

Using Trumpet winsock I dial the FreeBSD box and establish the slip
connection between Dos and the FreeBSD box. I can see the web pages
on the internet. But, Every now and then the slip connection just drops 
or the data stops comming. Infact after 3 or 4 pages the connection
just drop's.
Have you come accross problem like this?
Do you see any problem with the TCP/IP?
When I turn on the Tracing on the DOS machine, some time the Trumpet
winsock complains like this "Unknown TCP -- reseting". After that point
the TCP/IP connection just drops?
Any suggestion?

>There is something called the Transaction TCP wich tends to confuse 
>broken term server. This could be disabled in the 2.0.5 version.

That's what I read in the news group archive.

There were couple of line I was suppose to add in the sysconfig file to
take care of the problem. I did add the following lines.

sysctl -w net.inet.tcp.rfc1323=0
sysctl -w net.inet.tcp.rfc1644=0
(This will turn of T/TCP (Transaction TCP).


This did not work. Same problem still exsists.
Thank you very much for taking time to read.

Thanks,
Tushar Patel