Fantasy Grounds Classic Connections Explained

[RunningWolf]

Networks that are very unlikely to work
To save you time in working all the way thru to the end the following setups are highly unlikely to work:
GM is tethered to a mobile phone or mobile hotspot
GM network is connectd by Sattelite

That explained the issue I was having when I was asking on Discord Situation solved on my home box now. It was also crewing up my email program.

[MicCheckOneTwo]

I just open tcp1802 completely
its not a commonly scanned port and residential networks are not typically aggressively port scanned on all ports
and if FG wasnt open but something else was listening at that time on TCP1802 they would need to have an attack ready for whatever that app was right away
the risk is i think pretty low

Even that hasn't done it. I'm just kinda scratching my head on why, because (as far as I can tell) it should be working. My firewall has a pinhole open for TCP 1802 on any program. Still failing tests.

[Myrdin Potter]

My experience is if the port really is open, then your firewall is blocking something. Delete the program from the firewall and add it again when it tries to connect.

[damned]

Even that hasn't done it. I'm just kinda scratching my head on why, because (as far as I can tell) it should be working. My firewall has a pinhole open for TCP 1802 on any program. Still failing tests.

If you would like me to have a look at it with you please send me your email via PM.

[MicCheckOneTwo]

My experience is if the port really is open, then your firewall is blocking something. Delete the program from the firewall and add it again when it tries to connect.

Just tried that. Still no luck. I also checked to make sure the port is empty before I connect. It's not in use or reserved beforehand, then is set to "Listening" when connected. So I'm pretty sure it's not my firewall blocking anything. I'm gonna send damned a PM, and we'll see where it goes from there.

[MicCheckOneTwo]

Just figured it out with damned's help. It was because my first router was DMZ'ed to my second, but those specific ports were forwarded to the second router's OLD ip address. Before I tried DMZ I had just forwarded that port to the second router by itself. So when I set router 1 to DMZ instead, it assigned router 2 a new IP, and that port was still only forwarded to the old IP in router 1. So it was basically DMZ'ing everything EXCEPT that port, as it was still forwarded to the old IP. Unforwarding the old IP fixed the issue.

Damned, I owe you a beer if you ever find yourself in Texas.

[Jaume]

Hi! help me please!!
I'm running out of ideas on how to fix my FG connection

1. LAN IP Address: 192.168.87.194
2. The first two sets (octects) of your WAN IP: 192.168
3. Wireless
4. Network and Sharing Centre: Private
5. Confirmation of what AV: Kaspersky Internet Security (FG is marked as trusted app) I have created in KIP and Windows firewall rules for FG port
6. tracert to 8.8.8.8
1 11 ms 10 ms 10 ms 10.251.200.1
2 11 ms 11 ms 11 ms vlan25.as03.cph1.dk.m247.com [185.206.224.241]
3 27 ms 32 ms 29 ms 83.97.21.164
4 11 ms 10 ms 11 ms xe-2-0-3-0.bb1.cph1.dk.m247.com [83.97.21.230]
5 11 ms 11 ms 11 ms kbn-b3-link.telia.net [213.248.89.118]
6 21 ms 20 ms 19 ms kbn-bb3-link.telia.net [62.115.121.14]
7 20 ms 19 ms 19 ms s-bb3-link.telia.net [62.115.139.168]
8 20 ms 20 ms 19 ms s-b6-link.telia.net [62.115.133.29]
9 20 ms 20 ms 20 ms 74.125.32.56
10 * * * Timeout.
11 21 ms 20 ms 20 ms dns.google [8.8.8.8]

my setup: my pc is connected to a Cisco WAP551 that is connected by ethernet to a fiber box that I have no control.
I have talk to my ISP (owner of the fiber box) and they claim all ports are open (despite canyouseeme.org says the opposite)
I have tried Hamachi without success, users can connect to my networks but fail to connect FG or ping me (running a diagnose says ports are closed)
What I find surprising is FG is the only software to have this problem, I have no problem hosting games on steam, or using other p2p software like torrent
I will extremely appreciate any help you can provide me :-)

[damned]

welcome Jaume

Answers 1 and 2 and 6 dont gel...
can you post screenshots please?
What FG shows
what tracert shows
and what the status page of your router shows

[Jaume]

Hi Damned
yep, I know it don't has too much sense, also considering during all the week I had two IP jumps at the beginning.
So after writing the post and reviewing the firewall once again I decided to restart computer and fiber box.

Now it looks again as usual.
Ipconfig shows IP 192.168.87.194 which is matching the internal IP displayed in FG, the external Ip is 212.112.152.102

Here is the tracert
1 1 ms 1 ms 1 ms 192.168.87.1
2 4 ms 4 ms 4 ms 100.80.0.3
3 6 ms 6 ms 6 ms be201.est-pe30.link.stofa.net [178.155.255.222]
4 7 ms 7 ms 8 ms be211.lyk-dist01.link.stofa.net [212.10.45.34]
5 6 ms 6 ms 6 ms be207.koldg-cor01.link.stofa.net [178.155.255.59]
6 7 ms 6 ms 6 ms be200.koldb-dist02.link.stofa.net [178.155.255.187]
7 5 ms 6 ms 6 ms be217.dck-pe02.link.stofa.net [212.10.13.217]
8 6 ms 6 ms 6 ms 100.127.255.231
9 7 ms 7 ms 7 ms be300-4094.dck-pe02.link.stofa.net [212.112.132.24]
10 7 ms 7 ms 7 ms be217.koldb-dist02.link.stofa.net [212.10.13.216]
11 9 ms 7 ms 7 ms be200.koldg-cor01.link.stofa.net [178.155.255.186]
12 7 ms 7 ms 9 ms be102.koldt-br01.link.stofa.net [212.10.45.202]
13 16 ms 16 ms 16 ms be101.koldt-cor01.link.stofa.net [212.10.45.201]
14 17 ms 17 ms 17 ms be191.koldt-cor03.link.stofa.net [178.155.255.132]
15 17 ms 16 ms 16 ms be200.frnx-br01.link.stofa.net [89.184.134.79]
16 16 ms 16 ms 18 ms 74.125.50.94
17 16 ms 16 ms 16 ms 108.170.251.129
18 17 ms 19 ms 16 ms 72.14.234.115
19 16 ms 16 ms 16 ms dns.google [8.8.8.8]

No way to post screenshot of the router status page since I don't have access to the router :-(
I´m not even sure if I do have a router, according to the ISP support they have activated the router build in the fiber box for me and assigned a local fixed IP (nat44) but still no way to reach the web interface of the router.

[damned]

Your ISP is giving you misinformation.
While they are not blocking anything they are doing something called carrier grade NAT and this means you cannot do port forwarding yourself.

Either they need to Port Forward TCP 1802 to your router (and yes you do have a router you can log into) or you need to use one of the Port Forwarding alternatives.
Hamachi is nice and simple to setup in most cases.