Hi,

As TP-Link uses only "Lazy WDS", you have only to enable WDS on the TL.
Did you choose the channel manually and use 2 separate SSID?

HiSpeed wrote

Hi,

As TP-Link uses only "Lazy WDS", you have only to enable WDS on the TL.
Did you choose the channel manually and use 2 separate SSID?

Thanks for the reply. Yes, it is just WDS on the TL, although I have also tried on just the TD, and on both.
The channel is manually chosen as 11, the SSIDs are different, but have also tried the same.

Alos I have made sure the firmware is most updated.

Any other ideas?

I have a WR1043ND working WDS perfectly.
Did you set your laptop statically, I mean with a fixed IP address and the TD address in Gateway and DNS?

HiSpeed wrote

I have a WR1043ND working WDS perfectly.
Did you set your laptop statically, I mean with a fixed IP address and the TD address in Gateway and DNS?

Yes, using Debian Linux.

My ip address on laptop is 10.0.2.37, netmask 255.0.0.0, gw 10.0.2.253, dns 10.0.2.253.
TD address 10.0.2.253, netmask 255.0.0.0
TL address 10.0.2.15, netmask 255.0.0.0

Is that all okay?

Why do you use a class A and not a class C?
Did you enable the MAC address filtering?

HiSpeed wrote

Why do you use a class A and not a class C?
Did you enable the MAC address filtering?

...just always have for a 10.0.x.x network. It makes no difference being under class C 255.255.255.0 either, but I have set that for both devices right now.

Also interesting, I just ran the diagnostics from the TL, and got these results:
Pinging 10.0.2.253 with 64 bytes of data:

Reply from 10.0.2.253: bytes=64 time=1 TTL=64 seq=1
Reply from 10.0.2.253: bytes=64 time=126 TTL=64 seq=2
Reply from 10.0.2.253: bytes=64 time=2 TTL=64 seq=3
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.0.2.253
Packets: Sent = 15, Received = 3, Lost = 12 (80% loss),
Approximate round trip times in milliseconds:
Minimum = 1, Maximum = 126, Average = 43


Now why should it be doing that?
The devices are within 8m of each other, and I have no trouble connecting via laptop.

Are you using the last firmware (3/24/2009)?

HiSpeed wrote

Are you using the last firmware (3/24/2009)?

Firmware Version:
3.13.9 Build 120201 Rel.54965n
Hardware Version:
WR941N v2/v3 00000000

Firmware Version:0.6.0 1.1 v0005.0 Build 120926 Rel.27100n
Hardware Version:TD-W8968 v1 00000000

I had same problem. My Main router is adsl td-8951n earlier version but supports WDS. I bought two TL-WR740N to setups as WDS bridge and to expand my wireless coverage. I had following setup

TD-8951N
IP: 192.168.1.1
Subnet: 255.255.255.0
DHCP: Enabled from 192.168.1.100 to 200
SSID: main

TL-WR740N
IP: 192.168.1.2
Subnet: 255.255.255.0
DHCP: off
WDS bridge SSID main with WPA2 password.
Wireless set to SSID repeat1 with WPA2 password.

TL-WR740N second one
IP: 192.168.1.3
Subnet: 255.255.255.0
DHCP: off
WDS bridge SSID main with WPA2 password.
Wireless set SSID repeat2 with WPA2 password.

Problem:
------------
When connected to SSID main, can access (GUI and ping) all three access point and internet
When connected to SSID repeat1, can access own and second WR 740N. No GUI and ping access to main router and no internet.
When connected to SSID repeat1, can access own and second WR 740N. No GUI and ping access to main router and no internet.

The problem is that gateway IP 192.168.1.1 cannot be access when connected from WR 740N. As such internet does not work.

Solution:
-----------
It seems there is incompatibility issue on WDS between 8951N and 740N. As I connected 8951N to wan port of 740N. And second 740N was connected wirelessly through WDS to first 740N, DHCP turned on first 740N and off on second. There were no issue like the above, ping among all three access point worked and internet worked.