#Port Forwarding Problem...
24 messages · Page 1 of 1 (latest)
There you use Host Routing if i recall
IPv6 Host Exposure*
You can take a Look in IPconfig in cmd
If there is only a Local IPv4 Address then you have IPv6 or DSLite
192.168.x.x or 10.x.x.x.
is there something else?
IPv6 and IPv4 are incompatible
Port Forwarding even if, is done on the Router
show me the cmd window with snipping tool
then i can figure it out
im available
give me 6 min
im there
hmm?
One other thing you could miss is about the firewall on Windows itself. Make sure you open port or program on your computer.
We looked at it
Showed it to him, both on my Computer, and on our Windows Servers. i did not have a Chance to see for myself
I think it may be, that his IP Plan Changed from a IPv4 and IPv6 (Normal DS) to a DSLite one
Which makes it unreachable
My Windows 11 Workstation
Our Windows Server 2012 R2 with Exchange 2013. We have the same Internet Plan on the Whole Network, and there is a External IP. He only has Local IPs as you can see, which makes Forwarding still Possible
But because of Doxxing Scares, he didnt want to show me his Router Interface, which i can understand