Print

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

[EddieZ]

Just to give you company: On my 655 using "http://dlinkrouter" does not work either. But I really don't care, since typed URL's are autocompleted nowadays  My former routers (Asus, Linksys) also suffered from the same, but suddenly responded once in a while.
By no means this tells you the device is defective. If you can connect to a computer by IP address and not by NetBIOS name, the problem is with Netbios name resolution.

You can artificially make this happen though, in Windows by editing the HOST file (IP may vary with other configs):
192.168.0.1             dlinkrouter (or in your case 'dlinkap')

The Netbios nameservice will use the HOST file to identify the designated IP by the name. It requires (in Windows) the LMHOST to be active.

I'm sure Mac also has an equivalent (not a creative guy, sorry).

The router or AP does is not DNS server, so name resolution does not take place inside the router. The router will only forward the request to your ISP's DNS server.

The fact that 'DLINKAP' does not work is most probably an issue with the client. This can be caused by a number of reasons. It could be a Netbios broadcast issue (which can not cross other routers/AP's in the LAN), which settings can also partially be manage from the router setup (on the 655 it is on: http://192.168.0.1/Basic/Network.shtml)

Any way... I need to go to sleep (Europe) so I found you an article on these kinds of problems with Netbios: http://articles.techrepublic.com.com/5100-10878_11-5034239.html.

Takeaway: NetBIOS alone should not give you many headaches. Unfortunately, when NetBIOS problems occur they can be difficult to detect. Understanding how NetBIOS works is the key.

Let me know if your issue was solvable by any of the 5 solutions provided (partially also covered above).

Conclusion so far: this issue does not indicate a broken router.

[mig]

I thought (at least on my LAN) the router provides the Name Service (DNS) for all hosts which have requested dynamic IP addresses on the LAN, and (in my case - a Linksys WRT54G w/Tomato firmware) any static LAN IP addresses that I have manually entered into the router's "hosts" table.

I have specified DNS servers (I use opendns) for the router to use to resolve hostnames on the WAN, and I enable DNS relay.

All clients (static and dynamic) use the routers IP as the DNS server in the client's network config.

I have to admit I was (pleasantly) surprised when I first pluged the DAP-1522 into my network and typed http://dlinkap [as the documentation directed] and I got the web GUI for my DAP-1522.  

Then I rationalized the DAP-1522 had obtained a dynamic IP from my router, therefore, it's device name 'dlinkap' was able to be resolved.


EDIT:  I guess my router <network?> is doing NetBIOS name resolution for my LAN not DNS, I have confused those two concepts, and I have edited my previous posts to correct my mistake 

[EddieZ]

I thought (at least on my LAN) the router provides the Name Service (DNS) for all hosts which have requested dynamic IP addresses on the LAN, and (in my case - a Linksys WRT54G w/Tomato firmware) any static LAN IP addresses that I have manually entered into the router's "hosts" table.

Through Netbios name resolution it does. Not through DNS (looks the same but isn't--to cut a long story short).
I do know that Tomato firmware (and other alternative firmware) have more advanced DNS capabilities added to the standard package), so cannot be compared to standard firmware.

DHCP sends a packagewith Netbios info. Perhaps statically assigning LAN IP's ('reservation') affects this, I don't know and haven't tried it.

[Lycan]

more importantly the NETBios can be blocked by a number of things on a given network and is ****e to......failures. Yea, I thought I was going crazy there for a second. Well that still may be true but I was right about the NetBios thing at least.

[EddieZ]

Nice one: http://networking.nitecruzr.net/2005/05/address-resolution-on-lan.html

[glathe1851]

I found this chain in my search as my own DAP-1522 was making me crazy.
I found the answers here unhelpful and a little harsh in the personal invective.

Yet there was no actual answer to the issue - here is how I stumbled through the problem.

I used RESET - Note:  takes 10 seconds to restore factory settings.

Many routers for small lans use the subnet 192.168.1.X...
The DAP-1522 uses 192.168.0.X...
So if you are NOT on the same subnet you will not be able to access the device.

I plugged in the wired ethernet connection and manually configured the TCP/IP properties:
Address:  192.168.1.25 (can be anything but ...1 and ...50)
Subnet Mask:  255.255.255.0
Default Gateway:  192.168.0.1 (the DAP 1522 itslef)

I set the slide switch to AUTO and reset to factory settings...

Now I can access the thing at 192.168.0.50 - just as per the manual.
At this point the default name dlinkap will work since you are on the same subnet.
You see, the DAP-1522 intercepts the request and if it sees its own name then it responds directly.

When I was done I set the slide swith back to AP since it is wired to my router and I use it as an access point...

Now that you are there, I think you can follow the manual to get wherever you are going.

[glathe1851]

Oops, so used to typing 192.168.1.xxx that I have muscle memory, the manual TCP/IP setting I used was 192.168.0.25 to be on the ...0.xxx subnet.