Fantasy Grounds Classic Connections Explained

[Fot5]

I don't see that. I thought that IPV6 addresses were 8 sets of 4 alphanumerics separated by colons, like asdf:1234:zxcv:0987:qwer:5678:qoiu:6543

[Fot5]

An update on my issue.

I installed PureVPN with port forwarding and a dedicated IP, and I turned off my firewall. I am able to connect to my son's game while on the VPN, but he cannot connect to mine. WTF?

[Myrdin Potter]

You should not need your firewall turned off with the VPN. Are you using the VPN IP address to connect, are all connections set at private and are you connecting to the server with the dedicated IP address and the user ID associated with it?

[damned]

Hey All,
First, Unity (FGU) works marvelous. I love it. My players love it. No issues there (or at least I hope not after I have monkeyed around with my router/AV settings). Classic (FGC) however is a different story. Got FGC through Steam and hoped to use it to host at a future point for friends who's systems are 5-10+ years old (and most notably not 64 bit). Run the connection test in FGC and come up "FAILURE." I have tried several combinations and looked for anyone who might have had similar ISP/AV setups and had similar problems. Here is my responses to the pinned questions.

The reason for asking all 8 questions is that the answer is usually revealed in the answers.
You need to find the WAN address that the router shows
and post the tracert
For AV and firewall rules you need to accept incoming connections on tcp1802 do not set the source port

[damned]

2. The first two sets (octects) of your WAN IP as displayed by Fantasy Grounds and as displayed by your Router:
FG: 173.28
Router: 173.28

6. Post the results of the tracert 8.8.8.8 command (if you have security concerns you can remove this bit once its been responded to)
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 54 ms 2 ms 6 ms www.gryphoncare.com [192.168.1.1]
2 6 ms 10 ms 3 ms 192.168.0.1
3 16 ms 22 ms 151 ms 10.164.3.1
4 14 ms 22 ms 21 ms 172.30.11.9
5 29 ms 36 ms 27 ms 68-66-73-64.client.mchsi.com [68.66.73.64]
6 34 ms 47 ms 35 ms po13.chgil001cr1.mchsi.com [68.66.72.41]
7 37 ms 28 ms 55 ms po10.chgil001er1.mchsi.com [68.66.73.122]
8 39 ms 36 ms 141 ms 72.14.194.2
9 32 ms 42 ms 33 ms 74.125.251.149
10 34 ms 38 ms 156 ms 108.170.238.139
11 53 ms 35 ms 33 ms dns.google [8.8.8.8]

Trace complete.

Mostly when you have 4 private network hops like you do in the tracert you cant do port forwarding.
However in #2 you say that the router shows the same WAN IP address as FG reports.

Which device shows 172.38.something as its WAN ip address?

What device is 192.168.1.1?
What device is 192.168.0.1?
Can you browse to 10.164.3.1?

[Fot5]

I've resolved the issue. Apparently, a VPN client (Checkpoint VPN) that I installed for a company I'm working created the problem. If I run FGC without that software installed (FGC won't even work if I completely quit the software--it can't even be running in the background unconnected), then everything works fine. As soon as I install Checkpoint VPN, the problem comes back. I haven't figured out what is going on with the VPN client to cause this, but at least I've identified the source of the problem.

[CD0369]

The reason for asking all 8 questions is that the answer is usually revealed in the answers.
You need to find the WAN address that the router shows
and post the tracert
For AV and firewall rules you need to accept incoming connections on tcp1802 do not set the source port

Hello Damed,
My AV/Firewall are configured to allow incoming on TCP port 1802. My buddy downloaded FGC and is on my home network. We were able to connect to each other without a problem. While he was connected, I ran netstat. The results were: netstat -an | findstr "1802" TCP 192.168.4.32:1802 192.168.4.53:51731 TIME_WAIT

After some time, was finally able to get my WAN info from my modem. It does match FGC. Below is what I had previously deleted.

1 6 ms 4 ms 5 ms 192.168.4.1
2 8 ms 5 ms 4 ms 192.168.0.1
3 26 ms 27 ms 55 ms tukw-dsl-gw70.tukw.qwest.net [63.231.10.70]
4 29 ms 26 ms 25 ms 63-226-198-41.tukw.qwest.net [63.226.198.41]
5 186 ms 29 ms 25 ms sea-edge-12.inet.qwest.net [67.14.41.58]
6 29 ms 28 ms 26 ms 63-158-222-114.dia.static.qwest.net [63.158.222.114]
7 28 ms 31 ms 25 ms 74.125.243.193
8 29 ms 28 ms 25 ms 209.85.254.237
9 26 ms 28 ms 26 ms dns.google [8.8.8.8]

For whatever reason, I cannot get my snips (.PNG format) to copy to the forum. Let me know if you want them and how you would like me to get them to you.

***Update***
Did a factory reset on my modem. Redid the settings on it and now it works properly. Sorry for the inconvenience.

[Myrdin Potter]

I've resolved the issue. Apparently, a VPN client (Checkpoint VPN) that I installed for a company I'm working created the problem. If I run FGC without that software installed (FGC won't even work if I completely quit the software--it can't even be running in the background unconnected), then everything works fine. As soon as I install Checkpoint VPN, the problem comes back. I haven't figured out what is going on with the VPN client to cause this, but at least I've identified the source of the problem.

When using PureVPN, you do not need to port forward with the dedicated option. You turn PureVPN on and then run Fantasy Grounds. Connection test should succeed. I assume the other VPN client is interfering in some way. You might ask PureVPN tech support.

[Nylanfs]

I've resolved the issue. Apparently, a VPN client (Checkpoint VPN) that I installed for a company I'm working created the problem. If I run FGC without that software installed (FGC won't even work if I completely quit the software--it can't even be running in the background unconnected), then everything works fine. As soon as I install Checkpoint VPN, the problem comes back. I haven't figured out what is going on with the VPN client to cause this, but at least I've identified the source of the problem.

A VPN that you can't turn off is an issue in my book.

[LordEntrails]

Checkpoint has probably set a network connection and set it to be the primary. Therefore even when not connected, FG is trying to use that IP to display on teh connection screen. You can either; 1) disable the network connector, or 2) go into your registry and change the network adapter order so your VPN is after your regular NIC.