3) the last part of that address being "135". Those addresses are usually assigned automatically, and the DNS usually just counts up, so that would be 135 devices connected in your local network, which seems a bit excessive.
The MTU part below just indicates that you have no internet connection - the frontier servers simply can't reach your PC at 192.168.x.x. Question: are you on a company/private network, or a VPN? In the former case, you'd need to talk to your network admins - nothing FD or we here can do about that (ok, I can't - and those who do would be well advised not to state that publically, as that could more than slightly illegal). In the latter case, you may need to disable/bypass/tunnel that VPN for ED. FD support might be able to help you with that, but you'd probably have better chances in talking to your VPN tech support, or maybe both.
3): This is entirely plausible without being disturbing. Most routers allow you to specify an IP address range for DHCP to hand out. This allows you do a couple of things including limiting the number of devices that can connect to your LAN. This means that private IP addresses don't necessarily begin at 192.168.x.
1.
...and I believe that you meant to say
DHCP rather than
DNS. Domain name servers don't assign IP addresses to devices on your local network, that's DHCP's job. Apologies if I misunderstood your intent.
Numerous possibilities, of course. The advice to investigate settings if you are using a VPN is certainly among them. Much of that is outside my knowledge; I simply haven't fiddled with VPNs yet.
--------------------------------------------------
OP: your initial post doesn't reveal much about your network (this is wise!). This makes it more difficult for us to suggest tactics that could lead to a solution, or to suggest ones that make sense in your situation. We also don't know your skill level.
One more that I can offer:
If your gateway/modem includes a router (many do), it should be safe to temporarily plug your PC into one of the LAN ports (it should still be protected behind the gateway/modem's NAT and firewall). This test would allow you to narrow-down the location of your problem to either "your" part of your home network or the ISP/gateway/modem. Keep in mind that it may not be as simple as just moving your network cable from your router to the gateway/modem. If you are indeed using a VPN, you may have to modify/simplify settings associated with that (temporarily go without the VPN if possible). If this isn't possible, I think you should start talking to the person who set up your VPN/network, etc.
My apologies if this suggestion ignores the fact that you're using WiFi to connect your PC. That means you'll either have to find a cable or now configure the WiFi included on your gateway/modem.
Keep us up to date,
@rel04de. It helps us too - and we just want to get you playing with your friends again.
