WDS connection problem

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

WDS connection problem

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
WDS connection problem
WDS connection problem
2014-06-30 05:50:42
Region : Argentina

Model : TL-WR1043ND

Hardware Version : V1

Firmware Version : 3.12.25 Build 130322 Rel.33803n

ISP :


Hello,
I'm having a poblem with WDS connection with my router.
I did the settings to connect the router to one D-link, the WDS status is RUN.
I can access the TP-Link menu and ping the 192.168.0.2 via the D-link router and vice versa (access and ping 192.168.0.1 via TP-Link), but there is no internet when connected to the TP-Link.
Here is the set up:
Primary router connected to internet: D-link, IP 192.168.0.1;
Secondary router connected to the primary router via WDS: TP-Link, IP 192.168.0.2
WDS Status: Run
DHCP Server: Disabled
Channel: 10, like the D-link.

All seems fine but no internet.
Any ideas are welcome.
  0      
  0      
#1
Options
5 Reply
Re:WDS connection problem
2014-06-30 19:45:29
Hi,

Check if gateway and DNS parameters are set to 192.168.0.1 !
  1  
  1  
#2
Options
Re:WDS connection problem
2014-07-02 04:26:55
Hello HiSpeed,
Do you meadn this setting to the secomdary router (IP 192.168.0.2)?
it seems that this will not help because the gateway and dns are under DHCP settings which has to b disabled to the secondary router.



  0  
  0  
#3
Options
Re:WDS connection problem
2014-07-02 17:23:15
Please insert DNS addresses in network card, for example 8.8.8.8 and 8.8.4.4 and then check internet access
  0  
  0  
#4
Options
Re:WDS connection problem
2014-07-05 01:27:18
Hello jimasek,
it seems not pobbible to assign these DNS to the network card.
See the screenshots below.









Any other ideas?
  0  
  0  
#5
Options
Re:WDS connection problem
2014-07-05 15:12:30
You don't need to use the google DNS (8.8.8.8) !
Use your primary router address instead (192.168.0.1), but put it into the Gateway and DNS fields of TCP/IPv4 properties !
  1  
  1  
#6
Options