Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vorta]

Hello!

I've registered here to ask about this unusual issue I'm having with a wireless extender. I'll refer to DAP-1320 as the "extender" and to ZTE ZXV10 H201L as the "router".

I turn the extender on and connect to it with my laptop. I've configured it to connect to my wireless network, which I want to extend, by entering the correct SSID and password. Upon reboot device cannot connect to the network. After waiting for half an hour I went into the network settings of the extender and the IP the extender wants for himself was 192.168.0.50. So DHCP obviously doesn't work properly.
The router operates on a different subnet. It's IP as well as IPs of all devices on the local network are 192.168.1.xxx. There are different ranges for different ports, 192.168.1.41 - 192.168.1.50 being for SSID1.

I've created SSID2 with a range of 192.168.1.51 - 192.168.1.60 to be sure there will be no conflicts with devices using SSID1 and configured the extender as follows:
LAN Connection: Static IP
IP Address: 192.168.1.51
Subnet mask: 255.255.255.0
Gateway Address: 192.168.1.1 (the router's IP)
Primary DNS Server: 8.8.8.8

Upon reboot extender reports a successful connection to the router. Yay! ...but we're not done yet.

With my laptop I do have a connection to the extender (I can open it's web GUI) and I can access the router, through the extender, as I can open it's web GUI on 192.168.1.1. But I don't have access to the Internet?!

I went to inspect my connection between the laptop and the extender and found out that extender gave my laptop very wrong IP details:
IP Address: 192.168.0.81
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.50
DHCP Server: 192.168.1.51
DNS Server: 192.168.0.50

Wrong subnet, wrong gateway... No wonder I can only reach devices on local network.

So I went in and manually defined IPv4 settings for my laptop:
IP Address: 192.168.1.52
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Server: 8.8.8.8

Hooray! I could finally connect to the internet through the extender. Yay! ...but we're not done yet.

Even though I could happily surf the Internet on my laptop, all of the devices on LAN1-4 ports started getting IP-s in range 192.168.0.8X and their Internet connection died. Chrome would report "DNS_PROBE_FINISHED_NO_INTERNET". Soon no device on the network apart for my manually configured laptop could connect to the Internet, as they were all suddenly on 192.168.0.8X IP range. Even though they are not connected to the extender. They are connected directly to the router. For some reason router started giving them all IP Addresses the way that extender does, with wrong subnet as well as wrong default gateway IP (192.168.0.50). Router comes back to normal as soon as I disconnect the extender.

So I'm at the end of my wits. There must be something I'm doing wrong here. e.g. even though extender's new device IP is 192.168.1.51, I can still access it at 192.168.0.50 as well. Even though that IP is no longer displayed anywhere in the extender's GUI.

If anybody can shed some light on this, it would be greatly appreciated.

[Vorta]

Does D-Link support even read this board?

[FurryNutz]

Link>Welcome!

• What Hardware version is your DAP? Look at the sticker under the DAP.
• Link>What Firmware version is currently loaded? Found on the DAPs web page under status.
• What region are you located?

Have you used the set up wizard to help you get the DAP connected to the main host router?
The default IP address of the DAP is 192.168.0.50 so when you set it up, it should chance over to the .1.# pool after it's set up. Then you'll need to probably reboot your DAP connected PC so it sees the change as well after the DAP is set up.

[Vorta]

Hello!

HW Version: B1
Firmware version: v2.03
Region: Croatia

I've tried automatic and manual setup. I've tried changing the IP to .1. pool, but the setting wouldn't "stick". Even though it is set to 192.168.1.50, router still reports using 192.168.0.50 after reboot.

[FurryNutz]

Review the user manual on getting it set up.
Some FAQs:
http://support.dlink.com/FAQView.aspx?f=3uf9wwsabXcQtG6p3l%2b4qQ%3d%3d
http://support.dlink.com/FAQView.aspx?f=IQtAh1GvFfQB5ulA%2fQPE1Q%3d%3d

[Vorta]

I've successfully set it up with another router, which uses .1. as a subnet. However, I can't set it up with a router that uses .0. as a subnet. These manuals don't help me because I've tried/did the things listed.

[FurryNutz]

Since you got the DAP connect with a different model router, this lets us know the DAP is working and there may be an issue with the initial router.

[Vorta]

DAP definitely works in certain cases.

I've tested it with multiple routers. If you read my first post again, the router that was causing the problem. My family has one, my girlfriend's family has one and my cousin has one. The same issue happens with all three of them. DAP is using the wrong subnet.

It works with all the routers that use the same subnet DAP sets itself to and doesn't with all other routers that use a different subnet.

[FurryNutz]

Can you change the IP address pool on the ISP modem to be on the same pool as the DAP?