Windows Server 2012

[Knersuss]

Hi guys,

I have switched to using my hub from my own client as the instance running in my Windows Server 2012 has stopped accepting my local LAN connection..
When i connect via another network or my friends join the server it works but I am completely unable to connect to it unless I go to 3G.

Any suggestions will be appreciated... It used to work for a very long time and the only difference is that I upgraded the JoinFS Client as obviously installed MS updates as required.

Regards,
Nico

[Peter]

Are you connecting on the same machine? If so, there was a recent design change that disallows this. Is this something that you really need to do? You could just use the instance that's already running?

Peter

[Knersuss]

Hi Peter,

No it is two different systems.

The purpose of the server is to serve when I am not there.

I currently run the client with hub mode on my PC to deliver the service but that means I need to have my PC on all the time

The server runs 24/7/365 so it makes seems to have the hub running there... and it used to work very well when i used my LAN to connect to it.

Regards,
Nico

[Peter]

Both of the screenshots say Hub enabled. Should’t the other one be a normal client?

Peter

[Knersuss]

Peter,

Both screenshots are from the server, just different JoinFS versions

The feeling is that the LAN joining capability has been removed again. Like I said it works as long as I am not on the LAN and then try and connect to it.

This is a problem as I have another club looking at joining JoinFS but if LAN connections are not usable we are wasting our time with it and need to get Internet hardware in place to use this program and brings cost up etc....

[Peter]

I just tried version 1.3.44 and it connected over the LAN no problem. Even with one as a hub I was still able to connect to it. What address are you using to connect?

Peter

[ATC Roo]

I can also confirm that 1.3.44 works over LAN on my setup, using an internal IP to connect to the hub.

[Knersuss]

Thank you gentlemen, I have no doubt that you can connect local but the questions is, are you using Windows server 2012 as the O/S on the server?

[Peter]

I only have Windows 10 I'm afraid. But I'm sure nothing has changed that would start causing a compatibility issue with Windows. JoinFS still uses a single UDP port for communications. However, the way is remembers port numbers has changed slightly. I would check your port forward settings and make sure you still have static IP addresses on the relevant machines and that different ports are used for each machine and configured accordingly in the router.

Peter

[ATC Roo]

Thank you gentlemen, I have no doubt that you can connect local but the questions is, are you using Windows server 2012 as the O/S on the server?

I'm afraid I'm not.
I checked LAN connection from a Windows 10 OS to a Centos 7 OS.
I only mentioned I was able to connect so that Peter knew that it wasn't only his machines that worked over LAN.

As Peter mentioned above..
Are you using the Internal IP address or External IP address to connect?

I assume he asked this as some Routers are not able to connect to a LAN machine via your External IP.
This is sometimes referred to as a NAT Loopback.

[Knersuss]

Thank you guys for your assistance.

I created a small windows 7 VM and loaded it on my Windwws Server 2012.
It appears to be working as expected but, before I sign off on this mission, I would like to get the gang together on our side and test it with a few guys together and not just me alone.

If this works it means that Microsoft probably killed the JoinFS operations on the Server product with one of their last updates.

Will let you guys know what ASAP