Windows 10: I am having difficulty accessing my router configuration with Edge browser and Windows 10

I have seen older posts with this issue but the discussion threads are locked with no real solution, so I am reposting the question.


Initially I was able to access my new Netgear X4S AC2600 router configuration page at 192.168.1.1 via the Edge browser on Windows 10. It would properly bring up a login window and connect to the router.


I noticed that after I changed the Network Profile from 'public' to 'private' under connection properties (attempting to make my PC discoverable on the home network) that Edge would no longer display the login window to allow connection to the router.

Chrome browser allowed access to the router login and configuration page in both 'public' and 'private' Network Profile settings.


Upon changing the Network Profile from 'private' back to 'public' the Edge browser again successfully displayed the router login window and allowed access to the router configuration. I suspect an underlying firewall setting is being automatically changed, but cannot identify the rule/setting that is preventing the login window/access.


Is there a way to enable Edge access to the local router configuration page with a Network Profile setting of 'private'? I certainly have work arounds to configure and manage the router, but the inconsistent behavior is annoying and doesn't reflect well on the products (regardless of whether the issue is Edge, Windows 10, Windows defender or some other component in the Microsoft stack).

:)

 

Configure Wireless Access Point

I have an existing network using a Buffalo N300 wireless router configured as 192.168.11 and 255.255.255

I have recently purchased a Sony Bravia TV with internet capability and would like to connect a second router – the Belkin F5D-8233 – as an access point for the TV. As I already have the router, it is cheaper than me purchasing the Sony wireless dongle.

Essentially, the Buffalo is connected to my PC in one room and provides the internet access. The Belkin would be in another room, connected via Ethernet to the TV.

I have set the Belkin up to use 192.168.11.10 with the same SSID and security settings as the Buffalo. I have also set it up as an Access point.

I have connected the Belkin and the Buffalo together via the Ethernet LAN ports to try and do an initial configuration but I cannot see the Belkin when I do this even though the LAN ports light up.

Can someone give me step by step instructions on how to configure the Belkin so that it gets internet access wirelessly in the other room?

I have been able to confure the TV so that it sees and connects to the Belkin but obviously this is of little use unless it can connect to the internet through that connection.

Thanks, any help appreciated.

 

Unable to access my router

1. I already have a gateway configured in my house, so no, i'm not relying on this router for internet. However, I plan to make this into an access point in the very near future.

2.This is what I'm getting when i follow that step....

Autoconfiguration IPv4 Address. . : 169.254.205.6(Preferred
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

So with this i tried 169.254.205.1 with unlucky results :/

 

Microsoft is developing a built-in ad blocker for its Edge browser

"One of the first browser add-ons many people install to improve their online experience is Adblock Plus or something similar. Until recently, Microsoft Edge's lack of support for add-ons put off a lot of would-be users, but reports from Build 2016 suggest that native ad blocking is on its way to the Internet Explorer successor.

Adblock Plus is coming to Edge, but built-in ad blocking would negate the need for such an add-on. A slide shown off and snapped at a Build presentation shows that the next version of Edge, in response to user feedback, will feature ad blocking capabilities. There's no word on delivery timescale, but the upcoming Windows 10 Anniversary Update would seem a likely candidate.

ZDNet's Ed Bott photographed the slide which shows Microsoft's development roadmap built around feedback from testers. Right at the top of the list is reference to plans to create a plugin and extension store for Edge, but it's entry number four that's more intriguing.

"Build ad blocking features into the browser" is listed as a Feature Request from users. But the good news is that it is not only listed as being "Deliverable 4682811", but as "Targeted for the next version".

This will no doubt come as good news for those who have fallen in love with Edge, but it's not something that will be welcomed by the likes of Adblock Plus. It does seem that, particularly in the mobile arena, there is a move to baking ad blocking into the browser so it makes sense that Microsoft is following the trend. But it is the fact that Edge straddles Windows 10 on the desktop and Windows 10 Mobile that makes this a particularly interesting move.

Keep an eye out for Insider builds in the coming weeks as the feature may be just around the corner."

Forget extensions, built-in ad blocking is coming to Microsoft Edge - [UPDATE... no it's not!]