rsistoch wrote: Sun Oct 12, 2025 3:17 am Hi Funchi-san.
I tested it and it works fine when using it on same computer.
I tested it on 2 different devices and it doesn't get a signal.
PC using wired network and laptop using wifi, the public IP address is the same.
I tried filling both public IP and private IP of the laptop (receiver) in FNC Sender indicator on PC but still can't get a signal.

Thank you for verifying the operation between PCs.

First of all,
it is essential that both devices are on the same network.
Only private IP addresses are accepted.

On top of that,
the communication must be allowed through the Windows Firewall on each PC.

Normally, a "Windows Security Alert" window will appear, in which case you must click "Allow access".
If the alert window does not appear, you will need to manually configure the Windows Firewall settings.
These are mandatory steps.

In this particular case, it is also likely that the router settings need to allow communication between the wired PC and the wireless PC.
It depends on the router you are using.

If you are using a security appliance such as a UTM, you may need to ask your network administrator to configure the settings accordingly.

All of these are network-specific configurations within your local environment.

At this point, that is all I can explain to the best of my understanding.
I do realise that this could potentially be resolved by simply purchasing a new PC on my end, and I sincerely apologise for the trouble.

The FNC_LINK uses Windows' ws2_32.dll.
To be honest, it is intended to be capable of a variety of functions.
However, the setup procedure varies depending on the PC and network environment.
Providing support for this would be a considerable burden on me, so my position is that only those who know what they are doing should attempt to configure it.
Needless to say, connections to other networks have not been tested.

Well, nowadays I believe most issues can be resolved by looking things up on the internet.

funchi wrote: Sun Oct 12, 2025 8:46 am Thank you for verifying the operation between PCs.

First of all,
it is essential that both devices are on the same network.
Only private IP addresses are accepted.

On top of that,
the communication must be allowed through the Windows Firewall on each PC.

Normally, a "Windows Security Alert" window will appear, in which case you must click "Allow access".
If the alert window does not appear, you will need to manually configure the Windows Firewall settings.
These are mandatory steps.

In this particular case, it is also likely that the router settings need to allow communication between the wired PC and the wireless PC.
It depends on the router you are using.

If you are using a security appliance such as a UTM, you may need to ask your network administrator to configure the settings accordingly.

All of these are network-specific configurations within your local environment.

At this point, that is all I can explain to the best of my understanding.
I do realise that this could potentially be resolved by simply purchasing a new PC on my end, and I sincerely apologise for the trouble.

As far as i know if there are 2 devices on the same network and have the same private ip address then one or both will dissconnection.

rsistoch wrote: Sun Oct 12, 2025 9:04 am As far as i know if there are 2 devices on the same network and have the same private ip address then one or both will dissconnection.

There may have been a translation issue in one of your previous posts.
Are you a native Japanese speaker?
If that is the case,
I will provide some additional explanation in Japanese."

funchi wrote: Sun Oct 12, 2025 9:12 am There may have been a translation issue in one of your previous posts.
Are you a native Japanese speaker?
If that is the case,
I will provide some additional explanation in Japanese."

日本に住んでいる外国人ですが、日本語がわかりますので、日本語で話していただいて大丈夫です。

Apologies for not thoroughly reading your explanation in the previous post.
Let me restate the issue for clarity:
Both the PC and the laptop are connected to the same network.
They are both configured to use a private network profile.
Telnet has been enabled on the PC, and I have verified the internal network connectivity between the PC and the laptop by performing a ping test via CMD.
The results confirm that both devices can successfully communicate with each other over the local network.
I’m still researching additional information online. If I find anything new or if the issue is resolved, I will report back to you.


Is it possible to add a parameter to set the PORT manually?

rsistoch wrote: Sun Oct 12, 2025 12:40 pm Is it possible to add a parameter to set the PORT manually?

The "Pairing ID" parameter is used to configure the port. It increases or decreases the base port number 49000 based on the value of the "Pairing ID" parameter.
For example:
If the "Pairing ID" is set to "1", the port will be 49001.
If the "Pairing ID" is set to "-1", the port will be 48999.
The "Pairing ID" parameter can be set within the range of -10000 to 10000.