Connect Neutral Router TP-LINK WR1043ND

[pestanin]

Hello everyone.

I just received the router in question and although the operation was supposed to be as easy as connecting my current Zyxel P660HW-61 to the WAN connection of the neutral one and then proceed to configure both, it is not turning out that way. In fact, I have not been able to even start because the WAN light does not turn on which means it is not picking it up and I cannot access the TP-LINK configuration in any way.

I follow these simple steps:

1º We connect an ethernet cable from the modem to the blue RJ45 connector on the back of the TP-Link router. 2º We connect another ethernet cable from any of the yellow RJ45 connectors on the back of the TP-Link router to the network card of our PC. Set the network card configuration on the PC to acquire IP and DNS automatically. 3º Connect the power connector from the router's power supply to the socket on the back of the device marked with the word POWER. 4º After about 2 minutes and with the computer connected, open the Internet browser and type 192.168.1.1, a dialog box will appear asking for the username = admin and password = admin (this information is found on the label at the bottom of the router), press Enter on our keyboard and… we are already in the router's status menu (status).

and what happens to me is that it stays identifying the network until it gives an error.

I am sure it is something trivial but with the denial I spend on networks who knows :facepalm:.

I have also read what is recommended on adslzone but as I say, since I have never been able to access the neutral router there is no way to follow instructions.

Thank you very much.

Best regards.

[Fassou]

Set up the neutral router without connecting it to the Zyxel, they won't have the same default network range and will be fighting

Salu2!

[pestanin]

I've managed to get into the Tp-Link settings but no matter what I put, it doesn't "connect" with the Zyxel in any way. I've tried connecting the WAN connector of the neutral to the LAN of the Zyxel and from LAN to LAN and there's no way. In theory, one of these should work but it doesn't for me :wall:

Actually there are three ways to connect:

1st ADSL router acting as a router with its local network 192.168.1.XXX and neutral router connected its WAN to a LAN port of the ADSL router creating another local network. In this case the IP of the neutral router should be 192.168.2.1 and its network would be 192.168.2.xxx.

2nd ADSL router acting only as a modem so that nothing can be connected to it other than the neutral router. In this case the neutral router would do the PPPoE. The IP of the neutral router should also be 192.168.2.1.

3rd ADSL router acting as a router and neutral router acting as a switch. In this case the neutral router is given an IP 192.168.1.254 and DHCP is deactivated but it no longer connects through the WAN port but through a LAN port. In this case it doesn't matter how the WAN is configured.

And then the guy says that

I put the ADSL as a modem, without connecting anything else, I changed the IP of the neutral one and …tachannnnnnnnnnnnnn..........at the first try

no idea what that is… In the Zyxel I don't see that ADSL as a modem only.

Best regards.

[kynes]

The zyxel as a modem has two ways, one is bridge mode, which in adslzone you should have several threads where it explains it, and another is to open all ports to the tplink. I have some hand with the people of redeszone, in case you want me to tell them something.

PS: Anyway, if you had bought a TRENDnet, you wouldn't have that problem, you would have me here to bother me until it was resolved :troll:

[Fassou]

When you look back at the first post, by default both routers come configured in 192.168.1.1 so they won't work together until one of them changes the network.

This is when you have to decide if you want the router and WAN firewall function to be performed by the Zyxel or the new TP-LINK.

The difference lies in whether you believe that the new router will be able to handle everything and you configure the Zyxel as a modem, or if you prefer that it is the Zyxel that filters and protects you from external access, because you already take care of the neutral one yourself ;D

Salu2!

PD: If what you want is for it to work NOW! and leave the rest for later, connect to the Zyxel, change the DHCP server network range to any other, save and connect a cable from its LAN to the WAN of the TP-LINK. After a few seconds connect your equipment to the TP-LINK and it should work.

[pestanin]

@kynes:

The zyxel as a modem has two ways, one is bridge mode, which in adslzone you should have several threads where it is explained, and another is to open all ports to the tplink. I have some hand with the people of redeszone, in case you want me to tell them something.

PS: Anyway, if you had bought a TRENDnet, I wouldn't have to go through that, you would have me here to bother me until it was resolved :troll:

I know, I know… Knowing the good that is known... I'm going to try to get it out and see if tomorrow with more time I get enlightened.

Fassou, at first it seemed more logical to use the Tp-Link as the "final" router because it is better, more modern, etc... but I'm not sure either. What I do see is that it doesn't work doing that. I change the range, connect to the Tp-Link and there's no signal. The WAN light doesn't even turn on. Could it be because I removed the DHCP function before? Tomorrow I have the afternoon free, I'll review configurations because I don't even know how I left it after touching it so much today.

Thanks.

Best regards.

[Fassou]

You have to leave DHCP activated on both, but on the Zyxel you change the range (you can set, for example, 10.0.0.1 / 255.255.255.0).

Regards!

[pestanin]

Good afternoon.

