Print

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

[rotohead]

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.

[Lexist2112]

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 #

[rotohead]

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]

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.

[Lexist2112]

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

Goto page 14

[FurryNutz]

Ya you may have had a bad unit. Please give another 890L a try.

[FurryNutz]

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

Goto page 14

[Lexist2112]

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

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.

[FurryNutz]

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.

[Lexist2112]

Well, then I hope there working a more complete GUI, with useability. If not........waiting for DDWRT

[FurryNutz]