D-Link Forums
The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Europe DIR-655 => Topic started by: WebCF on January 29, 2015, 12:55:41 AM
-
Hi,
I've bought an DIR-655 but actually dont want to use the WAN-feature. I've configured it to a new static IP address for the LAN and disabled DHCP, since I use another server for that.
The 4 LAN ports should act as a switch, right? Well, I've connected on Port 1 a cable to another switch (and with that, the onnection to DHCP-server is established) and on PORT 2 a PC. I can ping any local server and access the DLINK via PC on port 2 - but DHCP is not working. The PC on port 2 sends the DHCP discover but never get an answer from my dedicated DHCP.
Did I missed something? It seems, that the DIR-655 is dropping those packets. The IPv6-discover is working.
REV: C1, Latest firmware as of today (3.02b05). Tried several resets. Firewall is off (standard).
EDIT: Forgot to metion: During bott, I got an IP from my dedicated DHCP, but after complete boot, there is no communication between client <-> DCHP over the 655 possible, so I lost my IP and never get a new one.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What region are you located?
- Was a Factory Reset performed before and after any firmware updates then set up from scratch?
>FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
Please follow this: Turning a router into an AP. (http://forums.dlink.com/index.php?topic=40856.0)
-
Region: Europe, Germany
Yep, I've performed a reset several times.
Since I dont get it working, I already sent it back and try another one, so sorry if I cannot give further test results. But maybe someone have a similar issue with 3.02?
Regarding your link: The internal feature such as UPnP DHCP etc are disabled. I use an IP from class B net (172.31.30.4).
As already said: The first minute, my PC gets an IP via DHCP, than the discover packets never gets answered (tested via Wireshark).
-
I'll check with mine. I've test many routers using the link. However never used a class B address, always used 192.168.0.# address. You should have tried that to be sure. :-\