It could be a newer UPnP version that isnt being read properly by your Router?
Printable View
It could be a newer UPnP version that isnt being read properly by your Router?
It sure could. I did verify latest firmware on the router (WZR-1166DHP Version 2.13) but didn't troubleshoot beyond this point. I knew I was on thin ice when I noticed the router version date was well before Windows 10.
Check this setting: https://www.computerhope.com/issues/ch001367.htm
Need some help accessing port 1802 & connecting to the FG server to host a game. I am not a hardware person at all, but do well with RTFM for most GUI software. I have created rules in my firewall that should allow 1802 to work. That was relatively easy. Completely stumped at this point. Any help would be appreciated.
sent you a PM.
You don't actually connect to a FG server provided by SmiteWorks - the GM Fantasy Grounds instance is the server running on your computer. Have you logged into your internet router and setup port forwarding to your GM computer IP address? What tests are you doing?Quote:
Originally Posted by tadkil
Yeah... non-technical kind of guy. Turned off my firewall and still could not connect. May need to remote in some IT support.Quote:
Originally Posted by Trenloe
Brilliant help. Damned is awesome.
Trying to setup fantasy grounds on new Surface Pro 4 running windows 10. I have a Netgear C6300 cable modem/wireless gateway. I set up the DHCP server on the gateway to always give the surface the same IP address. Then I set up port forwarding for port 1802 (external and internal) to the IP address of the Surface (which I have confirmed matches the address I input in the C6300 port fwding table). I first tried to create a path through windows Firewall by adding an inbound rule to allow FantasyGrounds to receive incoming TCP traffic from any port. Didn't work. So I tried to be more specific and created inbound rule to allow FG to receive incoming TCP from 1802. Didn't work. I created a rule to allow any program to accept TCP on port 1802. That didn't work. So I disabled Windows Firewall altogether and my connection test still failed. In a different thread I saw the netstat -a - p tcp command to check to see if the surface was listening on port 1802. It is not, even with Firewall disabled. Any ideas what might be causing the communication breakdown or how to correct it?
Oh I also tried disabling ipv6 on my network adapter and giving the surface a static ipv4 address (with appropriate subnet mask and DNS servers). That didn't seem to help either and it made my internet access a bit dodgy so currently relying on modem to always give the surface the same IP through DHCP.
heya warwick!
it looks like you are (were!) going about things the right way.
lets roll back to your initial setup -
router gives surface same ip each time = good
port forward tcp 1802 on router to surface = good
create windows firewall rule on surface to allow tcp 1802 from ANYWHERE = good
stop there
now on surface what does FG tell you the External IP address is?
on the router what does it think the WAN/Public/External IP address is?
open a cmd prompt and type:
tracert 8.8.8.8
can you post the first 4 hops?
send me a PM if you like.