FG Knowledge Base - Firewalls

[damned]

If you are running games at separate times change the port forward each time.
Otherwise do as above by LordEntrails.

[ddavison]

In the short term, it might just have to be a part of your standard routine when hosting a game to go into the router and edit the rule to point back to your IP.

[GarthGiantbane]

Thanks for the replies.

I'll follow that suggestion and either change the static IPs between the two PC's or edit the firewall rule depending on who's playing/hosting for the session. Probably the latter, seems easier for me.

[darthravage]

This is something I do not understand what it is or how to do it. I am not able to run a successful connection test. Would someone be willing to help me??

What do I make the inbound --- to ---?
What should the local port be ---- to ----?

[damned]

The local port is always TCP 1802
The inbound port is always TCP 1802
The source IP address is usually set to ANY, or blank or 0.0.0.0

[Uktar]

having lost an most of a Sunday just to get my friggin' internet to work again after trying to get the Port Forwarding setup so I can actually run this stupid friggin' system, I'm wondering how in the world I can get my friggin' money back. I thought it'd be fun to run my brothers in Rise of the Runelords, and now all I can think is how I've pissed away a couple hundred dollars for an ultimate license and the rise of the runelords fg so that I can waste all my time trying to figure out how to be a network admin. Why or why was I so stupid? Roll20 may be a lot more work as a GM, but all i need is a friggin' web browser. If I wanted to work in IT, I would've gotten a computers degree. Is there a sticky where people who don't want to be tech support can complain about this PITA game system?

[ddavison]

Hello Uktar,

I'm sorry to hear that you had such a frustrating experience. We offer assistance via email at [email protected] for port forwarding or any other questions you have. Please send us the make and model # of your router and send us a screenshot of your Connection Test screen from the DM's computer. It normally just takes a few minutes to set up once you've been told what to put where. After that, it rarely needs to be changed or adjusted and never needs to be set by the players. There are a few cases where it gets more complicated, but we can quickly determine that for you.

We also offer full refunds at any time within 30 days if you decide that is the best route forward for you. We truly hope you will consider giving it another shot with a little bit of help. Let us know at [email protected] either way and we'll take good care of you.

-Doug

[Trenloe]

having lost an most of a Sunday just to get my friggin' internet to work again after trying to get the Port Forwarding setup so I can actually run this stupid friggin' system, I'm wondering how in the world I can get my friggin' money back. I thought it'd be fun to run my brothers in Rise of the Runelords, and now all I can think is how I've pissed away a couple hundred dollars for an ultimate license and the rise of the runelords fg so that I can waste all my time trying to figure out how to be a network admin. Why or why was I so stupid? Roll20 may be a lot more work as a GM, but all i need is a friggin' web browser. If I wanted to work in IT, I would've gotten a computers degree. Is there a sticky where people who don't want to be tech support can complain about this PITA game system?

I'm sorry you've had problems setting up your network and that you're obviously angry.

The reasons why you bought FG are still valid - it will be a great tool to play Rise of the Runelords with your brothers. If you're prepared to take some assistance from the community, I'm sure we can get you up and running.

If you're beyond that, then send an email to [email protected] and I'm sure they'll issue you a refund.

And no, there is not one single thread where people can complain. I don't really see the point in that. You've posted that you have issues getting port forwarding setup, in the right thread for that issue. If you want to officially complain, rather than just publicly get something off your chest, then use the support email I mentioned above.

My recommendation would be to try to get it working with our assistance. If you're willing, try these:
1) From a windows command prompt, type tracert 8.8.8.8 and post the results here. This will tell us your network architecture and if there might be issues with how your ISP has setup your Internet connection.
2) Make sure your network is set to Private not public, in Windows Network and Connections Center.
3) Make sure FantasyGrounds.exe has an exception in your security/anti-virus software.
4) Let us know the make and model of your Internet router, so we can help you setup port forwarding.

EDIT: Doug replied while I was typing...

[Gwydion]

I feel your pain, Uktar. When I first purchased Fantasy Grounds I took my internet down for 2 days trying to port forward! I was too nervous to ask for help on the forums. Once I got that sorted, its been nearly 2 years of the most fun I've ever had. I was so frustrated those first couple days, though, I almost quit on the program. I'm so glad I didn't and I really hope you don't either. I mean it when I say this community is the best I've ever seen for jumping in and helping people. Good luck!

[Uktar]

Thanks for the rapid response

Here's what came up when I ran tracert 8.8.8.8 :

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 13 ms 16 ms 13 ms cpe-174-109-128-1.nc.res.rr.com [174.109.128.1]
3 17 ms 15 ms 18 ms cpe-174-111-106-034.triad.res.rr.com [174.111.106.34]
4 21 ms 16 ms 16 ms cpe-024-025-062-150.ec.res.rr.com [24.25.62.150]
5 23 ms 21 ms 19 ms 24.93.67.202
6 25 ms 29 ms 30 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
7 26 ms 29 ms 39 ms bu-ether11.atlngamq47w-bcr01.tbone.rr.com [66.109.6.35]
8 27 ms 21 ms 23 ms 0.ae3.pr1.atl20.tbone.rr.com [107.14.17.190]
9 27 ms 26 ms 23 ms ix-ae-14-0.tcore1.A56-Atlanta.as6453.net [64.86.113.37]
10 24 ms 22 ms 24 ms 64.86.113.106
11 * * * Request timed out.
12 27 ms 23 ms 22 ms