io not available from outside my network

[LordM]

Hi folks!

I set up my io just like I used to the last years. Some passive ports forwarded, port 9999 and 9998 forwarded too.

But since some time it is not available from any other computer than the machine it is running on.

I confed host.rules like this just to get a connection from another machine inside my local network:

POLICY ACCEPT 4

CLASS ADMIN -1

ACCEPT I 192.168.178. ADMIN -1



Ports are open, but connection times out.


Any idea, why this could be???

thanks in advance.

[Yil]

Check out the /logs dir and see if it's reporting rejected connections which it will for Hosts.Rules issues. My guess is you are trying to login to the ioFTPD account which is configured by default to ONLY accept loopback connections for security reasons. So either add your local lan to ioFTPD account, or create another account and add it to that... Either way the reason for the rejection should be in a logfile entry.

[LordM]

I'm trying to login into a normal user account.

IP added is *@*

And I don't get any entries in the logfiles. :(

[Yil]

Hmm... Firewall issue? You mentioned ports forwarded, but to the correct IP/port?

If you can connect to the machine from another computer inside the router then it's a network issue somehow... What is HOST= set to?

[LordM]

No firewall installed.
Well, IP and ports are correct. gotta check from another machine inside my router.

Host is set to: 0.0.0.0

[LordM]

okay. Tried from another machine inside my router. I don't get a connection there too.
And again no log entries for blocked IPs or something like that.

EDIT:
Tried other programs, and they are available from inside and outside...

EDIT 2:
Downgraded to 6.2.1 and that one works with same setup in Hosts.Rules and ioFTPD.ini!!!

Now I'm confused.

[Yil]

If it's the identical ioFTPD.ini and Hosts.Rules files (it's WAY too easy to mess up ioFTPD.ini file in some subtle way) and everything else the same except the executable then I'm baffled since you can talk to it locally so you know it's running in both cases...

If you drop both version into the same system dir and run one then the other and the newer fails, but the older works, then try reverting to a plain generic 6.3.5 file or even a 6.2.1 file just to rule out new features like something wierd going on with immune hosts, users, etc.

[LordM]

As I said: 6.2.1 exe with 6.2.1 ini file works.
I tested the 6.3.5 exe with 6.2.1 ini and it works.
Then I tried 6.2.1 exe with 6.3.5 ini and it works too.

Only 6.3.5 exe with 6.3.5 ini doesn't work.