Sign in to follow this  
Followers 0
WOLF81

Filelists Issue

10 posts in this topic

K, just so ya get all the info hopefully someone can help me with this. I have my own hub setup and connected to another hub by another user with the same users online(we're hooked on to the same exchange and so doesn't count as downloaded data).. I can't download any file lists off my hub what-so-ever. It says 'connecting...' but that's as far as it gets. Doesn't timeout or anything. But I can download 1 of the 2 users on the other hub (we'll call him mr x) but not the other user (mr y). But on that note, mr x is capable of getting filelists of my hub. Been trying to work it out for ages and just stuck.

So the 2 questions are... Why can I not access filelists from my hub what-so-ever, and why cant I access mr y's list on the other hub either and yet I can get mr x's list on that hub??

Hope this wasn't too confusing. :)

Share this post


Link to post
Share on other sites

Does the hub run on the same machine/network you are using? Also, are you passive or active in the two hubs? If active, which of the three setting options applies to you in Connection settings?

Share this post


Link to post
Share on other sites

Does the hub run on the same machine/network you are using? Also, are you passive or active in the two hubs? If active, which of the three setting options applies to you in Connection settings?

I have got hub on the same network. To clarify the setup, PC 1 is running the hub (Using YnHub) and have apex running with me connected to the hub via local ip address. But get the issues as said in 1st post.

Also have tried PC 2 which is connected to the same network running apex using different user name and WAN ip address to connect, but doing it this way on this pc doesn't allow me to receive any file lists on either my hub or the other one. Although at least it's telling me it's timing out

One of the original users who used to run the primary hub had similar issues and has now shutdown the hub hence why I'm now running it. He's also the one user I can't get any file list of what-so-ever.

Excuse my ignorance, but I don't know about passive or active mode. Where do I find this and what does it actually do?

Just added the connection setups from apex if it might help. The black one is the one running the hub via YnHub.

//edited by Mek: screenshots moved to post attachments.

post-20976-060215200 1294567389_thumb.jp

post-20976-043305300 1294567394_thumb.jp

Share this post


Link to post
Share on other sites

The first issue I can see is the Bind address (network interface of all connections). Set is to 0.0.0.0 as was the default, in both clients.

Active/Passive refer to the 4 radio buttons in the connection window: the first three are basically active mode, the last one (firewalled - passive, worst case) is passive.

Here, set it to Passive for both clients.

Save your LAN hub into favorite hubs and enter its properties window. In the right pane, you can specify Direct connection and enter the internal IP of your PC in LAN, see the screenshot (sorry this is in Slovak but you should get the idea). Reconnect to the hub and it should be working. Do this for both clients.

//also, please use the attachment feature in this forum for screenshots so that they do not disappear during time...

post-20976-011143700 1294567259_thumb.pn

post-20976-018316400 1294567660_thumb.pn

Share this post


Link to post
Share on other sites

Latest news, I have followed your instructions but hate to say, I'm back to where I was. The bind address is now set at 0.0.0.0 and have set up to passive mode. Edited the Hub properties to specify the direct connection, but still no change. It still goes in the2 hubs all fine, but still can access only one of the 2 users filelists on the hub I don't run, and can't access either users filelists on my own hub. Exactly as it was. :) Appreciate the help by the way. Any other suggestions would be great. Could it be a settings problem with YnHub that I've done wrong perhaps?

Share this post


Link to post
Share on other sites

uhh... maybe. Try PtokaX and see if it changes.

Share this post


Link to post
Share on other sites

Well, we could do more if you could post a picture of your network with addressing scheme explained (IP addresses of networks and their netmasks), with the place of the two DC clients and the hub denoted. Perhaps I have made an errorneous assumption when reading your description :)

Share this post


Link to post
Share on other sites

OK, not sure how much info ya needed so got as many pics up for you as possible. P.S. I did originally try your suggestions from previous posts and have changed some things back again, but on that note, funny thing, I can now receive both users file lists from the other users hub, but still can't connect to them via my own hub. At least it's now localized to my hub now. Probably something I've overlooked in my apex connection settings to the hub. I'm very new to this so I haven't really got a clue :) Port Forwardinipconfigl.th.jpgg settings IP infomodemsetup.th.jpg IP used for DC network comnetip.th.jpg YnHub settings ynhub.th.jpg Apex Connection settings apexconset.th.jpg My apex hub connecton settings myhubsettings.th.jpg

Share this post


Link to post
Share on other sites

Okay. I can see you don't get a public IP address on the WAN interface of your router. You only get 10.12.12.54 so that's why you cannot be active for Internet hubs. Therefore, if you set both your clients to Passive mode (worst case), connections to Internet users should work if you enter your external (that is, not 192. and not 10. one) IP address in the External/WAN IP field. If you set 10.12.12.54 there, connections for you will be possible for other CommunityNet users but not to Internet users.

Don't forget to change youur Bind address back to 0.0.0.0

Currently, you cannot set the "Firewall with manual port forwarding" to a specific hub so passive is the only option.

If you are not going to access Internet hubs from a client, then set Firewall with manual port forwarding in your connection settings. Set 34690 as your TCP port, 34691 as UDP port, and 34692 for both the TLS/TCP and DHT/UDP ports. Set the External / WAN IP address to 10.12.12.54. Note that using these settings, you won't be able to connect to a client running on another machine in your internal network (192.168.xxx.xxx address). But you should be able to connect to other CommunityNet users with 10.x.x.x addresses.

I am afraid your network setup is too complicated for a DC client to be configured universally.

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0