Unable to connect to device via IP address or DLINKAPP

<< < (2/4) > >>

toddrom:
Quote

The reason you can't access it is because your PC network adapter isn't communicating with the 1522 and isn't automatically getting the correct IP info to do so.
This not correct - I had 2 computers running xp x64 and W7 x64 wired to the DAP-1552 configured (using WPS button) in bridge mode to a DIR-655 router. The connection worked just fine, I was able to see all other PC's and devices on my network, access internet, etc.... The problem is that I was not able to see the DAP 1552 from anywhere and access its configuration menu. After a "factory" reset, the configuration setup to my router was preserved since I did not have to use the WPS buttong again.
I could not see its MAC address in the arp table either.

I tried again to reset it and configured the PC wired to it with 192.168.0.99:
IP address: 192.168.0.99
Subnet: 255.255.255.0
Gateway: 192.168.0.50
This time it worked!

I tried the above settings several times before with same gateway and various other IP's but it never worked. I think the .99 IP made the difference but I don't understand why.

In the configuration menu I changed the DAP LAN to DHCP, connected it to my router and now it is working again in bridge mode and I can access it by its new 10..199 IP  address or http://dlinkap from any PC, wired or not, responds to pings, can see it in arp cache and everything is normal.

The configuration with the .99 IP seems to have been recomended by Dlink before since I found it in this post:
http://www.paraesthesia.com/archive/2010/05/04/connect-to-the-d-link-dap-1522-access-point-configuration-manually.aspx
The remarks regarding DHCP are right cause since I tried many times with static IP and .50 gateway before trying the .99 IP
Plus, the use of the gateway does not make sense either since both are configured with static IP's and physically on the same network. I can confirm that the pings and attempts to access the DAP were using the right adapter as shown also in the routing table. I even tried it with all other network adapters disabled on the PC to make sure.

rtk:
Considering your fix was essentially what I told you to do (other than assign a different IP address to your PC) not sure what you disagree with.   With regards to the 1522 DHCP vs. static IP setting when running in Bridge mode, mine is set to static IP which allows the IP's to be assigned from the wireless router connected to the 1522.

Quote from: toddrom on June 21, 2010, 11:46:41 AM

This not correct - I had 2 computers running xp x64 and W7 x64 wired to the DAP-1552 configured (using WPS button) in bridge mode to a DIR-655 router. The connection worked just fine, I was able to see all other PC's and devices on my network, access internet, etc.... The problem is that I was not able to see the DAP 1552 from anywhere and access its configuration menu. After a "factory" reset, the configuration setup to my router was preserved since I did not have to use the WPS buttong again.
I could not see its MAC address in the arp table either.

I tried again to reset it and configured the PC wired to it with 192.168.0.99:
IP address: 192.168.0.99
Subnet: 255.255.255.0
Gateway: 192.168.0.50
This time it worked!

I tried the above settings several times before with same gateway and various other IP's but it never worked. I think the .99 IP made the difference but I don't understand why.

In the configuration menu I changed the DAP LAN to DHCP, connected it to my router and now it is working again in bridge mode and I can access it by its new 10..199 IP  address or http://dlinkap from any PC, wired or not, responds to pings, can see it in arp cache and everything is normal.

The configuration with the .99 IP seems to have been recomended by Dlink before since I found it in this post:
http://www.paraesthesia.com/archive/2010/05/04/connect-to-the-d-link-dap-1522-access-point-configuration-manually.aspx
The remarks regarding DHCP are right cause since I tried many times with static IP and .50 gateway before trying the .99 IP
Plus, the use of the gateway does not make sense either since both are configured with static IP's and physically on the same network. I can confirm that the pings and attempts to access the DAP were using the right adapter as shown also in the routing table. I even tried it with all other network adapters disabled on the PC to make sure.


toddrom:
Here is what I disagree with:

PC wired configuration that I tried and failed (no ping response, no http)
IP address: 192.168.0.2, 5, 9, 15, 49, 52, 254
Subnet: 255.255.255.0, 255.255.0.0, 255.0.0.0
Gateway: 192.168.0.50 or empty

PC wired configuration that worked (ping response and http)
IP address: 192.168.0.99
Subnet: 255.255.255.0
Gateway: 192.168.0.50

From a networking point of view there is no reason whatsoever for the configurations I tried before to fail. The use of gateway should also make no difference on a network with static IP's where all devices attached are in the same range.



rtk:
glad to hear you are working ::)

Fred Mertz:
Thanks to your discussion, I was able to get into the DAP1522 setup.



Fred M

Navigation

[0] Message Index

[#] Next page

[*] Previous page