You only need TCP, not UDP.
Please try the second instance of FG localhost test.
Printable View
You only need TCP, not UDP.
Please try the second instance of FG localhost test.
The test seemed to be a success. It joined.Quote:
Originally Posted by Trenloe
And by a success, I mean I could join the localhost. Does that mean people elsewhere should be able to join, despite it showing a Failure with the Connection test? I've tried joining with the laptop on the same local network and it isn't working.Quote:
Originally Posted by tekmagika
It tells us that there is something blocking communication on the network interface of your computer. More than likely security software.Quote:
Originally Posted by tekmagika
When you tried to join on the same local network did you use address 192.168.2.199 to connect?
No, I tried localhost and then the alias. I'll try the specific IP.
edit - nope, the IP didn't work either.
edit edit - I checked and my IP had changed to 192.168.2.6, which seems to be working. The laptop is currently connected.
That's probably why your connection test wasn't working too.Quote:
Originally Posted by tekmagika
You'll need to change your virtual server on the router to see this new IP address.
It's worth setting up a static IP address for your GM computer so this won't happen again.
Sounds like you will need to check your port forwarding rules. The internal IP probably changed when you rebooted your router. You also might be able to reserve an internal IP for your host so that the next time the router reboots you don't have to update the port forward rules.Quote:
Originally Posted by tekmagika
Hello FG Universe - so I have an iMac and use Parallels to run Windows 10 for Fantasy Grounds. Looking for some guidance on how to apply the above steps so I can host FG demo users with my Ultimate license. Based on the above posts, I just realized that I have the intelligence of pond scum as it applies to firewall/port configurations, so I was hoping some good-aligned forum hero would come along and rescue me from my woeful ignorance.
Hello fightingcrow60
So you are running a virtual instance of Windows?
Launch a cmd prompt and type
ipconfig
and check what IP address you have.
If the first 3 sets of digits are the same as the IP address on your Mac then you will need to setup a port forward on your router to the IP address displayed in ipconfig.
The port forward rule will go on your router and is tcp 1802 on the wan interface to tcp 1802 on this parallels ip address.
if that doesnt work do the folling in your cmd prompt
tracert 8.8.8.8
and post the first 10 lines.
and in Mac
Launch Network Utility
Click Traceroute.
8.8.8.8
Click Trace.
paste the first 10 lines here also.
WINDOWS:
C:\Users\Jeremy>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 29 ms 26 ms 28 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
MAC:
Jeremys-iMac:~ Jeremy$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 homeportal 4.767 ms 4.412 ms 1.421 ms
2 99-121-4-3.lightspeed.miamfl.sbcglobal.net (99.121.4.3) 24.578 ms 24.180 ms 24.559 ms
3 99.167.141.126 (99.167.141.126) 24.118 ms 24.496 ms 23.720 ms
4 12.83.70.21 (12.83.70.21) 26.683 ms
12.83.70.13 (12.83.70.13) 28.346 ms 30.124 ms
5 fldfl401me3.ip.att.net (12.123.153.113) 39.945 ms 32.413 ms 59.809 ms
6 * * *
7 216.239.50.55 (216.239.50.55) 29.970 ms
216.239.50.57 (216.239.50.57) 28.429 ms
216.239.50.59 (216.239.50.59) 27.412 ms
8 216.239.51.131 (216.239.51.131) 27.489 ms
216.239.51.139 (216.239.51.139) 27.423 ms
209.85.242.159 (209.85.242.159) 27.305 ms
9 google-public-dns-a.google.com (8.8.8.8) 27.166 ms 27.542 ms 26.368 ms
Trace 1 is very interesting.
What is the IP address on both the Mac and the Windows?
Windows: 10.211.55.3
Mac: 192.168.1.67
Because I run FG on the virtual Windows desktop, the "Load Campaign" screen displays the internal and external IP addresses from the Windows side. But my router's IP is 192.168.1.254, which looks more related to the Mac side.
I tried changing the Windows IP to fit with the Mac IP naming scheme, but this just made my computer run really slow and FG still could not pass the connection test (so I swapped it back to the original Windows IP settings).
Windows Firewall is configured to allow FG through on both public and private networks. I always run FG as a system administrator, not sure if that is relevant.
On my router page, I configured port forwarding on both the Windows and Mac IP addresses, but neither worked during test connection.
It is becoming quite the ordeal, lol
Use the 10.211.55.3 # in the router port forward entry.
tried that, but did not work (see PORT attachment in my previous post)
This might have been answered previously, but have you tried the Mac OSX Installation instead of running under Parallels?
hi fightingcrow60 you might need to do this as well - https://download.parallels.com/deskt...uide/31974.htm
Figured it out!! Changed my virtual machine networking preferences from "Shared" to "WiFi". This allows my virtual machine to talk directly to my router (which enabled it to pick up the correct IP addresses). The set the port forwarding on my router so that the virtual machine IP is open on port 1802.
Huzzah! +1 INT for everyone :)
Well done fightingcrow60.
I was connecting and then I'm not. I am not at all computer savy so will need some extra help or a good link to what I need to do.
The only thing I've done is log into my router and enable the port forwarding to 1802.
Have you double checked the GM computer IP address and used this to you enable TCP port 1802 to forward to your GM computer? The IP address can change, so please check what it is now and that this matches the port forwarding on your router.Quote:
Originally Posted by crb31
Would you mind pointing me in the right direction for instructions on this? I was able to connect just fine so something in my settings or router must have changed. ThanksQuote:
Originally Posted by Trenloe
For specific instructions, please provide the make and model of your router.
From a basic standpoint, this is what you'd need to know:
- When you configured port forwarding in your router you'd have needed to tell it *where* to forward the port 1802 traffic to. This would have been the IP address of your computer (probably something like 192.168.0.100 for example).
- Since then your computer could have obtained a different IP address.
- To check your computer's current IP address there are different ways depending on what operating system you're using. In Windows 10 for example you could click on your network icon in the system tray (down by your clock), click on Network & Internet Settings, click on Ethernet and then click on your Network. This should show your IP address. For more explicit instructions we'd need to know what operating system you're running.
- Once you've determined what IP address your computer has now, go back into your router and look at the port forwarding settings. Ensure your port forwarding rule is pointing to the computer's current IP.
For instructions on port forwarding for your router: find your router make/model and look for that here: https://portforward.com/router.htm
I think I figured it out. Thanks. I may need some help giving my PC a static IP - but that is for the future.
Okay, so I finally figured out the whole story when it comes to setting up FG to always have 'Success!' when running the Connection Test on macOS. I have this documented so that others don't need to go through the same frustration I did.
1. First thing we need is to find out what your computer's IP address is; this is basically the 'location' of your computer in your network. We do this in macOS by clicking on the Wi-Fi icon in the task bar
https://i.cubeupload.com/hMnVH7.png
and selecting 'Open Network Preferences'.
https://i.cubeupload.com/k7rgsy.png
2. You'll wind up with this screen:
https://i.cubeupload.com/uKUsjR.png
Whatever method you're using to connect to the internet, Wi-Fi or Ethernet (or electric camel, I dunno), you will need to know your current IP address. That is found here:
https://i.cubeupload.com/qxXOw9.png
This will be in the format of a quadrapartite number, separated by periods, such as xxx.xx.x.x. THIS NUMBER IS VERY IMPORTANT! WRITE IT DOWN!
3. Okay, now we need to assign what is called a 'Static IP' to your computer. The short of it is that, whenever you have a device that connects to your network, it has to find an opening to squeeze into, so it'll do a quick scan of what 'locations' are available. The 'location' of any connected device is determined by the last number in the IP address, which corresponds to the last 'x' in the example I just provided - for sake of absolute clarity, it is the 'x' in bold here: xxx.xx.x.x.
Now, the reason we want a 'static' (or 'fixed') IP address is that connected devices like to switch addresses for various reasons, like if a device isn't always connected to the network. A good example of this would be your smartphone; you connect it to your network to minimize your data plan usage, but once you're out of range of your network, it connects to a satellite, leaving a 'hole' in your network, which the next device that connects to your home network will fill. This is what's called a 'dynamic' IP address. It changes as needed, and for Fantasy Grounds, this is the main problem people have!
4. More than likely, your Mac will be set up 'Using DHCP', like this:
https://i.cubeupload.com/0oUfnV.png
But that's not what we need; this means that your Mac can (and likely will) change its IP address when it 'needs to', which will cause problems with FG connectivity. We need to make sure that the address doesn't change...and we do that by choosing our own address! You need to click on the 'Configure IPv4' box, and change it from 'Using DHCP' to 'Using DHCP with manual address'.
https://i.cubeupload.com/ON5tVw.png
5. Remember that number you wrote down? Well, here's where we'll need it. You will need to fill in your IP address EXACTLY in this box:
https://i.cubeupload.com/Xxgaiu.png
So, if your current IP address is 192.168.0.1, you would fill in 192.168.0.1. This will basically tell your router and modem that your computer is to always be at that address, and not to switch it up. Basically, it's a reserved parking space for your Internet access. Click 'Apply', and you're done setting up the static IP!
Caveat:. There are circumstances when you might not want to keep your current IP address, in which case, you can choose any number from 2-200 for the last number. For example, you might change your new address to 192.168.0.127.
6. Now that that's done, we can move onto Port Forwarding. What we're doing here is opening up a very specific hole in our computer's firewall/router that will allow FG to communicate effectively - kind of a carpool lane type of thing. We'll need to go to the AirPort Utility, which is inside macOS' 'Utilities' folder, which you can reach by hitting ⌘⇧-U on the desktop. Open this app:
https://i.cubeupload.com/dBjhi5.png
7. You'll be shown a window with your router (in my case, 'Daniel's AirPort Time Capsule') and the Internet depicted by icons. Click on your router:
https://i.cubeupload.com/7p9N4O.png
and click the 'Edit' button on the window that pops up. Click on the 'Network' tab, as shown below:
https://i.cubeupload.com/ohKasQ.png
8. You'll reach this screen. This is where the payoff is.. Under the section labeled 'Port Settings', you'll see a '+' symbol next to a '-' symbol. Click the '+'.
https://i.cubeupload.com/Ui0qXK.png
This will bring up the following screen:
https://i.cubeupload.com/ckZGi5.png
The red box is where you need to type in the IP address of your computer. You can enter whatever you like into the 'Description' box, but as shown above, the 'ports' boxes need to have '1802' entered - this is the port that FG will make use of to communicate. Once that is done, click 'Save', and when that window closes, click the 'Update' button highlighted here:
https://i.cubeupload.com/8BDGZG.png
Once your router restarts and you can confirm that you have Internet access, open FG and test your now-successful connection!
Hopefully this helps prevent the frustration I went through!
Dan
Sweet, good job on the clear and concise writeup! Also welcome to the forums and FG community in case somebody hasn't already welcomed you!
This thread needs some clean up. I would suggest possibly a new thread with the opening post being a check list of trouble shooting steps and solutions.
Would anyone be available around 8pm central USA time tonight to go over this setup? We got FG running on another player's computer but it won't work on mine doing the exact same steps.
I am still unable to connect. 127 pages of issues and there still isn't a streamlined way to set this app up?
Hello Aracon,
This normally means that the port forward settings are not set properly on the router. Can you send a screenshot of the FG connection test screen with the local IP address shown and of your router's port forward config screen? You can email it to [email protected]
-Doug
Good evening, everyone. I'm afraid i too need assistance getting this port foward thing working. i am new to FG, but i have been reading this thread and thought i had the correct info for my router....i am wrong. i have a netgear routher and i logged into it to open the port 1802, but i dont think im using the correct ip address? i found 192.168.0.100 but had no luck. i tried 192.168.0.49 also. this is my first adventure into port fowarding and firewalls. Thanks for the assistance.
ive used the internal ip address shown on the FG connection test to open a port on my router. i have reset the router. i went into mcafee to open port 1802. still no luck.
Get ahold of “Damned” he rocks on fixing stuff.
Thank you sir. I will do that.
maratanza please open a cmd prompt and type: tracert 8.8.8.8 and post the results please
Good morning from kentucky, and thank you for the assistance
C:\Users\david>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 74 ms 3 ms 1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 142.254.146.21
3 11 ms 10 ms 11 ms be59.evvninas02h.midwest.rr.com [74.128.6.101]
4 22 ms 21 ms 22 ms be27.lsvmkyzo01r.midwest.rr.com [65.29.30.38]
5 * 33 ms 30 ms be24.clmkohpe01r.midwest.rr.com [65.189.140.162]
6 37 ms 37 ms 40 ms bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68]
7 41 ms 37 ms 38 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
8 35 ms 37 ms 34 ms 0.ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
9 51 ms 38 ms 35 ms ix-ae-27-0.tcore2.CT8-Chicago.as6453.net [64.86.79.97]
10 35 ms 37 ms 34 ms 72.14.219.82
11 * * * Request timed out.
12 37 ms 35 ms 34 ms 216.239.47.219
13 34 ms 38 ms 38 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete
log onto your router 192.168.0.1 and create a Port Forward rule for TCP 1802 to forward to your computers LAN IP (possibly 192.168.0.49? based on your earlier post) on TCP 1802
Make sure that in Windows Network and Sharing Center your network shows Private Network
If you have a screenshot (Alt+Printscreen) of your FG Connection Test screen with your Internal IP address shown and another screenshot of your router's port forward config screen, we can usually spot what you'll need to adjust. You can email those to us at [email protected] or save the images and post them up here as well.
Thanks for the responses. As soon as I get home this evening i'll do everything you guys are asking. I've never even heard of port forward until a couple days ago. I am definitely a dinosaur.