joedj / ftpii

An FTP server for the Nintendo Wii
Other
52 stars 18 forks source link

Timeout connecting to ftpii #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What version of ftpii are you using?
0.0.18

What steps will reproduce the problem?
1. Run ftpii on wii
2. try to connect with client (far manager, ftp windows command)

What is the expected output? What do you see instead?
Expect to connect to ftp, instead a timeout. The only thing I could think
of is that I don't use DHCP on wii. Enabled, but no change.

Original issue reported on code.google.com by girts.ni...@gmail.com on 7 Mar 2009 at 5:55

GoogleCodeExporter commented 9 years ago
Is this still a problem with 0.0.19?

What does the Wii output?  Does it show you an IP address, and say that it is
listening for connections?

Original comment by joe.goo...@psychlaw.com.au on 26 Apr 2009 at 10:28

GoogleCodeExporter commented 9 years ago
This problem remains for WinSCP+FTPii_v0.0.19. Opera 9.64 and IE6.0 does not 
have 
this problem with FTPii_v0.0.19.

Original comment by drug...@gmail.com on 26 Apr 2009 at 11:59

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I don't know why, but it works now. Previously didn't even ping, now pings
successfully. I guess it was a network problem afterall.

Original comment by girts.ni...@gmail.com on 26 Apr 2009 at 2:10

GoogleCodeExporter commented 9 years ago
Great, gonna close this.  drugold's WinSCP issue is still active as Issue #37

Original comment by joe.goo...@psychlaw.com.au on 26 Apr 2009 at 2:51

GoogleCodeExporter commented 9 years ago
I know that this has been closed, but I now know what is the issue. The device 
is not
pingable = accessable from network until I run wii http server (Wii Web Server).
After that ftpii works for some time, as well as does the ping...

Original comment by girts.ni...@gmail.com on 26 Apr 2009 at 5:52

GoogleCodeExporter commented 9 years ago
Ignore my comment 6, please, the problem is with the wireless signal too weak.

Original comment by girts.ni...@gmail.com on 27 Apr 2009 at 8:05