Thread: FG Knowledge Base - Firewalls
-
November 16th, 2017, 02:16 #271
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
-
February 21st, 2018, 01:27 #272
- Join Date
- Feb 2018
- Location
- Kentucky
- Posts
- 6
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.
-
February 21st, 2018, 02:11 #273
- Join Date
- Feb 2018
- Location
- Kentucky
- Posts
- 6
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.
-
February 21st, 2018, 02:31 #274
- Join Date
- Feb 2010
- Posts
- 83
Get ahold of “Damned” he rocks on fixing stuff.
-
February 21st, 2018, 03:02 #275
- Join Date
- Feb 2018
- Location
- Kentucky
- Posts
- 6
Thank you sir. I will do that.
-
February 21st, 2018, 12:39 #276
maratanza please open a cmd prompt and type: tracert 8.8.8.8 and post the results please
-
February 21st, 2018, 13:01 #277
- Join Date
- Feb 2018
- Location
- Kentucky
- Posts
- 6
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
-
February 21st, 2018, 13:24 #278
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
-
February 21st, 2018, 14:20 #279
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.
-
February 21st, 2018, 14:44 #280
- Join Date
- Feb 2018
- Location
- Kentucky
- Posts
- 6
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.
Thread Information
Users Browsing this Thread
There are currently 2 users browsing this thread. (0 members and 2 guests)
Bookmarks