PDA

View Full Version : Could use some help connecting



Elfazar
March 14th, 2019, 23:06
Hello

I have been uable to connect the last 2 days using the Connection test Run Test. I have been able to in the past, which lead me to believe that it is because i have not set a static IP address.. So i went back in and changed the ipv6, (and reconfirmed the ipv4) address was correct. However i still run into a failure. The Canyouseeme website says it cannot see my port 1802 yet however. As well as continuing failed tests. I would like to solve this without using Hamachi as had been suggested.I evern went as fire as uninstalling my anti virus software and disabling windows firewall. And i can confrim my network is still set to private. I am on Win10

Elfazar
March 14th, 2019, 23:14
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 10.0.0.1
2 16 ms 18 ms 12 ms 96.120.100.249
3 14 ms 14 ms 13 ms po-109-rur02.tumwater.wa.seattle.comcast.net [68.87.206.13]
4 18 ms 21 ms 17 ms be-44-ar01.seattle.wa.seattle.comcast.net [69.139.164.22]
5 22 ms 19 ms 17 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
6 17 ms 25 ms 16 ms be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]
7 19 ms 16 ms 16 ms 50.242.150.26
8 * * * Request timed out.
9 18 ms 16 ms 17 ms 209.85.254.236
10 20 ms 17 ms 17 ms 74.125.243.195
11 18 ms 29 ms 17 ms 72.14.236.174
12 26 ms 25 ms 25 ms 216.239.46.208
13 25 ms 26 ms 25 ms 64.233.174.131
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 25 ms 25 ms 21 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Zacchaeus
March 14th, 2019, 23:30
Make sure that your network is set to private and that you have a rule excepting FG in your antivirus.

I’m not sure waphat you mean about the setting of the port forward rule. It doesn’t look from your tracert that you should have any issues with your ISP sharing addresses or anything. Can you screenshot your rulle.

Also you are the host right?

Elfazar
March 14th, 2019, 23:33
Canyouseeme is a website that verifies if you have a port open. I will post a screen shot

Elfazar
March 14th, 2019, 23:36
This is my port forwarding rule26718

Elfazar
March 14th, 2019, 23:38
The Ipv4 addres i used was the one that shows up as "Internal" within the fantasy grounds app, and the ipv6 address is the one from my ipconfig /all listed under "Wireless LAN adapter Wi-Fi:" I do not use an ethernet connection. it is also followed by the words (Preferred)"

Elfazar
March 14th, 2019, 23:39
I have made sure my network is set to private. And i have put an exception to my firewall for port 1802. I have gone as far as actually disabling my firewall and trying to connect

Zacchaeus
March 14th, 2019, 23:44
I would remove the IPv6 thing. And the exception in your AV should be for Fantasy Grounds not Port 1802. Make sure there aren’t multiple rules if you are using Windows Defender. If there are delete them all and create a new one.

Elfazar
March 14th, 2019, 23:51
So just leave the ipv6 field blank?

Elfazar
March 14th, 2019, 23:53
26721 This is what it looks like now, continuing failure

Zacchaeus
March 15th, 2019, 00:06
So in the past you had to set port forwarding? Because all you should have needed to do was change the computer that the rule was pointing to. If you didn’t need to port forward before then assuming nothing has changed you shouldn’t have to now. It may be all you needed to do was reboot your router. If FG cnnected fine before then either the network has been set to public, your anti virus has had some change of heart or your computer’s IP address has changed and your Port Forwarding rule needs updated.

If you didn’t need to port forward before I wouldn’t mess with that now.

Elfazar
March 15th, 2019, 01:21
I did have it pit forwarded before also.i have now u I stalled all antivirus software so it isnt that. My network is still on private. Just confirmed

LordEntrails
March 15th, 2019, 01:32
Verify your internal IPv4 address. You rule has is set to 10.0.0.60 but I don't think your ping showed the same did it? I believe the command is netstat

Elfazar
March 15th, 2019, 02:27
Within fantasy grounds it says 10.0.0.60. Netstat says the same

LordEntrails
March 15th, 2019, 03:41
Sounds like you have done everything right...
Sometimes people have reported that they have to do a few things, if you haven't, try these and test after each one:
- reboot your router
- delete your port forwarding rule and recreate it
- delete any firewall and/or anti-virus exceptions and recreate them

There are a couple of network gurus who can give better info than me and may even be able to walk through things one at a time with you. Hopefully one will stop by soon and point out what we are missing.

Elfazar
March 15th, 2019, 04:18
Fixed

Not really sure what the underlying issue was but i did what you said. Deleted the port forwarding rule. Unplugged my Router, and turned off my firewall for private networks connections. Seems to work fine now, thank you all for the help so much

LordEntrails
March 15th, 2019, 05:18
Fixed

Not really sure what the underlying issue was but i did what you said. Deleted the port forwarding rule. Unplugged my Router, and turned off my firewall for private networks connections. Seems to work fine now, thank you all for the help so much
Yeah! Glad it worked, I felt bad you were struggling with it so much.