Master router and new slave router lags

Toggle sidebar Toggle sidebar
A

Asiel

Honorable
Aug 27, 2012
47
0
10,530
Master router is Asus RT-N12C1. IP is 192.168.1.1 with DHCP turned on
Slave router is Tp-link TL-WR841N (This is a new router replacing the old dead slave router) IP for slave router is 192.168.1.2 with DHCP turned off. Admin name password have been changed, and firewall for this router has been turned off. Wireless function is also turned off, as it is not needed.


Problem Summary:

- Network computers not always detected
- Wireless computer now asking for a password (not always) only when it feels like it...
- Sometimes get "Not accessible" message, only for wireless pc

Network environment:

Network cables used are identical, as it's just the router that was changed.
Windows XP and Windows 7 mix (No issues experienced with old slave router).


Description of problem:

The new slave router (Tp-link TL-WR841N) is not working as well as the old slave router.
When attempting to access other network computers, there is a lag of at least 3 seconds, sometimes a little more. At times, the other computers aren't even detected on the network.
For some reason, when attempting to access the wireless pc over the network (shared folders) a user name and password prompt pops up. There were never any passwords setup to access the network or any folders on the network, not sure why that's happening.

The old router had no issues at all. It was fast to open network folders and access the network. There were never any password prompts, as expected, since no password was setup.

Could this slave router (Tp-link TL-WR841N) have a setting which is causing lag or a communication issue?

Thanks for looking and any advice.


 
Solution
H
I agree with the others. This is a case of using the wrong tool for the job. You're asking a router to act as a switch. If I were you, I would make that router be an actual router since that is what you're working with.

I checked out the manual for the TP-Link router and found out it supports static routes. Pages 70 through 72:

http://www.tp-link.com/resources/document/TL-WR841ND_V9_User_Guide_1910010905.pdf

I would connect your ASUS to your TP-Link on the TP-Link's WAN port and enable static routes. You'll have to have each LAN of each router be on a different network, and have the WAN of the TP-Link be on the same network as the ASUS LAN. Then you have each router point to the other for their LAN networks. And you'll have to...
Sort by date Sort by votes
T

thently

Distinguished
May 10, 2007
1,982
7
20,465
Ok few quick questions... Why do you need a "slave router"? Also does the network go into your slave router using the wan port or one of the 4 lan ports. You will want to use just the lan ports if this is not an external internet facing router.

Thent
 
Upvote 0 Downvote
J

jfreggie2

Honorable
Sep 16, 2013
150
0
10,760
The cable from you mater router to your slave router should be plugged into one of the switchports, not the WAN port, and I believe it should also be a crossover cable as well.... also... since you're not using any of the services provided by a router... you could just use a switch instead.
 
Upvote 0 Downvote
InvalidError

InvalidError

Titan
Moderator
May 18, 2007
23,815
5,265
108,890

Practically all remotely recent switches, routers and Ethernet MACs have auto-MDI detection which automatically configures the port for straight or cross-over as needed. With 1GBase-T which uses all four pairs in both directions, cross-over is completely pointless.

As for using a router as a switch, I agree, completely silly to buy a router but only use it as a simple switch... not even using it as a range extender for WiFi.
 
Upvote 0 Downvote
H

humangod

Reputable
Jun 17, 2014
63
0
4,660
I agree with the others. This is a case of using the wrong tool for the job. You're asking a router to act as a switch. If I were you, I would make that router be an actual router since that is what you're working with.

I checked out the manual for the TP-Link router and found out it supports static routes. Pages 70 through 72:

http://www.tp-link.com/resources/document/TL-WR841ND_V9_User_Guide_1910010905.pdf

I would connect your ASUS to your TP-Link on the TP-Link's WAN port and enable static routes. You'll have to have each LAN of each router be on a different network, and have the WAN of the TP-Link be on the same network as the ASUS LAN. Then you have each router point to the other for their LAN networks. And you'll have to include a default route on the TP-Link that point back to the ASUS router. Welcome to routing 101.

In order for my suggestion to work, your ASUS router will have to also support static routes AND you'll have to have a basic understanding of how routing works. Otherwise, you'll just hose your network and you'll have to reset both routers back to factory and start all over.

Otherwise, go buy a switch and stop using your router to do things it wasn't meant to do.
 
Upvote 0 Downvote
Solution
InvalidError

InvalidError

Titan
Moderator
May 18, 2007
23,815
5,265
108,890

Routers work fine as switches since all they really are is a SoC running routing software connected to a 5-6 ports unmanaged Ethernet switch ASIC... switches with routing features tacked on via a SoC connected to the monolithic switch's (G)MII port.

Routers as switches do cost $50-100 more and waste 5-10W extra power though.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom