D-Link Forums
The Graveyard - Products No Longer Supported => Access Points / Extenders => DAP-1522 => Topic started by: misterdna on January 23, 2009, 03:55:19 AM
-
Okay, I can't figure out if I have a defective DAP-1522, or what. First off, I have never been able to access the unit at http://DLINKAP when my computer is connected directly to the 1522 via ethernet, only 192.168.0.50 works to bring up the web interface.
Second, I have more than one AP at my house, but the DAP-1522 is the only networking device I have have problems with (I am using the unit in AP mode). Basically, the problem is the wireless connection usually is much slower than my other APs (both N and G), even when the computer is physically right next to the DAP-1522. And that's when the unit is at it's best. At it's worst, I can't connect to the internet at all, even though my laptop shows full signal strength. The 1522 just seems really finicky. The problem doesn't seem to be a networking issue, because a 2nd AP that is connected through the wired portion of the DAP-1522 works perfectly, implying the 1522 is having no networking issues when using the ethernet ports. But since the problems persist with full signal strength and with the computer right next to the 1522, it doesn't seem to be a wireless connection issue either. And I have no problems connecting to any other wireless APs I own (and I own about 5 others, not that I use them all at the same time).
If I could, I would return my 1522, but I've been tinkering with it for too long now to return it. It has caused me a ton of frustration. I had a wired-only router for a long time (hence the purchase of the 1522), but just bought a new wireless-N router that is performing perfectly (as a router, and as an N AP). I hoped the old router might have not been playing nice with the 1522, but have seen no improvement with the 1522 wired to the new router (on opposite ends of my home).
Note that I use Macs only, no Windows machines. I started with the 1.02 firmware for the 1522, now have 1.20 firmware, but have noticed no improvements with my issues.
-
How exactly do you have the dap-1522 connected?
-
Currently, DAP-1522 is connected to router via ethernet (which is connected ethernet to cable modem via ethernet). But when I'm changing settings, I connect my laptop directly to the DAP-1522 via ethernet (can't seem to figure out any other way to access the 1522).
-
Have you tried a hard restart? Also different channels and channel width.
-
Have you tried a hard restart? Also different channels and channel width.
I've spent more time experimenting with settings. Originally had it set to use the Auto Channel Scan feature, and then tried manually a few different channels... No change with the performance issues. Also tried both the 20 and auto 20/40 width setting, and neither setting has fixed my problems.
I tried a hard reset too, no difference. Basically, even when the DAP-1522 is very close to our laptops (my wife's has G and mine has N), and the 1522 shows the strongest wireless signal, the performance for accessing web pages, etc. is almost always much slower than when we are connected to my other WAPs. And sometimes pages just don't load at all. All in all, just very undependable.
My other two devices, an old Airport Express G router (used as AP, not in router mode), and a new SMC N router, both give me great results, always loading web pages quickly.
Any other suggestions/advice? I haven't ever contacted D-Link support, as I've found boards like these typically give better results (and don't require lots and lots of time on the phone repeating steps I've already tried). But I'm still wondering if perhaps I have a lemon...
BTW, can anyone address my comment about "http://DLINKAP" never working right for me, even when I connect my laptop directly to the DAP-1522 (and have no other wired or wireless connection)? Does it work for everyone else? Heck, if I type it in right now, I got to a parked internet website, not to the router.
-
Have you tried giving it a static ip address?
-
I had the DAP-1522 being assigned to a never-expiring IP by the router, but just tried it using a static IP, and couldn't get any pages (or network devices) to load while connected to it. Router still saw the 1522 fine, and I could still access the 1522 at it's (now static) IP address when connected through a different AP.
Can you/anyone please address my question about "http://DLINKAP" never working for me from day one (with or w/o static IP, etc.)? Just seems weird that this very basic connection address has never worked for me -- and odd that someone besides D-Link owns the domain name DLINKAP.com (which is what I get if I'm connected to the internet).
EDIT: Just to add more info, I can connect directly (wirelessly) to the 1522 fine with the static IP setting (and I can connect to the 1522 via another AP on the network), but I'm not getting any web pages (or network devices) with the static IP setting, when connected (wirelessly) to the 1522. When I put the 1522 back to the dynamic IP setting, I am able to get online. In fact, the 1522 seems to be working better after going back and forth with the IP setting. Since the behavior has been sporadic, I'm not holding my breath... But maybe now it's working okay? Well, the "http://DLINKAP" address still isn't working.
-
When you connect the dap-1522 directly to the modem do you still get these problems?
Also what is the switch on the back set to?
Which browser are you using when you try http://dlinkap?
What security mode are you using?
What 802.11 band is it set to?
-
When you connect the dap-1522 directly to the modem do you still get these problems?
Would never occur to me to try this, since this is an AP, not a router.
Also what is the switch on the back set to?
As mentioned in my first post, unit is in AP mode.
Which browser are you using when you try http://dlinkap?
Firefox and Safari (remember, I'm on a Mac).
What security mode are you using?
WPA Personal
What 802.11 band is it set to?
G and N
I have to admit, I'm starting to feel frustrated, like you're putting me through the ringer with question after question after question. Do you realize you haven't given me one hint of an answer, only question after question? Think you can throw me a bone give me just a give me a tiny bit of feedback, a few thoughts, ideas on what my problem is, anything but another question? I mean, I assume this thing should work for most people without having to tweak every setting, right? There are probably millions of possible setting combinations for this thing, and I have already spent so much time with it (before I posted my question on this board) that I am not sure I am up for spending more time with it with zero constructive feedback. As the thread titles state, the DAP-1522 was driving me crazy, and any more questions without any answers at all will probably send me over the deep end.
-
Simple reason for the questions is to find out what you have and haven't tried yet. By band mode I meant 2.4GHz or 5GHz. When you have security mode off is it still slow? I'll stop with those. My last thing would be to try and connect it directly to a pc and start over (hard restart) with a static ip that is not in use and not one from any router. Also try putting the switch on the back to auto. See what happens when you try to connect to one of the routers. There was a post that said it could be software on the pc thats blocking dlinkap. Once you've done setup, connect it to the router and see if it works better.
-
Am using 2.4GHz because my wife's laptop is only G compatible. Her computer has even more problems with connecting to the DAP-1522... And I haven't tried with security off. Are you thinking I could have a wireless security setting wrong?
Regardless of those issue, the connection problems are totally sporadic for both of us -- I can always connect, but network info is often slow, sometimes not there. However, my wife's G computer often can't connect at all (in both cases, we are practically next to device, it shows full signal strength).
I feel like I'm begging you to address the fact that the http://dlinkap never works for me. Is there a known issue with this link working with Macs? As I explained. my inability to connect to this address exists in all situations, including when the 1522 is connected directly to my Mac via ethernet, and there is no connection (wired or wireless) to any external network. Thus, there's no way wireless settings are related to this issue. The only explanations in my mind are (1) there's a known issue with this link working on current Macs, or (2) my DAP-1522 is defective. Could you or anyone please weigh in on this specific issue? If I get no other answer, that is the one thing I really would like feedback on. As a reminder, I have hard-reset my device, used the original and current firmware, but in all situations, the link http://dlinkap has never worked for me since day one. However, I have zero problems connecting to the 1522 using the IP address.
I guess it's hard for me, a newbie to this device, wondering if you are trying to troubleshoot:
(1) general network and wireless issues and standard DAP-1522 network/wireess settings, or
(2) DAP-1522 known-issues, bugs, or generally missed or strange 1522 settings that screw many people up.
I think, at this point, I'm really interested in advice regarding #2. I feel confident enough that I have worked through #1, having successfully set up a lot of devices on my home networks, including old and new routers from a variety of manufacturers (some have been used as wireless access points), an IP camera (with lots of advanced settings), an IP robot (with lots of advanced settins), my TiVo, used port forwarding, DMZ, etc.
So I guess I explained the info I'm dying to get from someone who knows the 1522. Regardless, I'll probably try one more hard reset, configure all the settings again, and give it one more try. If that doesn't make this AP work up to the level of my other APs, I guess I'll assume I have a broken unit, and I'll do what I can to get D-Link to replace it under warranty. If I get a new one with zero issues, I'll kick myself for all the hours I've wasted trying to troubleshoot this thing (mostly done before I joined this board).
Anyone know the quickest path to getting D-Link to warranty replace this thing?
Thanks for helping me out.!
-
tried setting the channel manually?
I have a DIR-655
and the DAP-1522 was insanely slow when I set the DIR-655's auto channel selection
setting them manually to channel 11 ( 20-70MHz on channel 7 ) , the studdering dissapeared and got a speedboost on transfers ( even when the signal streght stays the same )
-
tried setting the channel manually?
I have a DIR-655
and the DAP-1522 was insanely slow when I set the DIR-655's auto channel selection
setting them manually to channel 11 ( 20-70MHz on channel 7 ) , the studdering dissapeared and got a speedboost on transfers ( even when the signal streght stays the same )
As mentioned in my early questioning, yes, I've done manual and auto channel select.
I'm going to abandon all my other questions, and just repeat this single question:
The link http://dlinkap never works for me. Is there a known issue with this link working with Macs? As I explained. my inability to connect to this address exists in all situations, including when the 1522 is connected directly to my Mac via ethernet, and there is no connection (wired or wireless) to any external network. Thus, there's no way wireless settings are related to this issue. The only explanations in my mind are (1) there's a known issue with this link working on current Macs, or (2) my DAP-1522 is defective. Could you or anyone please weigh in on this specific issue? If I get no other answer, that is the one thing I really would like feedback on. As a reminder, I have hard-reset my device, used the original and current firmware, but in all situations, the link http://dlinkap has never worked for me since day one. However, I have zero problems connecting to the 1522 using the IP address.
-
btw, you're still using 1.20?
because it seems to have been removed.
also, have you tried in a PC?
I think its the only way to see if its a "naming" problem related to DLINK hardware and MACS
because I dont have your problem. ( note, my DAP-1522 came with 1.10 from the factory )
-
I'm going to abandon all my other questions, and just repeat this single question:
The link http://dlinkap never works for me. Is there a known issue with this link working with Macs?
There is a network device called a DNS or Domain Name Server. The purpose of this device is <NetBIOS name resolution is used to> translate the name of all devices on the network to their Ethernet IP address. If your DNS <NetBIOS name resolution> is not working properly, or a device has not properly registered it's name and IP address with the DNS <NetBIOS name resolution>, or you renamed the the DAP-1522, then you will not be able to access a device by it's default name 'dlinkap', only by it's IP address '192.168.0.50.
It seems to me that this is the symptom you are seeing - access by IP address but not by name.
Look on the 'network settings' page to see what 'lan connection type' and 'device name' you have set of your DAP-1522
:-[ EDITED: to replace incorrect DNS with NetBIOS name resolution
-
@ tamalero: I will try an old Windows machine I have and see what happens after a hard reset. If http://dlinkap doesn't work in that case, I will probably give up and try getting this thib replaced.
@ mig: On the network settings page's two settings:
1) LAN connection type: (dynamic or static) - As I mentioned above, I've tried both settings, but when connected to my network, the 1522 only seems to work properly with the dynamic setting, at which point the IP address is assigned 192.168.2.195 by my router. When I have the 1522 attached directly to my laptop via ethernet, and no DHCP is detected, the 1522 IP reverts to 192.168.0.50 (as is intended, in dynamic IP mode). http://dlinkap doesn't work in any of these set-ups. When I tried the static IP setting, I entered 192.168.2.195, and kept this IP lease on the router as forever. I was still able to access the device at 192.168.2.195, but the wireless connection would not serve up any web pages.
2) DEVICE NAME (NETBIOS NAME) - Mine says "1522". I don't know if I changed it. But even if I did, neither "1522" or "DAP-1522" is "dlinkap", so it doesn't seem like my device name setting would be messing up that URL. Also, from fresh out of the package, and fresh from a hard reset, you'd think think this would have the default device name settings, and the URL would work have worked as it is supposed to... But it never has.
I'll post again after I've tried the Windows machine and another hard reset.
-
When you changed it to "dlinkap" it still would not work? Are there any other devices that could be interfering with the dap-1522?
Do you still get these same problems in "bridge mode"? Also f/w 1.20 has been taken off the support page, so maybe give 1.10 a try. As I said before the reason for the questions is to find out what you've done.
-
When you changed it to "dlinkap" it still would not work? Are there any other devices that could be interfering with the dap-1522?
Do you still get these same problems in "bridge mode"? Also f/w 1.20 has been taken off the support page, so maybe give 1.10 a try. As I said before the reason for the questions is to find out what you've done.
Changed name to "dlinkap" and I still get the internet page dlinkap.com when I try the URL. There can't be another device interfering, because (as I've mentioned a few times), the dlinkap URL doesn't work even when the 1522 is connected directly to my laptop with ethernet, and neither are connected to anything other devices in any way (wired or wirelessly).
I've tried the 1522 in every mode, the dlinkap URL has never worked in any mode. BTW, shouldn't the URL work in every mode? When you ask me to try bridge mode, is it because AP mode is a known issue? Sorry ANON, but sometimes I feel you simply want me to try every available setting on this thing, and I just don't have time to do that.
I saw the post that the 1.20 firmware was taken off, and I haven't had a chance to change the firmware again. But as I said in my initial post, the URL problem existed for me with the initial loaded firmware too, so it's not purely an issue with the 1.20 firmware. But I will load the most recent firmware (still up), do a hard reset, and try accessing http://dlinkap from a Windows machine. If that doesn't work, I'm declaring my unit a lemon.
-
That sounds fishy, it indeed seems something is either interfering with your hardware ( believe it or not, some cellphones can make the DIR-655 reboot until they're taken a few meters away ).
or the unit is defective.
at first I had problems setting up the DAP-1522 ( auto didnt work )
but anyway my steps
1.- laptop on ( change ethernet to 192.168.0.3 )
2.- set DAP-1522 to bridge
3.- connect to the laptop on any port of the DAP
4.- bring the basic ip 192.168.0.50
5.- configure the wireless bridge ( including disable DHCP, channels..etc.. )
6.- connect
7.- change the internal ip address then soft-reboot ( from inside )
after I restarted, I connected with my laptop wireless ( disconnected the ethernet )
and accessed the DAP using my router's wireless connection and seems to work fine.
btw, you can try this as well by plugging the DAP-1522 to the DIR-655 but I DO NOT RECOMMEND IT
as soon you connect your bridge to the DIR-655 ( via wireless )
the DIR-655 will slowdown to a crawl... and detect a "LAND ATTACK" ( router loop lol )
so unplug fast.. and.. thats done...
the weird thing, seems the DAP-1522 are very delicate components, each one as their own quirks and thigns that make them bugg out..
in my case.. the channel on auto on dir-655 will slowdown my DAP-1522 to a crawl.
-
2) DEVICE NAME (NETBIOS NAME) - Mine says "1522". I don't know if I changed it. But even if I did, neither "1522" or "DAP-1522" is "dlinkap", so it doesn't seem like my device name setting would be messing up that URL.
The device name IS that URL. If you name your device "myaccesspoint" then http://myaccesspoint should get your browser to load the web GUI for your DAP-1522. This URL will only work if there is a DNS service on <NetBIOS name resoultion> on your network to translate the character string "myaccesspoint" into the static (or dynamic) IP address assigned to your device.
Part of the reason http://dlinkap does not work (there could be more factors contributing to this URL failure) is that your device is not name "dlinkap".
When you use dynamic IP, your router (who assigns the IP address) should be acting as the DNS <NetBIOS name resolution>for the IP addresses it assigns dynamically. What is the manufacture and model of your router? The problem could lie there?
:-[ EDITED: to replace incorrect DNS with NetBIOS name resolution
-
The device name IS that URL. If you name your device "myaccesspoint" then http://myaccesspoint should get your browser to load the web GUI for your DAP-1522. This URL will only work if there is a DNS service on your network to translate the character string "myaccesspoint" into the static (or dynamic) IP address assigned to your device.
Part of the reason http://dlinkap does not work (there could be more factors contributing to this URL failure) is that your device is not name "dlinkap".
When you use dynamic IP, your router (who assigns the IP address) shoud be acting as the DNS for the IP addresses is assign dynamically. What is the manufacture and model of your router? The problem could lie there?
I feel like you are missing much of what I've said (several times) in this thread. The URL has never worked from day one, fresh out of the box, connected straight to my laptop via ethernet. The day I received this device, I followed the quick set-up directions, which said to use "http://dlinkap" to access the device, and that URL didn't work even then. I then tried the IP address listed, and that's always been the only way I could log on to the 1522 (via default or assigned IP address). So clearly, the problem has existed before any router was in the picture, so there is no way it could be the router causing the problems (btw, I've tried the 1522 with two routers, and also connect directly to the device, w/o being connected to anything else, when trying to troubleshoot). I have configured many IP devices, other WAPs, and other things on my network and have zero networking issues, the only network/wireless problems I have are 1522 issues (which, at this point, I'm just focusing on one of, but all of them are listed at the beginning of the thread). Also, my post that you are replying to says I did put the device name to dlinkap and it still doesn't work (it brings up dlinkap.com, on the web).
While I feel very certain my router has nothing to do with my issues (for the reasons mentioned above, plus this router has impressed the hell out of me with it's stability, features, and user ratings), it is the SMC WGBR14-N, which I believe is SMC's top-of-the-line consumer Gigabit N router.
I have set up a lot of devices on my network, many a lot more complicated that this thing, and I just don't have issues like I am having with the 1522... Which makes me think it's a problem with my unti, not a problem with a setting.
Anyway, as I said in my previous post, I will change the firmware, hard-reset, and try a windows machine and see what happens. Please sit-tight until I do that and post my results.
-
You type in "dlinkap" and dlinkap.com is what your browser brings up?
The questions I last posted was for all the "problems" you first stated, not just the "dlinkap" issue.
Guess it's time to give the tech support a call on getting another dap.
-
That sounds fishy, it indeed seems something is either interfering with your hardware ( believe it or not, some cellphones can make the DIR-655 reboot until they're taken a few meters away ).
or the unit is defective.
Thanks for saying the unit could be defective. I really needed to hear someone on this board say that. Not that it IS defective, but just acknowledge that it COULD BE defective. Really felt like I was taking crazy pills...
-
You type in "dlinkap" and dlinkap.com is what your browser brings up?
Sorry to sound exasperated, but YES! I've said this in more than one post that dlinkap.com comes up when I put in http://dlinkap. Some domain name squatter owns that URL (surprised D-Link didn't buy it for themselves).
-
1) NETBIOS resolution can be tricky. I wouldn't worry about it not working too much as long as you can reach the AP by it's IP. Do you have other AP's or devices that resolve NETBIOS names?
2) How many AP's do you have in your house? Are they all DAP-1522? how many are running at the same time?
Unless we understand everything about your network we can't help you fix it. Getting frustrated and asking that we give you some magic answer is not realistic.
How are we supposed to know what the problem is if we don't ask you questions?
Do you go to the doctors and say "I hurt" then when the doctor says "where?" you just demand an answer?
Questions are the only tool we have to help you, short of going to your house and viewing the issues for ourselves.
-
1) NETBIOS resolution can be tricky. I wouldn't worry about it not working too much as long as you can reach the AP by it's IP. Do you have other AP's or devices that resolve NETBIOS names?
2) How many AP's do you have in your house? Are they all DAP-1522? how many are running at the same time?
Unless we understand everything about your network we can't help you fix it. Getting frustrated and asking that we give you some magic answer is not realistic.
How are we supposed to know what the problem is if we don't ask you questions?
Do you go to the doctors and say "I hurt" then when the doctor says "where?" you just demand an answer?
Questions are the only tool we have to help you, short of going to your house and viewing the issues for ourselves.
The thing is all I did was answer question for the first page of this thread. I didn't get frustrated for awhile, when I just kept getting questions, but was getting zero answers. So you're way off base saying I expected a magic answer without answering questions. Also frustrated with how much time I've spent messing with this device, and now feeling like I'm repeating myself many times in the same thread when I'm asked questions I had answered before (even your question about APs on my network was specifically answered in one of my previous posts).
Aren't all networking issues thrown out the window regarding the URL not working when I explain the URL didn't work from day one, with the device connected straight to a laptop with an ethernet cord (completely isolated from any other device or network)?
This is my only 1522 that I have ever owned. It's my only D-Link wireless device (I do have a gigabit switch by D-Link). Right now I have a router with wireless, an Airport Express in AP mode, and trying to get the 1522 working smoothly. But I've tried the 1522 with many networking configurations, and as I mentioned, totally away from the network too.
At this point, I don't want you guys to help me troubleshoot my network -- I could be wrong, but for many reasons, I feel confident in my network and network troubleshooting abilities. I just want help from people who know this device to help me with this device. Please just humor me, and pretend this isn't a networking issue. My network works great in every respect, with my Rovio and IP camera, and multiple computers -- everything works as expected, and is accounted for correctly in the router. In the past year I have spent hours learning about my network in order to set-up many IP devices, and don't want to start back to square-one network troubleshooting just to get a lowely WAP to work (when I don't believe that is my issue).
Again, my reasoning for focusing on this issue: it is a non-network issue I've had since day one, and I figure if it is proven the device isn't working properly with this URL issue, it could serve as evidence my unit is defective, and I should replace it. At some point awhile ago, the cost of the hours spent troubleshooting this device has eclipsed the cost of tossing it. And now I keep allowing myself to feel the need to respond to posts. I think my idea of changing firmware, hard reset, try from windows machine makes complete sense as a final step to test if the URL works, and I'm going with this idea. No one else has said they have problems with the URL, so I am going to assume that the unit is bad if the URL doesn't work as it is supposed to. Please, help others in need in the meantime, no need to try to help me any more.
-
I feel like you are missing much of what I've said (several times) in this thread...
Well, I feel you seem to be missing is the fact that networks (both local and wide area - internet) run on numbers or IP addresses like "192.168.0.50" not names line "dlinkap". (and I'm surprised at this since you state you are an experienced network administrator) You will NEVER be successful with http://dlinkap until you have a correctly configured service (such as a DNS) <NetBIOS name resolution> to translate the "dlinkap" to the IP address "192.168.0.50" [or what ever IP address you have assigned to your DAP-1522]
When you connect your mac laptop directly to the DAP-1522, do you know what service, on that single cable, point to point network, which is responsible to translate names to IP addresses? I don't believe there a service to fulfill that requirement, and that is the reason that typing http://dlinkap in your browser does not work (and the additional possibility that the DAP-1552 may not be named "dlinkap")
When you connect your DAP-1522 to your router, the router <NetBIOS name resolution> is responsible for translating names to IP addresses. If the router's DNS <NetBIOS name resolution> is not configured correctly, there will be no resolution for "dlinkap" and the router will ask your ISPs DNS servers if there is any domain name "dlinkap.com" that can be translated to and IP address (your web browser is trying to 'help you out' in this failure situation by adding the .com to the end of your original request name of 'dlinkap'). Your IPSs DNS servers will find there is a domain "dlinkap.com" that can be translated to an IP address of 208.73.210.121 registered by Jan Svoboda (who has registered about 40K domain, definitely a squatter) and your web browser show you that page. [by the way, my employer has blocked my access to that site, claiming Filter Category: Viral_Content_Sites;Advertisements;Productivity - so be careful)
In each situation http://IPaddress does work, so this means the http://dlinkap issue is a result of name to IP address translation failure, not a failure with the DAP-1522.
If you can get past this issue, you may be able to get help for you other DAP-1522 issues. However, if you are frustrated with the setup and performance of the DAP-1522, perhaps it is not the best device for you. Stop driving yourself crazy, declare your unit defective, cut your losses (in money and time), chalk it up to experience, and go purchase another access point which may work better in your particular network situation.
:-[ EDITED: to replace incorrect DNS with NetBIOS name resolution
-
Well, I feel you seem to be missing is the fact that networks (both local and wide area - internet) run on numbers or IP addresses like "192.168.0.50" not names line "dlinkap". (and I'm surprised at this since you state you are an experienced network administrator) You will NEVER be successful with http://dlinkap until you have a correctly configured service (such as a DNS) to translate the "dlinkap" to the IP address "192.168.0.50" [or what ever IP address you have assigned to your DAP-1522]
W
Its a NETBIOS name, not DNS.
-
Its a NETBIOS name, not DNS.
So what device (process?) handles the NETBIOS Name Service (NBNS) on a Macs only (no Windows machines) network? In this situation, wouldn't the Name Resolution fall back to the router's DNS?
-
1) A router doesn't have DNS. It' has DNS servers. On the WAN and they're not going to know what your Ip=DNS name res is.
2) It's NETbios, I have no clue. I don't really work with Mac.
Lets see if I can get someone that knows more then me about it.
oh Eddie.....?
-
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.
-
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 :-[
-
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.
-
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.
-
Nice one: http://networking.nitecruzr.net/2005/05/address-resolution-on-lan.html
-
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.
-
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.