@Raikke 

Raikke wrote

Win 10 not connect router maintenance, everything works fine ok.
Only the management page cannot be accessed on the win10 pro machine.
Was it some SMB thing?
No help either, tried to change.

What is the URL you were using with what Browser or was it a phone/tablet app?

What did you see when you tried or was there an error?

Can other devices connect to the GUI?

SMB would only come into play with Network Sharing. SMB1 has to be enabled to do that, not an issue to connect with a browser to the router GUI.

Open a CMD prompt and enter 'ipconfig /all' (without the 's). Then use the DEFAULT GATEWAY IP address as the URL of the active network adapter (one that doesn't show Media Disconnected). Usually 192.168.0.1 or 192.168.1.1. That should work.

This assumes you are on the same network as the router. If you are connected wirelessly it is possible you are connected to the Modem/router, not the router. That of course would be why you couldn't connect.

@IrvSp 
Can other devices be connected to the graphical user interface?

 All XP and Win7 machines on my LAN connect ok.


SMB should only play with network sharing. SMB1 must be on
and does not need to connect to the browser with the router interface.

Alright.

Open the CMD prompt and type 'ipconfig / all'.
Then use the DEFAULT GATEWAY IP as the URL of the active web adapter
(one that doesn't look like Media Truncated). Usually 192.168.0.1 or 192.168.1.1. It should work.

This is done, the screen is blank on the WIN10 machine, but the connection is established.


Unfortunately, the type of device I never remembered before.
However, the device is a CPE-510 v1.0 router with PHAROS drive
Works with its counterpart 100% in every way.
Only control can not be achieved with WIN10 machines, several tried and tested.
that is, 100 failures on WIN10 machines!

@Raikke 

Which is the one with the problem? You mentioned two, first an Archer C5400 on the first post and now CPE-510 v1.0 router with PHAROS drive?

Wondering if the device that work are connected to the CPE-510?

The 2 routers will have different IP Addresses.

Can the W10 PC's connect to the GUI on either router?

@IrvSp  Which one has the problem? Did you mention two, first on the Archer C5400 in the first post and now on the CPE-510 v1.0 router on the PHAROS drive?

There is a problem with the CPE-510, 192.168.0.120
 

Wondering if a working device is connected to the CPE-510?

All devices are functional on the intranet.
But the CPE-510 does NOT work on WIN10 powered devices.

All routers have different IP addresses.

C5400 is 192.168.0.1
CPE-510 is 192.168.0.120

Can the W10 connect both routers to the graphical user interface?

C5400; WIN10 hardly connects, about every 4-5 refreshments from the browser.

The CPE-510 does not connect to WIN10 machines. Only on XP and WIN7 machines does the GUI appear.

@Raikke 

So does anyone use that CPE-510 with a Windows 10 pro?
Would it be important to get confirmation that this device really works with WIN10?

@IrvSp Not answer any ?????

@Raikke 

Raikke wrote

@IrvSp Not answer any ?????

Well, for one I don't work for TP-Link and just was curious?

Some answers confused me as well?

" But the CPE-510 does NOT work on WIN10 powered devices. "

Not exactly sure what you meant here? 'NOT work' is the problem, I don't know what happened or what was used and how? Do you mean using that as the Gateway for the W10 PC or connecting to its Wifi or trying to access the GUI?

This clarified it some?

" All routers have different IP addresses.

C5400 is 192.168.0.1
CPE-510 is 192.168.0.120

Can the W10 connect both routers to the graphical user interface?

C5400; WIN10 hardly connects, about every 4-5 refreshments from the browser.

The CPE-510 does not connect to WIN10 machines. Only on XP and WIN7 machines does the GUI appear. "

So you really can't connect to the GUI on either router, at least consistently. Is this one W10 PC or do you have more than one with the problem?

On the W10 PC, open a CMD prompt and run IPCONFIG, and find the active adapter and it should look like this:

Wireless LAN adapter Wi-Fi 2:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::fcec:270d:64fc:ed23%22
   IPv4 Address. . . . . . . . . . . : 192.168.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

What does your's look like? I am connected to my only router. That shows in the Default Gateway.

Can you PING both 192.168.0.1 and 192.168.0.120?

As for 'hardly connects', have you cleared the Browser Cache?

Have you tried another browser? W10 has both IE and Edge on it. Firefox or Chrome would be another to try? I've got an A20 router and ONLY Chrome can open the GUI with a saved set of userID and Password. all others I need to manually enter those to  get into the GUI. You problem might just be a cache hold old data or a browser problem.

@IrvSp 

No WIN10 machine can display the GUI on the CPE-510.

WIN10 connects to all possible browsers, but the GUI does not appear.

On Win 7 and XP machines, the GUI comes up correctly.

There is a problem with the WIN10 operating system, but what is the problem?

Benches, ipconfigs, etc. are 100% okay. Only on WIN10 machines, many, GUI does not appear!

@Raikke 

If you really think it is OS related, then I'd think it could be your Security... Windows Defender couldn't/wouldn't possibly be the cause. However another Security Suite you are running could be. The IP Address is NOT part of the Trusted IP Address list?

You didn't post the Gateway Default IP Address from IPCONFIG, what is it?

If you do a NETVIEW from a W10 PC, do you see other PC's and the Router if you have a USB drive connected?

It wouldn't appear to be the router though if other PC's not running W10 work fine, might want to post in a W10 forum?

@IrvSp  ipconfig:
default gateway: 192.168.0.1

that has nothing to do with it because the internet works from anywhere on the intranet.

I can't access the CPE-510 wifi link from any WIN10 machine.
Behind the link are machines that can access the web ok.
Likewise, the link provides access to the CPE-510 for XP and WIN7, not for WIN10.

WIN10 machines cannot access any part of the intranet to the CPE-510 GUI.

Only this is the problem.
Otherwise, the whole intranet works ok.

The internal network has 18 machines.
There are 6 machines behind the CPE-510 link.
The CPE-510's address is 192.168.0.120, here at the office end.

In the annexe, the address opposite to the CPE-510 is 192.168.0.125
XP and WIN7 computers have access to those GUI management pages from anywhere.

I want access to the office to get to win10 from the machine I work on.

I apologize for the fact that this is a translation from Google's translation machine, we can't do better ...;)