ftflow

Thanks for your replies so far. I certainly know 192.168.0.1 is not my WAN IP but only my LAN gateway, it sounds like it can't get past my gateway or something. Although, it now correctly shows me as having Apex, and I can also connect actively, but my IP still shows as 192.168.0.1...I wonder if the problem will arise again (of having to connect passively) I've always had my client computer (and server computer) as static reserved address in router. Something's definitely wrong in some way.

Hi, I recently started my own hub where I have it running on Ptokax with Dixbot script. In my hub, Apex thinks (or is it my server that thinks?) my WAN IP is 192.168.0.1 and that my client is DC++ 0.706! I can only connect to people in passive mode, and even then it still has problems. In other hubs, it's all fine and no problems. I've played around a lot with firewall port forwards to no avail. I'm sure it's possible to actively connect to my own server behind the same router, I know a friend who does it. Many thanks for your help. I guess this is the best place to ask (if it's not, please let me know - not exactly sure if it's an Apex problem or Ptokax problem, or even a router problem)