There is no your aunt. If I put any range outside the typical 192.168…. it tells me that it is not valid as a starting limit and I cannot change it. Here is a picture with the fields because then there is another section called Static DHCP to enter Mac Adress and IP but that is not true? By the way, the tp.link did have DHCP activated so it should not be that <:(.

I am going to keep trying in the meantime with the Zyxel in modem mode only.

Best regards.

[Fassou]

You may need to change the IP of the router first, before the DHCP service as a protective measure so that you do not put different ranges.

Anyway, if you are determined that the TP-Link will handle everything, it is better to put Bridge+PPPoA on the Zyxel and that's it.

Goodbye!

P.D.: the cable between both routers I assume is 100% reliable, right?

[pestanin]

If I grab the males that I have... Let's see if I understand.

The idea is to have the Zyxel connected to the PC via the RJ45 of all time (or WIFI will be the same) and then enter its configuration and select bridge mode + PPPoA. I restart, save changes etc... and then connect this to the Tp-Link via LAN Zyxel - WAN Tp-Link which should be plugged into the PC also via RJ45 right? Ultimately which one should be connected to the PC?

The cables are requetecomprobados (it's the only thing I can do with some reliability :facepalm:)

Best regards.

[Fassou]

When you have the Zyxel configured (turn off the WiFi by the way), you leave both routers off and without a cable connection.

You start the Zyxel and let it synchronize, then you connect the computer to the TP-Link and finish configuring it if it wasn't, and finally, you connect a LAN port of the Zyxel to the WAN of the TP-Link.

By entering the TP-Link you should be able to see how on its WAN side it has taken the public IP that the Zyxel has passed on, which acts as a modem.

Goodbye!

[psgonza]

Hello

I have done the same thing, but with a SAGEM (1500 something, an old Wanadoo used as a modem) and a linksys WRTxx… It took me a while but in the end I got it to work.

I don't know if you have already done this, but just in case it is of any use to you, on the device that is going to act as a modem, you do not configure the PPOA or anything like that, only the atm with its vci and things like that. The neutral router that goes behind the modem is the one that should take care of the authentication.

Regards

[pestanin]

In the end I didn't stop and I couldn't look at anything. This afternoon I try a little bit of everything although the other day I put the Zyxel in Bridge + PPPoA mode and besides not working with the Tp-Link it cost me an egg to be able to access it again to change it. The Zyxel didn't synchronize and I had to do a blind reset :wall:.

psgonza, then I would leave the Zyxel with its configuration as I have it now? This way there has been no way.

Thanks.

[Fassou]

Your ISP is Timofónica, right?

Salu2!

[pestanin]

So is that it? Any problems with these gentlemen and the apparatus?

[Fassou]

So you got it to work on monopuesto (Bridge), but not the TP-Link right?

Salu2!

PD: The PPPoA issue is only when the ISP is Telefónica ;D

[psgonza]

@pestanin:

In the end, I didn't stop over the weekend and I couldn't look at anything. This afternoon I tried a little bit of everything, although the other day I put the Zyxel in Bridge + PPPoA mode and, in addition to not working with the Tp-Link, it cost me an egg to be able to access it again to change it. The Zyxel didn't synchronize and I had to do a blind reset :wall:.

psgonza, so should I leave the Zyxel with its configuration as I have it now? This way there has been no way.

Thanks.

I'm not at home yet, I'll see if tomorrow morning I can look at it and tell you how I put it, in case it works for you.

[pestanin]

Oh well, oh well!. If I put the Zyxel in Bridge mode it goes crazy, stops syncing and as it doesn't "link" with the Tp-link I lose internet and the will to live.

If I do the operation```
Start the Zyxel and let it sync, then connect the computer to the TP-Link and finish setting it up if it wasn't, and finally, connect a LAN port of the Zyxel to the WAN of the TP-Link.

Going into the TP-Link you should be able to see how on its WAN side it has taken the public IP that the Zyxel has passed to it, acting as a modem.

it doesn't even turn on the WAN light on the Tp-Link and obviously doesn't get the IP that the Zyxel passes to it if it passes anything… To do this operation do they have to be both with DHCP activated or just the Tp-Link? How should the IPs be? Right now the Zyxel is in the range 192.168.1.1 and the Tp-Link in 192.168.2.1. I've also tried the trick from [http://www.adslzone.net/postx196025-0-15.html](http://www.adslzone.net/postx196025-0-15.html)``` That the IP of the Zyxel is 192.168.1.1 (its gateway).    That the IP of the Conceptronic is 192.168.0.1 (its gateway).    That the WAN of the Conceptronic is in Dynamic IP (to get an IP automatically through the WAN).    That on the WEB of the Conceptronic on the HOME screen, in the WAN section, in the Connection type line it says DHCP.    If all that is like that connect the ethernet and telephone cables, then power the Zyxel first, then the Conceptronic and then the computer.

and neither.

[pestanin]

I'm going to try http://www.adslzone.net/postp2033032.html

I have accessed the TP-LINK with the network cable connected to my pc   I have changed the IP to the following... 192.168.1.2   I have deactivated the DHCP   Activated the Wireless on the TP-LINK    I have changed the network cable from my pc to the Zyxel, since after these changes on the TP-LINK I did not have internet access   I have deactivated the Wi-Fi of the Zyxel from the Portal Alejandra to leave this job to the TP-LINK and everything is (in principle) configured, I have the Wi-Fi through the TP-LINK and Imagenio working. 

and I'll tell you…

[pestanin]

Well, zero dollars. So there is no WIFI connection on the Tp-Link in any way and in theory it is exactly the same case (although there is no image here but the Zyxel is the same). More tomorrow.