Re: [twsocket] Odd Behaviour

2006-03-20 Thread Dan
andes" <[EMAIL PROTECTED]> To: "ICS" Sent: Monday, March 20, 2006 12:00 PM Subject: Re: [twsocket] Odd Behaviour > Hi, > >>> You need a bigger data port range than that. This >>> will allow only one data transfer (can be a file > listing) then you

Re: [twsocket] Odd Behaviour

2006-03-20 Thread Allan Fernandes
Hi, >> You need a bigger data port range than that. This >> will allow only one data transfer (can be a file listing) then you will have problems with ports >> being in time_wait state, so having no available ports. Please correct my interpretation if I am wrong. One Ftp transfer can make use

Re: [twsocket] Odd Behaviour

2006-03-18 Thread Dan
- Original Message - From: "Allan Fernandes" <[EMAIL PROTECTED]> To: "ICS" Sent: Friday, March 17, 2006 11:21 AM Subject: Re: [twsocket] Odd Behaviour > > FtpClient1.Port=5011 > FtpClient1.DataPortRangeStart=5015 > FtpClient1.DataPortRangeE

Re: [twsocket] Odd Behaviour

2006-03-17 Thread Allan Fernandes
Hi , >> You know that FTP protocol use TWO ports. One for control and one for data. >> Maybe the data port on a server collide with the control port or data port for another one. Firstly let me apologise for my delayed reply. As I am new to this socket programming I had to read up and try out th

Re: [twsocket] Odd Behaviour

2006-03-11 Thread Guillaume MAISON
Allan Fernandes a écrit : > Hi Arno Garrels, > >>> I still haven't got your configuration and the > problem completely. >>> As far as I understand the FTP server in question >>> is listining on port 5014. >>> It has active connections downloading files, but > one of your clients >>> gets a 10061 w

Re: [twsocket] Odd Behaviour

2006-03-11 Thread Francois PIETTE
http://www.overbyte.be - Original Message - From: "Allan Fernandes" <[EMAIL PROTECTED]> To: "ICS" Sent: Saturday, March 11, 2006 5:51 AM Subject: Re: [twsocket] Odd Behaviour > Hi Arno Garrels, > >>> I still haven't got your configur

Re: [twsocket] Odd Behaviour

2006-03-10 Thread Allan Fernandes
Hi Arno Garrels, >> I still haven't got your configuration and the problem completely. >> As far as I understand the FTP server in question >> is listining on port 5014. >> It has active connections downloading files, but one of your clients >> gets a 10061 when it tries to connect, is that correc

Re: [twsocket] Odd Behaviour

2006-03-09 Thread Arno Garrels
I still haven't got your configuration and the problem completely. As far as I understand the FTP server in question is listining on port 5014. It has active connections downloading files, but one of your clients gets a 10061 when it tries to connect, is that correct? --- Arno Garrels [TeamICS] ht

Re: [twsocket] Odd Behaviour

2006-03-09 Thread Allan Fernandes
Hi Arno Garrels, >>What does this mean? Server?, client?, Port?, PasvPortRange >>or DataPortRange? Are you using Pasv mode? I use two ports for Ftp communication One set of TFTPClientP1 and TFTPServerP1 using port 5011 is used to communicate between MyNode.exe's. The other set TFTPClientP2 and T

Re: [twsocket] Odd Behaviour

2006-03-07 Thread Arno Garrels
Allan Fernandes wrote: > P1 denotes port = 5011 and P2 denotes port = 5014 >(I have tried changing ports to 6011 and 6014) What does this mean? Server?, client?, Port?, PasvPortRange or DataPortRange? Are you using Pasv mode? > The Problem: > All Transfers via P1 are perfectly OK, but