Printable View
Yeah, understood. That's why I mentioned the bit torrent example since that's the other one where I had to do port forwarding but it was successful. Team Speak can do hosting as well but I've only been doing client. Maybe I need to look into it and try there as well. Just a head scratcher is all.Quote:
Originally Posted by LordEntrails
If you have been messing with a lot of stuff you may have too many things happening and they are interfering with one another. You may need to revert everything back tto where you started and then redo them one at a time and test your connection after each one.Quote:
Originally Posted by Galbraith Telmor
You could screenshot your Port Forward rule and your exception in your antivirus for us. It's difficult to diagnose an issue blindly.
Yeah - ran into this last night, took an hour to realize they've deployed an Intrusion Detection/Prevention solutions (IDS/IPS), as damned indicated. More info on it here. They really could have advertised it more...Quote:
Originally Posted by damned
I've left myself a "Sticky" on my windows 10 desktop to remind me to disable it prior to the night's session, and I'll re-enable it after.
Completely disabling it doesn't make much sense. The days of unsolicited inbound session requests went out in the 90s, and given the fact our home routers aren't well cared for with a Secure Software Development LifeCycle let alone a decent, long-term, firmware patching schedule - it's a decent service. Highly recommend it, particularly if you haven't worked in a SOC (Security Operations Center) and know your Cyber OpSec cold.
Here is the exception in Avast:
Attachment 31610
Here is the Port Forwarding on the router:
Attachment 31611
Here is the assignment of that forward to my static IP machine:
Attachment 31612
And then the Windows Firewall settings:
Attachment 31613
Attachment 31614
Continued since I could only post 5 images at a time.
Then I also set the port-specific rules too when the other didn't work:
Attachment 31615
Attachment 31616
I should also mention that, as I was taking these screenshots, I disabled windows firewall as well as Avast long enough to try to connect again. Still not successful. That makes me think it has to be something with the router/ISP but obviously that's just a guess on my part. I really have no clue. :(
I’m not an expert but I’m not sure if you need to change anything in Windows. Avast should take over the Windows firewall and setting an exception there should be enough. I’m not familiar with that router so I can’t say whether that rule makes sense or not to be honest. My feeling is you have too many things changed and they are getting in each other’s way. But that’s just a guess really.
Galbraith Telmor if you would like me to logon with you later on and go thru everything with you send me yuor email via PM and we will organise something.
1. LAN: 192.168.0.10
2. WAN: 160.2.xxx.x
3. Wired Connection
4. Connection is set to private.
5. Using ESET with exception set for the port with the program attached to the port.
6. 1 <1 ms 1 ms <1 ms 192.168.0.1
2 15 ms 16 ms 11 ms 10.117.59.1
3 15 ms 14 ms 13 ms 192.168.87.65
4 27 ms 30 ms 28 ms 10.224.252.217
5 28 ms 28 ms 26 ms 74.125.147.132
6 30 ms 29 ms 28 ms 108.170.240.193
7 28 ms 30 ms 26 ms 216.239.35.161
8 30 ms 28 ms 29 ms dns.google [8.8.8.8]
7. Router is an Arris TG862, I have set up a virtual server and port trigger.
Welcome BearOnATricycle
If FG shows the WAN of 160.2.something and that matches what the Arris shows as its Internet or WAN IP then this might work.
Otherwise you are going through a number of additional NAT stages and you will need to look at the Port Forwarding Alternatives thread.
FG shows my external to be the same as the Arris ip