Print

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

[volkier]

For the record, this is the second unit I am trying to get working right now, without much luck.

The Dir 505 unit gets picked up fine by everything if I don't connect to to my AP. The moment I connect it to my AP (via wifi since that's the whole point of this), it stops broadcasting the signal - ie. I can no longer connect to the DIR 505 itself. This is using different network names from the AP in 'hotspot' mode. I can access everything fine through the wired ethernet connection on the unit, but that's about it in this case.

On the other hand, I can connect to it wirelessly after nuking all the settings back to factory defaults, however this is up until I configure it to connect to my AP - and then the same non-broadcasting issue.

I have tried to update firmware, restart everything etc. This is the second day of trying to get the thing to work, with about 6 hours spent on it last night (ending up going to exchange the unit today), and I'm completely out of ideas.

Basically what I'm trying to do is (well, basically the main thing this product was intended for pretty much):

  <AP> (network name1)     --------    <DIR 505 as an AP> (network name2)   --------   <Wifi connection(s)>


Please help before this drives me to committing seppukku :

[FurryNutz]

Are the 2 APs running different channels? They need to be on different channels and not using the same. You can set up manual channels for each AP. They can be using the same SSID as well, just the channels need to be different, so for you main AP, I would put it at 1 and the DIR-505 at channel 11.

Any cordless house phones?
Any other WiFi routers in the area? Link> Use InSSIDer to find out. How many?

Seem like this might a configuration problem maybe...

[holmes4]

By default, you can't control the channel.  If there are two different SSIDs it should not matter. I run my DIR-505 this way all the time.

Did you do a factory reset after updating the firmware?  I found that was necessary.

[FurryNutz]

Even though the SSIDs maybe different, channels should differ. I presume the the autoscan should and would ensure of this. Just helps to check. Hope it will get going for him. 

[volkier]

Yes, setting all the channels to differ was one of the first things I've done. Yes, done factory reset after firmware update. Basically tried everything mentioned here and more.



HOWEVER, I have after nearly THREE FRIGGING DAYS, finally fixed it!!!!



The solution was reducing the number of characters in the SSID name. It seems that it did not like the network name to be 21 characters. That or it did not like the space characters in there. Either way, works flawlessly now (touch wood). I've been stress testing it with 20+ connections, forced signal interrupts cold reboots since mid-day, and so far no issues. Would also explain why it picked everything up like it should after the factory reset, but not the moment I configured it to broadcast the right SSID etc.

What I don't understand is why it did work for an hour or two at one point of time - albeit after hours of painfully attempting to configure it. Perhaps someone who is a little more familiar with networking and the unit's programming would be able to figure that one out. Might be something for the folks at DLink to look into. Not a biggie, and doesn't even need to be "fixed" - but it would be nice to have a mention of that somewhere...

[FurryNutz]

Wow, thats pretty long characters for SSID names. Usually recommended is the shortest possible. Sometimes using an (_) underscore between two words should work as well if spaces are not working. I would keep the SSID name short if possible.

Glad you found the fix and it's working for you.

Enjoy.

[volkier]

Thing is, I've been using the long(er) SSID on various routers without any issues. Granted, they are dedicated routers rather than a 'pocket gadget', and it's not really an "issue" as far as I'm concerned to have a shorter SSID - I simply never thought that would be the reason for all the problems.

[holmes4]

 I have run into occasional devices that don't correctly support everything legal in an SSID and/or WPA password. I have seen length restrictions and character set restrictions. Spaces in SSID names are not unusual. Had not yet seen that with my 505 but none of my SSIDs have spaces.