🚀 go-pugleaf

"Tom Berry" <tberry1@triad.rr.com> wrote in message
news:rspk32lgs0pasj0k68j8ku3m3t8goumf5s@4ax.com...
> I am using C++ 6 and Indy

Which specific version of Indy ar you using?

> It works OK with all my users except SOME WIN XP machines.
> They will get the error "Socket Error 11004".

At which point in the code exactly?  Did you verify that you are specifying
the correct Host string and Port number?


Gambit

On Mon, 10 Apr 2006 11:19:39 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:


>Which specific version of Indy ar you using?
>
The Verson properity says 8.0.25


>At which point in the code exactly? 

I am not really sure since it doesn't happen on my computer but I can
put a trap in the code and send it to one of the customers that has
the problem to find out.

> Did you verify that you are specifying
>the correct Host string and Port number?

Yes it does work for most my users - just a few Win XP users.

Thanks
Tom Berry

On Mon, 10 Apr 2006 11:19:39 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:

>
>Which specific version of Indy ar you using?
>

Do you think I should update to the latest Version 9?

Thanks
Tom Berry

Tom Berry schreef:
> I am using C++ 6 and Indy
> 
>   TIdFTP *Browser = new TIdFTP(Application);
>     
>     Browser->Passive = false;  
>     Browser->User = UserName;
>     Browser->Password = Password;
>     Browser->Port = 21;
>     Browser->BoundIP = "";   
>     Browser->Host = Host;
>     Browser->Connect(true);
>     Browser->TransferType = ftBinary;
>      Browser->Get(Path ,true);
> 
> It works OK with all my users except SOME WIN XP machines.  They will
> get the error "Socket Error 11004".   I cannot reproduce the error on
> my XP computer.
> 
> Any idea where to start looking for a resolutation?
> 
> Thanks
> Tom Berry
> 

Could the Windows XP firewall be the reason of this error?

-- 
Max

C++U2

"Tom Berry" <tberry1@triad.rr.com> wrote in message
news:7aal32l2n60nmv5socft2smkahgmgfdts6@4ax.com...

> The Verson properity says 8.0.25

Then you are using a VERY old version of Indy that is no longer supported.
You should seriously consider upgrading to the current 9.0.50 snapshot.
Indy 9 has a lot of features and fixed over Indy 8.


Gambit

On Mon, 10 Apr 2006 14:02:53 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:


>Then you are using a VERY old version of Indy that is no longer supported.
>You should seriously consider upgrading to the current 9.0.50 snapshot.
>Indy 9 has a lot of features and fixed over Indy 8.
>
OK I will try it.   Thanks
Tom Berry

On Mon, 10 Apr 2006 21:42:03 +0200, Max <nomail@4me.nl> wrote:

>Could the Windows XP firewall be the reason of this error?


I have tried turning everything on in the firewall and it still works
on my XP computer.

Thanks
Tom Berry

"Tom Berry" <tberry1@triad.rr.com> wrote in message
news:ggkl321u5q42so8r1t4cjs3hv2jmkdq6mh@4ax.com...

> I have tried turning everything on in the firewall and
> it still works on my XP computer.

Then you need to figure out how the user's machine and/or network setup
differs from your own.


Gambit

Tom Berry schreef:
> On Mon, 10 Apr 2006 21:42:03 +0200, Max <nomail@4me.nl> wrote:
> 
>> Could the Windows XP firewall be the reason of this error?
> 
> 
> I have tried turning everything on in the firewall and it still works
> on my XP computer.
> 
> Thanks
> Tom Berry
> 
A quick scan with Google gives a number of "socket error 11004" 
messages. They seem related to either firewall software blocking 
outgoing traffic or a hostname that isn't resolved by DNS. If you are 
sure that there isn't some firewall application running on the failing 
Win XP machines, you could try to bypass DNS and use the adress of the 
host instead of its name.


-- 
Max

C++U2