connection refused execftps...

[SnowSurfer]

(using a cross over cable)

I start the execftps server on my ps2..it goes to the default settings,

ip 192.168.0.10
netmask 255.255.255.0
gateway ip 192.168.0.1

says ftp server started on port 21

i am using version 3.2 of flashfxp

i set my network card to ip 192.168.0.11
netmask 255.255.255.0
gateway ip 192.168.0.1

i am able to ping the ps2 but every time i try to ftp to it this is what happenes

WinSock 2.0 -- OpenSSL 0.9.7g 11 Apr 2005
[R] Connecting to ps2 -> IP=192.168.0.10 PORT=21
[R] Connection failed (Connection refused)
[R] Delaying for 120 seconds before reconnect attempt #1
[R] Retry attempt Aborted
[R] Connecting to ps2 -> IP=192.168.0.10 PORT=21
[R] Connection failed (Connection refused)
[R] Delaying for 120 seconds before reconnect attempt #1
[R] Connecting to ps2 -> IP=192.168.0.10 PORT=21 (attempt # 1)
[R] Connection failed (No route to Host)
[R] Delaying for 120 seconds before reconnect attempt #2
[R] Retry attempt Aborted
[R] Connecting to ps2 -> IP=192.168.0.10 PORT=21
[R] Connection failed (Connection refused)

passive mode is off in flashfxp...any ideas? thanks

[radalv]

PS2

ip 192.168.0.10
netmask 255.255.255.0
gateway ip 192.168.0.11

PC
ip 192.168.0.11
netmask 255.255.255.0
gateway ip 192.168.0.10

Try it this way, I read this somewhere, probably on these forums. But I hace not tried it this way, I do not know if it works.

Good Luck

[zabolyx]

Make sure that FlashFXP has passive mode turned off.....

[dlanor]

(using a cross over cable)

I start the execftps server on my ps2..it goes to the default settings,

ip 192.168.0.10
netmask 255.255.255.0
gateway ip 192.168.0.1

says ftp server started on port 21

i am using version 3.2 of flashfxp

i set my network card to ip 192.168.0.11
netmask 255.255.255.0
gateway ip 192.168.0.1

In the above you are specifying three IP addresses:
192.168.0.10 = IP address of the PS2 network adaptor
192.168.0.11 = IP address of the PC network card
192.168.0.1 = IP address used by either of the abiove for general traffic, but here used incorrectly since no connected MAC address corresponds to that IP address.

When a gateway is defined, it must always specify a physical unit connected to the network for which it is to act as gateway. Strictly speaking, any unit on a local network should be able to communicate with all other units connected directly to the same ethernet, regardless of any gateway specified, as the gateway should only be used for traffic outside the local ethernet. (Here for traffic outside of 192.168.0.???.) But that is NOT how the PS2 drivers work. They apparently assume that ALL traffic must go through a gateway. (This indicates a faulty implementation of ARP.)

So to follow these non-standard rules there are several things you can do, but only one which make any real sense, being the minimum change solution.

Keep all settings at the PS2 end as they are (the default values), but change settings for the PC network card as follows:
IP = 192.168.0.1 (so the PS2 will see this PC as its gateway)
Gateway = blanks (A healthy PC doesn't need any gateway for this traffic)

The effect of this should be identical to the effect of the changes radalv suggested, except that my method allows you to use the default settings at the PS2 end, and uses no redundant gateway spec at the PC end.

These settings are similar to what I use, except that I don't use the default subnet 192.168.0.x (for reasons not connected to this kind of problem).

Best regards: dlanor

[SnowSurfer]

ok problem solved, i loaded the elf from an image in hdloader and it worked fine, stupid me. is dms hdd loader a piece of crap?

all the elf's that came in this package i got off ps2hd dont seem to work very well...

how do i go about installing elfs into the dms hdd explorer interface? thanks

if these questions dont really make any sense ill report them tmrw

[SnowSurfer]

ok how do i go about wiping my hard drive squeaky clean, im going to do this the right way this time...with launchelf and elfs no crappy dms stuff

[Kormann]

With ExecFTPS 0.68 FlashFXP could connect to it perfectly..
but now with ExecFTPS 0.69, I get connection refused

ExecFTPS 0.69's default config:
ip 192.168.0.141
netmask 255.255.255.0
gateway ip 192.168.0.1

PC's Network Card for PS2 Use
ip 192.168.0.1
netmask 255.255.255.0
gateway ip BLANK

I want to use 0.69 so much.. because it fixes many bugs.
My Windows is XP Pro, and I have 2 network cards.. one for my pc broadband connection.. and the other is for my ps2..
I'm using ExecFTPS 0.69 from DM$HddExplorer 1.31

[]'s
Kormann

[Kormann]

I realized that my network configuration is right and the problem is that ExecFTPS 0.69 and previous versions fully works from memorycard with its config.dat in the same folder... in the other hand it doesnt work from HDD.
I have tried DMS Hdd Explorer 1.31 and unofficial LaunchELF with no sucsess (maybe if I put config.dat in the same hdd folder when loading from LaunchELF it could run.. but its just a maybe).. I could only make it work from DMS MC Explorer

Does someone has any clue because it happens?
I think SlickStick messed up things because he didnt gave to the public his source code =/

[]'s
Kormann

[dlanor]

I realized that my network configuration is right and the problem is that ExecFTPS 0.69 and previous versions fully works from memorycard with its config.dat in the same folder... in the other hand it doesnt work from HDD.

Wrong. It does work from HD, but then has the same problems as all other software in finding where it was launched from. This is because the PS2 implementation of HDD filesystems uses a weird system for mounting partitions as virtual devices (usually 'pfs0:'). Using paths like that in the argv[0] argument passed to a launched program does NOT tell it where it was launched from, as that depends on what's currently mounted, which may even be dropped during the launch itself (depends on launch methods).

Because of this problem, most HDD compatible homebrew software look for settings in a folder on MC instead, with "mc0:/SYS-CONF/" being used by most such programs. This includes ExecFTPs and most other networking homebrew apps, which all look for "mc0:/SYS-CONF/IPCONFIG.DAT".

I have tried DMS Hdd Explorer 1.31 and unofficial LaunchELF with no sucsess (maybe if I put config.dat in the same hdd folder when loading from LaunchELF it could run.. but its just a maybe).. I could only make it work from DMS MC Explorer

Just so you know...
uLaunchELF has a new special command "MISC/PS2Net" which launches ps2ftpd (similar IOP module as used by ExecFTPs) to run in the background. You can then use FTP clients just as you would with ExecFTPs, without having to launch any ELF.

E P, another developer working on uLaunchELF, has made various fixes to the version of ps2ftpd used, to give it some (though not all) of the changes SlicStic had in ExecFTPs. You should try it and see how it works out for you.

Does someone has any clue because it happens?
I think SlickStick messed up things because he didnt gave to the public his source code =/

Doing so would have been a good thing, and normal courtesy in any case, since he based his code on an existing opensource project. Still, that choice was his to make, and we should let it go at that.

Best regards: dlanor

[Kormann]

Thank you for your reply dlanor

I have tested MISC/PS2Net (with uLaunchELF) before installing execftps.. But I had a problem, I couldnt see the content of my PS2HDD... I tried to mount partitions like I did before with execftps and nothing..(using FlashFXP3.2) Maybe I need some tips.. do you know any?


Offtopic now: Talking about uLaunchELF.. it would be good if launchELF had compatibility with DMS PS2VideoFIX.. it has a conflict when FORCE_NTSC is activated on DMS configuration... (I have to enable this option to play some imported games on HDLoader)
Or maybe if uLaunchELF had a built-in ps2video fix.., it would rock also (especially for ppl that doesnt have a modchip with this kind of videofixes.. thats not my case.. but I'm think in the others ;P)

See ya!