D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-890L => Topic started by: rotohead on March 06, 2015, 10:05:00 AM
-
My home network running 890L (ver1.03) has a mixed of wired and wireless devices and initially everything would be visible but lately a couple of NAS devices disappear from the network on three different computers (two wired and one wireless laptop). If done about all I can think of rebooting computers, NAS devices and the router with no success. I've tried assigning IP addresses to no avail. The fact that this is the same on three different computers makes me think it's the router. Any help would be greatly appreciated. I want to keep this router but if I can't fix this it's going back to NewEgg. :-\
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- What region are you located?
- Are you wired or wireless connected to the router?
Router and Wired Configurations
Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router. Besure to log into the Admin account on the router.
- Turn off TrueGigaBit Routing (http://forums.dlink.com/index.php?topic=60699.0) under Setup/Internet/Manual for those routers that have this feature for testing.
- Turn off ALL QoS (http://vonage.nmhoy.net/qos.html) or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options, Advanced/QoS (http://en.wikipedia.org/wiki/Quality_of_service) or Gamefuel. For the DGL-5500, review this for Streamboost information and settings: Furry's DGL-5500 Review (http://forums.dlink.com/index.php?topic=55136.0)
- Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual or under Setup/PARENTAL CONTROL/Set to>None: Static IP or Obtain Automatically From ISP.
- Enable or Disable Use Unicasting (compatibility for some ISP DHCP Servers) and test under Setup/Internet/Manual. Disable may help with speed performance on higher speed ISP services.
- Setup DHCP (http://forums.dlink.com/index.php?topic=58017.0) reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting and maintain consistency for applications that need to connect as well as mapped drives.
For devices like NAS, I use static IP addresses ON the NAS outside of the routers main DHCP IP address pool. I have a DNS-345 and use 192.168.0.34. It's always seen and listed. Review the DHCP lilnk above for more information regarding reserved and static IP addresses.
PC 3rd Party Security Software Configurations
- Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
-
OK, thanks for that quick reply. Most of those router features you mention are not on the 890 but I will try assigning IP addresses and see if that helps. I'm not using any QOS/Parental Controls. Only thing I've configured is the wifi name and password and security. I have a old style Slingbox HD that need one port forwarding rule. That's it. Not a real complex setup. I've report back on the assigning IP numbers and see how it runs over the weekend.
-
What Firmware version is currently loaded? Found on the routers web page under status.
What region are you located?
Ya, I need to make a new list of troubleshooting items for the new Ui.
Let us know about how it goes.
-
In the USA region. As stated in first post I'm running ver 1.03. and I've re flashed it once to see if that would help and it didn't do anything to improve my situation.
Doing the IP reserve on my devices I notice the number of connected devices that show on that page is always changing. One moment there is 18, then 21 then 15, then back to 21. Is that normal? Also, I had a older D-Link router five years ago (can't remember the model number) and I sure like the UI in those older products better then this one. Just my opinion but the 890 lacks much of the features on modern routers. Is there a chance a new firmware is available soon?
-
Here's more info after assigning IP's. The NAS that I'm not seeing listed as 'Computers' in 'Network" do show as 'Media devices'. In addition I can access these NAS devices on my own through browser UI with no problem. Very odd. I'm not seeing any change after assigning IP reserves but I'm gonna continue to troubleshoot.
-
Was a factory reset performed before and after applying the FW update? It's recommended to use this method to apply FW updates.
I recommend settings devices that don't need much router management to static IP addresses. This is were I have my NAS and printer. For those that do need some router management, use reserve method.
Fluctuation in device display probably depends on if the device is present and connected or some device may have sleep mode and thus will cause a disconnection and the device will no longer display on the routers web page.
D-Link is moving to this new UI and it's more simplified for home use since these models are a home class router. Yes the older generation routers had more granular UIs however D-Link may include additional features back in as time goes on.
FW was just released for the 890L. I presume there will be more updates as time goes on. We don't have exact time frame when they are released. I try to post when FW has made it to D-Links web site here in the forums when I can.
-
Was a factory reset performed before and after applying the FW update? It's recommended to use this method to apply FW updates.
....
Yes, I've done a factory reset after FW updates (not just rebooting) and nothing seems to make a difference. I've also re-flashed ver 1.03 in the same way. I'm getting a sinking feeling that this isn't going to get fixed. Thanks for your help though. I love the router's wifi range and good connectivity on my iPhone (for music streaming) but this won't work for me if I can't get access to storage devices to save files from the likes of Quicken, etc.
-
Still need to idenfity the problem or if there is one. Configuration here is key.
Can you post a picture of what your seeing?
Adding Screenshots In A Post (http://forums.dlink.com/index.php?topic=58120.0)
Let us know if using Static IPs on the NAS helps. It's what I use and it works for me...my DNS is always listed there to use.
Also can you map to the NAS as well?
-
OK, I've done a factory reset twice in a row (just to make sure ver 1.03 installed fully) and left everything default except the network name and password. That shouldn't effect wired devices should it? Anyway, I noticed in the 'network' page dlink by default only has ip addresses in the 100 to 199 range. I never noticed that before. The devices I want to see but aren't seeing are 192.168.0.150 and 192.168.0.163. There were however devices that were on my old network that had ip of .250 and .253. I never have gotten around to configuring those devices yet. I've since disconnected those devices and will later configure them if I can get the NAS devices to show up. For now the two NAS devices I'm most interested in seeing are now showing up. Hurray. I'm now going to add the remaining devices one at a time after getting them to let go of their old ip addresses and hopefully DHCP will do it's thing. Then, if all goes well I'll make a couple reserve ip assignments (one at a time) and see if I've got this fixed. I so much want to keep this router.
-
No, nothing seems to have improved overall. After I left it to run untouched for a hour I checked and it's not showing NAS devices again. I then shut every device off and rebooted router, NAS then one wired computer and my idea of the default ip range doesn't seem to have fixed this problem. With only the router, Diskstation NAS and a wired computer and still the wired Diskstation shows up as a media device but not a NAS that can be used. I can log into the Diskstation UI through it's ip address and access the same NAS on my iPhone via wifi. Nothing changed as I turned on a wifi laptop, wired printer and another older NAS by LaCie that also used to be visible but doesn't stay visible. I'm out of ideas. Too bad cause I like Dlink stuff but this isn't fixable IMO. I'm far from being a network expert and would welcome other ideas but I got to get something that works soon. Thanks
-
So you need to set up static IP addresses for the NAS out side of the DHCP IP address pool, so select something from 192.168.0.2 thru .99 or .200 thru .254.
Remove all IP reservations for NAS on the router.
Here what I have for my devices:
(http://i1195.photobucket.com/albums/aa396/furrynutz740il/WindowsNetworkingDIR890L_zpso9xgvp9k.png) (http://s1195.photobucket.com/user/furrynutz740il/media/WindowsNetworkingDIR890L_zpso9xgvp9k.png.html)
-
How do you assign a static ip address that no computer sees? That shouldn't be necessary but I'm not a expert. Another thing that Dlink needs to address in a flaw if you re-install a saved config.bin file. If you've saved a file and used a different admin password (different then password) and you restore that older config file it would not let you in with the changed password or the original default. Your only choice is to press the reset button on the unit. Too many bugs for me. It's going back to NewEgg and I'll try something else. I'm disappointed.
-
Seems like this is just a mis-configuration of the router and your devices. We've presented you with solutions and given you proof it works. Maybe someone can review your configuration and help you get it setup and working well if you interested in kerping the router using Teamviewer.
I suggest not changing the routers admin pw while in trsnsition from one config to another to avoid log in problems. Its not standard manangement practice to chamge router log in pw very often unless it been compromised or users fail to keep the pw to themselves alone. Use one password that you amd you alone know. It doesnt have to be complex either if u wish. Ill forward this finding to D-Link for review to see if its something to fix or not.
-
Thanks Furry for the help. This router was working properly for over a week then I changed the admin pw. There is malware out there that targets the default pw's of popular routers and that's why I changed. I did manage to save/restore a config.bin file. I finally got into the router by not putting anything in the pw field. Makes no sense. I still don't see how I would be able to assign a static ip to a device that doesn't appear as a device especially when MAC addresses aren't associated with ip's. Shouldn't be necessary to do static ip's that way anyway. I believe the firmware is permanently corrupted and can't be repaired or re-flashed. NewEgg gave me a return label/RMA so if I can't re-flash the firmware I'll send it back and get something else. I'm not real satisfied with the UI as it is limited even if it's primarily for home use. Thanks again. Appreciate your efforts to help me.
-
Here's another bug in this fw. I've restarted the fw from the beginning (1.0) and then flashed to ver 1.02. After 1.02 I ask it to check for a new fw (which I know exists 1.03) it says I already have the newest firmware. The only way to flash 1.03 is to do it manually. That's not right for a router intended for simplified home installs, if that's dlinks goal. Shouldn't need to configure static ip's either.
-
Rotohead,
FurryNutz has some GREAT advice in regards to static IP addressing OUTSIDE your DHCP range.
1) Open Router GUI
2) Identify your DHCP range, example 192.168.0.100 to 192.168.0.199
3) Your NAS box, configure it to ..... 192.168.0.201
4) reconnect NAS box to network and see if it comes up in your Win7
5) Go back into 890 GUI and see if your nas box shows up as 192.168.0.201, Click on the upper right hand side pencil and RESERVE that IP for the NAS.
Report back let us know.
BTW what NAS box are you using..Model and model #
-
After letting this 890 run this morning it finally died. Had to put my old Netgear unit back in. The reset button does nothing, only a blinking orange light. I'm done.
-
Rotohead,
FurryNutz has some GREAT advice in regards to static IP addressing OUTSIDE your DHCP range.
1) Open Router GUI
2) Identify your DHCP range, example 192.168.0.100 to 192.168.0.199
3) Your NAS box, configure it to ..... 192.168.0.201
4) reconnect NAS box to network and see if it comes up in your Win7
5) Go back into 890 GUI and see if your nas box shows up as 192.168.0.201, Click on the upper right hand side pencil and RESERVE that IP for the NAS.
Report back let us know.
BTW what NAS box are you using..Model and model #
It is a Synology Diskstation DS411 and has always worked flawlessly in all my setups.
It doesn't matter much now that the 890 died but for future how am I suppose to assign a static ip to a device that doesn't show in windows? I've asked that and no one has an answer. I understand the logic and have done static addresses in the past but DHCP is suppose to handle this. I wish the 890 would've worked properly. It did run well for a number of days then the disappearing devices started happening. I loved the range and great 11ac network for iPhone use. The UI is lacking and for the money it needs a more robust integration with windows.
-
Rotohead,
FurryNutz has some GREAT advice in regards to static IP addressing OUTSIDE your DHCP range.
1) Open Router GUI
2) Identify your DHCP range, example 192.168.0.100 to 192.168.0.199
3) Your NAS box, configure it to ..... 192.168.0.201
4) reconnect NAS box to network and see if it comes up in your Win7
5) Go back into 890 GUI and see if your nas box shows up as 192.168.0.201, Click on the upper right hand side pencil and RESERVE that IP for the NAS.
Report back let us know.
BTW what NAS box are you using..Model and model #
It is a Synology Diskstation DS411 and has always worked flawlessly in all my setups.
It doesn't matter much now that the 890 died but for future how am I suppose to assign a static ip to a device that doesn't show in windows? I've asked that and no one has an answer. I understand the logic and have done static addresses in the past but DHCP is suppose to handle this. I wish the 890 would've worked properly. It did run well for a number of days then the disappearing devices started happening. I loved the range and great 11ac network for iPhone use. The UI is lacking and for the money it needs a more robust integration with windows.
Return the dead unit, may have been malfunctioning all along and get yourself a new one and try again. Read the article below and see if this will help in assigning a static IP on the NAS.
https://global.download.synology.com/download/Document/UserGuide/DSM/5.1/Syno_UsersGuide_NAServer_enu.pdf (https://global.download.synology.com/download/Document/UserGuide/DSM/5.1/Syno_UsersGuide_NAServer_enu.pdf)
Goto page 14
-
Ya you may have had a bad unit. Please give another 890L a try.
-
Lex, does your 890L display networking devices correctly for you? ???
Rotohead,
FurryNutz has some GREAT advice in regards to static IP addressing OUTSIDE your DHCP range.
1) Open Router GUI
2) Identify your DHCP range, example 192.168.0.100 to 192.168.0.199
3) Your NAS box, configure it to ..... 192.168.0.201
4) reconnect NAS box to network and see if it comes up in your Win7
5) Go back into 890 GUI and see if your nas box shows up as 192.168.0.201, Click on the upper right hand side pencil and RESERVE that IP for the NAS.
Report back let us know.
BTW what NAS box are you using..Model and model #
It is a Synology Diskstation DS411 and has always worked flawlessly in all my setups.
It doesn't matter much now that the 890 died but for future how am I suppose to assign a static ip to a device that doesn't show in windows? I've asked that and no one has an answer. I understand the logic and have done static addresses in the past but DHCP is suppose to handle this. I wish the 890 would've worked properly. It did run well for a number of days then the disappearing devices started happening. I loved the range and great 11ac network for iPhone use. The UI is lacking and for the money it needs a more robust integration with windows.
Return the dead unit, may have been malfunctioning all along and get yourself a new one and try again. Read the article below and see if this will help in assigning a static IP on the NAS.
https://global.download.synology.com/download/Document/UserGuide/DSM/5.1/Syno_UsersGuide_NAServer_enu.pdf (https://global.download.synology.com/download/Document/UserGuide/DSM/5.1/Syno_UsersGuide_NAServer_enu.pdf)
Goto page 14
-
Lex, does your 890L display networking devices correctly for you? ???
Rotohead,
FurryNutz has some GREAT advice in regards to static IP addressing OUTSIDE your DHCP range.
1) Open Router GUI
2) Identify your DHCP range, example 192.168.0.100 to 192.168.0.199
3) Your NAS box, configure it to ..... 192.168.0.201
4) reconnect NAS box to network and see if it comes up in your Win7
5) Go back into 890 GUI and see if your nas box shows up as 192.168.0.201, Click on the upper right hand side pencil and RESERVE that IP for the NAS.
Report back let us know.
BTW what NAS box are you using..Model and model #
It is a Synology Diskstation DS411 and has always worked flawlessly in all my setups.
It doesn't matter much now that the 890 died but for future how am I suppose to assign a static ip to a device that doesn't show in windows? I've asked that and no one has an answer. I understand the logic and have done static addresses in the past but DHCP is suppose to handle this. I wish the 890 would've worked properly. It did run well for a number of days then the disappearing devices started happening. I loved the range and great 11ac network for iPhone use. The UI is lacking and for the money it needs a more robust integration with windows.
Return the dead unit, may have been malfunctioning all along and get yourself a new one and try again. Read the article below and see if this will help in assigning a static IP on the NAS.
https://global.download.synology.com/download/Document/UserGuide/DSM/5.1/Syno_UsersGuide_NAServer_enu.pdf (https://global.download.synology.com/download/Document/UserGuide/DSM/5.1/Syno_UsersGuide_NAServer_enu.pdf)
Goto page 14
Furry,
Yes ALL of my network devices show up, either wired or wireless. I renamed the ones that said Unknown devices to the proper name and all is good. In my network ALL of my clients have STATIC IP addresses, so I have no client conflict when they connect to router....in my opinion it is the best way.
I would like for DLink to add into the next FW build:
1) See which wireless clients are connected to 2.4/5ghz(1)/5ghz(2).
2) The impossible...bring back the old DLINK GUI, with a granular, in depth config for us.
3) Bridge mode function!!!!!!!!!!
I have said this in other posts, but when we pay $300 for a prosumer grade router, why would you skimp on a indepth config pages. Surely your average Joe consumer is NOT going to spend $300 on a router, there going for the cheap-get-me-on-by models, for which I can understand a SIMPLIFIED GUI.
-
Post your requests in the features and requests thread.
The old UI will not be coming back as far as I know FYI.
Furry,
Yes ALL of my network devices show up, either wired or wireless. I renamed the ones that said Unknown devices to the proper name and all is good. In my network ALL of my clients have STATIC IP addresses, so I have no client conflict when they connect to router....in my opinion it is the best way.
I would like for DLink to add into the next FW build:
1) See which wireless clients are connected to 2.4/5ghz(1)/5ghz(2).
2) The impossible...bring back the old DLINK GUI, with a granular, in depth config for us.
3) Bridge mode function!!!!!!!!!!
I have said this in other posts, but when we pay $300 for a prosumer grade router, why would you skimp on a indepth config pages. Surely your average Joe consumer is NOT going to spend $300 on a router, there going for the cheap-get-me-on-by models, for which I can understand a SIMPLIFIED GUI.
-
Well, then I hope there working a more complete GUI, with useability. If not........waiting for DDWRT ;D
-
::)