> I have a tcp connection problem.
> I connect to the Internet using a Debian 2.2r2.
> Some web servers refuse to respond to my requests.
> No matter witch browser I use (Lynx, Netscape Opera), they access the
> web servers but
> no data is transferred from them.
> The se
> I have a tcp connection problem.
> I connect to the Internet using a Debian 2.2r2.
> Some web servers refuse to respond to my requests.
> No matter witch browser I use (Lynx, Netscape Opera), they access the
> web servers but
> no data is transferred from them.
> The se
I have a tcp connection problem.
I connect to the Internet using a Debian 2.2r2.
Some web servers refuse to respond to my requests.
No matter witch browser I use (Lynx, Netscape Opera), they access the
web servers but
no data is transferred from them.
The servers seems to run on Windoze NT 4.0
I have a tcp connection problem.
I connect to the Internet using a Debian 2.2r2.
Some web servers refuse to respond to my requests.
No matter witch browser I use (Lynx, Netscape Opera), they access the
web servers but
no data is transferred from them.
The servers seems to run on Windoze NT 4.0
- Original Message -
From: Russell Coker <[EMAIL PROTECTED]>
To: Chris Wagner <[EMAIL PROTECTED]>; Debian ISP List
Sent: Friday, June 23, 2000 5:18 AM
Subject: Re: tcp connection
> On Wed, 21 Jun 2000, Chris Wagner wrote:
> >At 02:25 PM 6/20/00 +0200, Russell
- Original Message -
From: Russell Coker <[EMAIL PROTECTED]>
To: Chris Wagner <[EMAIL PROTECTED]>; Debian ISP List
<[EMAIL PROTECTED]>
Sent: Friday, June 23, 2000 5:18 AM
Subject: Re: tcp connection
> On Wed, 21 Jun 2000, Chris Wagner wrote:
> >At 02:25 PM 6
On Wed, 21 Jun 2000, Chris Wagner wrote:
>At 02:25 PM 6/20/00 +0200, Russell Coker wrote:
>>They don't use NVT. The TELNET protocol is not running on (for example) a
>>web server.
>
>Yeah but the NVT settings have to be negotiated for each side to talk to
>each other. If I telnet to an Apache web
On Wed, 21 Jun 2000, Chris Wagner wrote:
>At 02:25 PM 6/20/00 +0200, Russell Coker wrote:
>>They don't use NVT. The TELNET protocol is not running on (for example) a
>>web server.
>
>Yeah but the NVT settings have to be negotiated for each side to talk to
>each other. If I telnet to an Apache we
Are we talking about the 'TCP 3-way handshake'?
--
Kevin Blackham 801-539-0852
[EMAIL PROTECTED]877-964-7746
XMission Internet, Salt Lake City, Utah
On Tue, Jun 20, 2000 at 09:47:25PM -0400, Chris Wagner wr
Are we talking about the 'TCP 3-way handshake'?
--
Kevin Blackham 801-539-0852
[EMAIL PROTECTED]877-964-7746
XMission Internet, Salt Lake City, Utah
On Tue, Jun 20, 2000 at 09:47:25PM -0400, Chris Wagner w
At 02:25 PM 6/20/00 +0200, Russell Coker wrote:
>They don't use NVT. The TELNET protocol is not running on (for example) a
>web server.
Yeah but the NVT settings have to be negotiated for each side to talk to
each other. If I telnet to an Apache webserver on port 80, my telnet is
going to negoti
At 02:25 PM 6/20/00 +0200, Russell Coker wrote:
>They don't use NVT. The TELNET protocol is not running on (for example) a
>web server.
Yeah but the NVT settings have to be negotiated for each side to talk to
each other. If I telnet to an Apache webserver on port 80, my telnet is
going to negot
On Mon, 19 Jun 2000, Chris Wagner wrote:
>At 12:50 AM 6/19/00 +0200, Russell Coker wrote:
>>It is called TCP - Transmission Control Protocol. RFC793.
>
>I'm starting to conclude that it's just called a "tcp connection". But I'm
>still reading through
On Mon, 19 Jun 2000, Chris Wagner wrote:
>At 12:50 AM 6/19/00 +0200, Russell Coker wrote:
>>It is called TCP - Transmission Control Protocol. RFC793.
>
>I'm starting to conclude that it's just called a "tcp connection". But I'm
>still reading through
At 12:50 AM 6/19/00 +0200, Russell Coker wrote:
>It is called TCP - Transmission Control Protocol. RFC793.
I'm starting to conclude that it's just called a "tcp connection". But I'm
still reading through the RFC... It was written in 1983 and for whatever
reason it
At 12:50 AM 6/19/00 +0200, Russell Coker wrote:
>It is called TCP - Transmission Control Protocol. RFC793.
I'm starting to conclude that it's just called a "tcp connection". But I'm
still reading through the RFC... It was written in 1983 and for whatever
reason it
On Sun, 18 Jun 2000, Chris Wagner wrote:
>What I meant by that was what "octets mean and do" in terms of establishing
>and maintaining the connection. Like, what octets are exchanged that tell
>each machine, "yes the connection is established". That protocol has a name.
It is called TCP - Transm
On Sun, 18 Jun 2000, Chris Wagner wrote:
>What I meant by that was what "octets mean and do" in terms of establishing
>and maintaining the connection. Like, what octets are exchanged that tell
>each machine, "yes the connection is established". That protocol has a name.
It is called TCP - Trans
to a friend how you can telnet to any network service and use
that service. Like, you can telnet to a web server on port 80, manually
type the get commands and get the document. I said that this was because
they all use the same connection type. But I don't know what the name of
that conn
ing to a friend how you can telnet to any network service and use
that service. Like, you can telnet to a web server on port 80, manually
type the get commands and get the document. I said that this was because
they all use the same connection type. But I don't know what the name of
that conn
On Sat, 17 Jun 2000, Chris Wagner wrote:
> At 10:48 PM 6/16/00 -0500, Sanjeev Gupta wrote:
> >Sockets? Butyou would definitely have seen this more than a couple of
> >times.
>
> No, not sockets, sockets are way down on the stack. This is the protocol
> that says what the octets mean and do.
On Sat, Jun 17, 2000 at 12:43:45AM -0400, Chris Wagner wrote:
> At 10:48 PM 6/16/00 -0500, Sanjeev Gupta wrote:
> >Sockets? Butyou would definitely have seen this more than a couple of
> >times.
>
> No, not sockets, sockets are way down on the stack. This is the protocol
> that says what the oct
At 10:48 PM 6/16/00 -0500, Sanjeev Gupta wrote:
>Sockets? Butyou would definitely have seen this more than a couple of
>times.
No, not sockets, sockets are way down on the stack. This is the protocol
that says what the octets mean and do. It's the common thread among all the
high level protocol
On Sat, 17 Jun 2000, Chris Wagner wrote:
> At 10:48 PM 6/16/00 -0500, Sanjeev Gupta wrote:
> >Sockets? Butyou would definitely have seen this more than a couple of
> >times.
>
> No, not sockets, sockets are way down on the stack. This is the protocol
> that says what the octets mean and do.
On Fri, 16 Jun 2000, Chris Wagner wrote:
> Hola. What is the official name of the type of connection that the common
> network protocols use? It lives somewhere above the tcp layer and below the
> app layer but is so obscure that I can't find it. e.g. Telnet, ftp, http,
> etc. all establish
Hola. What is the official name of the type of connection that the common
network protocols use? It lives somewhere above the tcp layer and below the
app layer but is so obscure that I can't find it. e.g. Telnet, ftp, http,
etc. all establish an x type connection and then transmit their dat
On Sat, Jun 17, 2000 at 12:43:45AM -0400, Chris Wagner wrote:
> At 10:48 PM 6/16/00 -0500, Sanjeev Gupta wrote:
> >Sockets? Butyou would definitely have seen this more than a couple of
> >times.
>
> No, not sockets, sockets are way down on the stack. This is the protocol
> that says what the oc
At 10:48 PM 6/16/00 -0500, Sanjeev Gupta wrote:
>Sockets? Butyou would definitely have seen this more than a couple of
>times.
No, not sockets, sockets are way down on the stack. This is the protocol
that says what the octets mean and do. It's the common thread among all the
high level protoco
On Fri, 16 Jun 2000, Chris Wagner wrote:
> Hola. What is the official name of the type of connection that the common
> network protocols use? It lives somewhere above the tcp layer and below the
> app layer but is so obscure that I can't find it. e.g. Telnet, ftp, http,
> etc. all establish
Hola. What is the official name of the type of connection that the common
network protocols use? It lives somewhere above the tcp layer and below the
app layer but is so obscure that I can't find it. e.g. Telnet, ftp, http,
etc. all establish an x type connection and then transmit their da
30 matches
Mail list logo
