execftps refuses connection

[weissbierwicht]

Hi folks!
that damn execftps makes me go mad.
i installed pukklink 1.0b on my memorycard (original sony in a v7 ps2 chipped with ***3 2.0 flash 2.3 and *** explorer)
using inlink 1.3.7 i started execftps on my unit.
it boots up and says "ftp server ready on port 21" but i cant connect with any ftp client. i have not yet installed a HDD. just wanted to browse through the files stored on my MC.
all ftp clients report "connection refused" at the very beginning of the connection process.
since i don't own a crossover network cable i'm connecting to my ps2 through an ethernet switch, which should not be a problem at all.
any help would be appreciated, i'm willing to do everything to get that ****in' thing working.
thanx for your help, oh, and im sorry if im to dumb to use the search function and anyone posted this before...
wbw

[bladezero]

i had this problem when trying to run execftps from hdloader. the thing is it wont actually load and i think thats the reason why connection is denied. id recommend just making a CDR with execftps on. saves time.

[weissbierwicht]

ok, ill try that one

[weissbierwicht]

ok, thanx for your help, booting directly from cdr works. but installing on mc and booting using the *** explorer doesnt...
anyways..
what do those /mc/0 .... /mc/15 folders mean? first, i thought it could be the different memorycards, but i got only 2....

[dlanor]

weissbierwicht:
I believe your problems may be due to how ExecFTPs looks for its IP config file.
The readme.txt of the release I have specifies that it's done like this:

these following folders will be checked for the file.
mc0:/BOOT/EXECFTPS/
mc0:/EXECFTPS/
mc0:/SYS-CONF/
mc0:/SYS-CONF/IPCONFIG.DAT
if the file isnt found in any of these folders then the default net setup will be used.

Note that the *** Explorer does NOT correctly create any of those folders.
But when you boot ExecFTPs from CD-R you can use the FTP client to set up the
correct MC stuff needed for future boots from MC to work right.

As for the seeming multitude of memory cards, (we whould be so lucky... )
just ignore /mc/2/ through /mc/15/. They are just mirror images of /mc/0/ and /mc/1/,
probably caused by some oversimplification of the IRX driver code. Basically all the even
numbered entries mirror /mc/0/ while the odd ones mirror /mc/1/.

Best regards: dlanor