Networking Forums

Networking Forums > Computer Networking > Linux Networking > change sending ports in the middle of a network

Reply
Thread Tools Display Modes

change sending ports in the middle of a network

 
 
notgiven
Guest
Posts: n/a

 
      03-12-2005, 01:08 PM
A mainframe host is sending from a specific port to a PC (an IP
address / port) using "Raw" TCP/IP. At the end of the first page they
change from the original sending port to a different port, still
sending to the same IP address and destination port. The job fails,
only the first page printing.
I think it its correct behavior on the part of the receiving system to
end the TCP stream when transmission ceases from the original port,
and assume that the transmission from the new port (same IP address)
is a new transmission.

Am I incorrect?

Any ideas or suggestions?
 
Reply With Quote
 
 
 
 
Moe Trin
Guest
Posts: n/a

 
      03-12-2005, 05:36 PM
In article <(E-Mail Removed)>, notgiven wrote:

>A mainframe host is sending from a specific port to a PC (an IP
>address / port) using "Raw" TCP/IP. At the end of the first page they
>change from the original sending port to a different port, still
>sending to the same IP address and destination port. The job fails,
>only the first page printing.


Without further information, one would have to say this is wrong, citing
RFC0793 section 1.5 - one paragraph of which reads

When two processes wish to communicate, their TCP's must first
establish a connection (initialize the status information on each
side). When their communication is complete, the connection is
terminated or closed to free the resources for other uses.

>I think it its correct behavior on the part of the receiving system to
>end the TCP stream when transmission ceases from the original port,
>and assume that the transmission from the new port (same IP address)
>is a new transmission.


From a simplistic translation, see also section 3.5, which begins

3.5. Closing a Connection

CLOSE is an operation meaning "I have no more data to send."

>Any ideas or suggestions?


Not really enough information. Perhaps reading RFC0793 might give further
ideas.

0793 Transmission Control Protocol. J. Postel. Sep-01-1981. (Format:
TXT=172710 bytes) (Updated by RFC3168) (Also STD0007) (Status:
STANDARD)

RFC1180 may also be of interest.

1180 TCP/IP tutorial. T.J. Socolofsky, C.J. Kale. Jan-01-1991.
(Format: TXT=65494 bytes) (Status: INFORMATIONAL)

Both documents are on-line at many websites such as
http://www.ietf.org/rfc/rfc0793.txt (and rfc1180.txt)

Old guy

 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
which ports are in need to be opened to change password over VPN kreit Windows Networking 9 10-30-2007 01:04 PM
Sending a "ping": Which (ICMP) ports must be open in firewall to receive answer ? Peter Waibel Linux Networking 2 03-29-2007 05:49 PM
Change DHCP listening ports Tyler Rudolph Windows Networking 3 07-23-2005 11:18 AM
Changing sending ports in the middle of a job notgiven Linux Networking 3 03-12-2005 06:12 PM
Constant sending to all ports Pete Broadband Hardware 0 02-11-2004 10:26 PM



1 2 3 4 5 6 7 8 9 10 11