By default, the server listens (accepts incoming connections) on 5177 and the client listens (accepts incoming connections) on 5178. If all of the clients have the 'Client Uses Nat' value set to "1" then only the server is listening (on 5177).
5177 inbound to the server. 5177 outbound from the clients. 5178 outbound from the server.* 5178 inbound to the clients.* * Not necessary if ALL clients have the 'Client Uses Nat' value set to "1" ---------- Original Message ---------------------------------- From: "Rick Leske" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Wed, 5 Feb 2003 17:03:02 -0600 >Well... I'm trying to understand.. really, > > >>IIM uses 2 ports. > >>Clients connect to the Server on tcp 5177 (think of this as the control >channel). Through this socket the client sends requests to the server and >the server acknowledges those requests. >Also, Servers talk with other >Servers on port 5177. > >Ok so the server needs tcp 5177 input/output at the server level (server >being the machien the IIM server software is installed on). > >>The Server sends asynchronous data to the Client on tcp 5178 (think of this >as the data channel). > >asynchronous data.. hmm Server needs tcp 5178 input/output too. > >>Data such as status information and conversations travel over this socket. >This is the default configuration of the Client (listening on 5178). > >>Also, by default, the Client does not maintain a socket that is always open >to the server. When the Client is sending data, it A) opens a connection to >the server (who is listening on >5177) B) Sends its request C) waits for an >acknowledgment from the server and D) closes the socket. > >hmm.. C) waits for an acknowledgement for the server.. on 5177 right? > >>With some network configurations Clients need to be configured to use >persistent connections (i.e. maintaining an open socket to the server all >the time). This is when the NAT flag >should be set on the Client. In this >configuration, the Server does not talk to the Client via port 5178. Instead >it uses the persistent socket that was established when the Client logged >>on to the Server. > >Now this has me confused.. if a port is opened.. say 5177 to the Server and >the Server accepts the connection.. are you telling me that the client >software is 'not' going to keep the socket open but rather close the socket? >I thought most client/server socket handling was achieved at the server >level. If a NAT flag is required to 'keep alive' the socket from the >clients perspective I would think you should elimate that all together and >just assume that most people would want the connection alive. So the client >side software needs tcp 5177 inbound/outbound and 5178 inbound/outbound only >if you want to stop the server from disconnecting the socket... right?. > >>Also, there is a Help Topic in the Server Help that further explains the >NAT configuration issues. > >Recap? open 5177 and 5178 tcp for both input and output? > >~Rick > >___________________________________________________________________ >Virus Scanned and Filtered by http://www.FamHost.com E-Mail System. > > >To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html >List Archive: http://www.mail-archive.com/ipswitchim_forum%40list.ipswitch.com/ >Knowledge Base/FAQ: http://www.ipswitch.com/support/Instant_Messenger/index.asp > ________________________________________________________________ Sent via the KillerWebMail system at alpha.ipswitch.com To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/ipswitchim_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/Instant_Messenger/index.asp
