Re: RMI binding to SAME port but DIFFERENT IP address on SAME host

From: Randolf Richardson (rr_at_8x.ca)
Date: 08/16/04


Date: Mon, 16 Aug 2004 00:41:53 GMT


"Esmond Pitt <esmond.pitt@notatall.bigpond.com>" wrote in comp.lang.java:

[sNip]
>> I'm not sure if that is what you meant to imply, but there is no
>> "protocol number" field in a TCP/IP header.
>>
>> see http://mindprod.com/jgloss/tcpip.html
>>
>> The host computer simply knows which protocol it is hosting on each
>> port.
>>
>> You can't have two different protocols hosted on the same port, e.g.
>> HTTP and FTP.
[sNip]
> There is a protocol number field in an IP packet header, and I was
> talking about IP at the time. Obviously in the case of TCP the protocol
> number is the TCP protocol number, 6. BTW the statement that 'the host
> computer simply knows which protocol it is hosting on each port' needs
> further work. At the TCP level the host neither knows nor cares about
> the protocol; at the IP level you *can* have several protocols on the
> same port, e.g. ICMP, UDP, TCP.

            An official list of all the protocols can be found here:

                        PROTOCOL NUMBERS
                        http://www.iana.org/assignments/protocol-numbers

            Of those protocols, TCP and UDP tend to be the most interesting to
most people (probably with ICMP coming in at third place) since they are so
commonly used. Here's a list of all the port numbers used for TCP and UDP:

                        PORT NUMBERS
                        http://www.iana.org/assignments/port-numbers

            Unfortunately it gets very confusing to describe these things because
the terminology is re-used. It might be easier to ask about an "IP
protocol" (e.g., TCP, UDP, ICMP, etc.), or a "TCP/IP protocol" (e.g., HTTP,
SMTP, POP3, FTP, etc.) or "UDP/IP protocol" (e.g., DNS) instead.

            It's important to note that many of the protocols that are transacted
over TCP/IP and UDP/IP are sometimes supported (and recommended to be
supported) on both IP protocols. For example, you'll find that it's
possible to successfully run a DNS query over TCP/IP port 53 as well as the
usual UDP/IP port 53 on many DNS servers around the internet.

            I hope this information will help to clear up some of the confusion.



Relevant Pages

  • Re: Windows 2000 - MS Access XP and Sql Server 2005.
    ... The library is the library for the named pipes protocol; ... adding tcp: before the name of the server. ... the right port to use) at the end. ... I can't connect a client computer with windows 2000 to sql server 2005: ...
    (microsoft.public.access.adp.sqlserver)
  • Re: VPN Error 720
    ... The Zywall is configured for passthrough of port 1723 and GRE ... I got other error messages before that was done. ... avoidance of client/server terminology) makes a TCP (IP protocol 6) call to ... TCP Port 1723 on the other endpoint. ...
    (microsoft.public.windows.server.sbs)
  • Re: RMI binding to SAME port but DIFFERENT IP address on SAME host
    ... >> The host computer simply knows which protocol it is hosting on each ... >> You can't have two different protocols hosted on the same port, ... At the TCP level the host neither knows nor cares about ...
    (comp.lang.java.programmer)
  • Re: W2K VPN Setup
    ... GRE is as IP protocol, just like TCP or UDP. ... because it is not a port. ...
    (microsoft.public.win2000.ras_routing)
  • Re: excessive TCP dulplicate acks revisted
    ... The tcp duplicate ACK attack is back. ... there was a thread on duplicate TCP acks in -CURRENT. ... TCP STREAM TEST from localhost port 0 AF_INET to greenhouse- george.18clay.com port 0 AF_INET ... Socket Socket Message Elapsed ...
    (freebsd-current)