D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-685 => Topic started by: fgl30 on October 31, 2010, 05:27:13 PM
-
The problem is: some of LAN devices aren't recognized immediately.
Ex. I have one Grandstream HT-502 ATA hooked in a LAN port. The ATA is turned off, and DIR-685 is on. I turn on the ATA but it doesn't work... if I reboot DIR-685 everything works fine... These happens sometimes with other devices.... any suggestions, please? Thx
Sorry for my bad english
-
Have you tried giving it a fixed ip address and setting the ip address in the router?
-
Hmm, please, how to fix static Ip's in the router? I supposed to turn off DHCP server and choose IP's outside the routers DHCP range (192.168.0.100 - 199)?
-
Log on to the router and go to network setup at the bottom of the page is dhcp resevations fill in the boxes and save. If your unit is in the dhcp list you can click on the box that says computer name then click << and it will add the information in the boxes, then tick the check box and save. This give the same ip address to that unit. Or you can give the unit an ip address outside your dhcp range ie 192.168.0.99 it is up to you howyou do it. M
-
Ok, let me know if I understood... if I fill IPs of my devices in DHCP Reservation table (bottom of the page) but uncheck "Enable DHCP Server" in "DHCP Server Settings" (middle of the page), this means I´m putting fixed IPs? Thx
-
You do not need to uncheck "Enable DHCP Server" in the dhcp server settings if your computer works ok on dhcp.
-
I have a problem with the DHCP server where clients do not recceive an IP address until the router is rebooted. Tried upgradinf to FW 2.0.
-
I have had this problem, but do not know why. This happend to just recently I rebooted the router from the control panel in IE then it would not give ip addresses I had to power it down and up again since then it has been ok. This has been around for a while see link http://forums.dlink.com/index.php?topic=10847.0 as it says that thread it seems to be a firmware bug?