Print

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

[technik0]

dir-655 (OF COURSE!!!!) rev a3 fw: 1.35na

I have no idea what transpired prior to this issue occurring as this router was given to me (I think I know why! lol)  - anyhow, here goes:

No wired port will serve (LAN) or request (WAN) dhcp nor communicate with the network; it's almost as though the ports are VLAN'd from LAN config on router as static-assigned ip's on same subnet as router plugged into LAN ports will not communicate with router (i.e. attempting to ping router IP or browsing to admin interface) - funny part is that wireless clients have no issue receiving dhcp ip assignments and communicating with router's admin interface.   this is an isolated network, no other device is serving dhcp.

the switch functionality is working in the sense that I can static ip's on 2 pc's wired into the LAN ports and they can communicate fine, just not with the router's ip range.  connected to another network, these pc's are able to receive dhcp perfectly fine.

so... here's a head-scratcher... was thinking my next step may be to re-apply 1.35fw but wanted to bounce it off the kind folks here first.

thanks in advance...
t0

 

[FurryNutz]

Link>Welcome!
Try a Factory Reset?


Some things to try: - Log into the routers web page at 192.168.0.1.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking.

Check cable between PCs and Router, swap out to be sure. Link> Cat6 is recommended.

[technik0]

Sorry about that - should have specified that - both an admin interface reset and hardware reset have been done. And i caught your tweaks in the security cam post and attempted them as well, unfortunately, to no avail.

Using Cat 6 cabling.

I noticed an issue resolved in v1.32 that sounds similar - related to dhcp not working on port when dhcp has been disabled/enabled?

[FurryNutz]

If you what to reapply FW try following this:

FW Update Process

[technik0]

same issue after re-applying f/w

HOWEVER, for a brief moment while booting up right after the firmware has been re-applied, I had a "ping -t 192.168.0.1" running on a wired port (static ip on pc) and the router responded about 5 times (checked the arp table and the MAC's matched) and then the usual inactivity once the router booted up prevailed - this response scenario does not occur on a normal router reboot - just after re-applying the firmware (tested this 3 times now)

[FurryNutz]

Does the router work after powering OFF the router then back on?

[technik0]

inconsistently yes (maybe 1 out of 8 tries from what I tried) but only for like 4 ping replies, I wonder if that's just the f/w recovery mode replying at that step of the boot process?

[FurryNutz]

Sounds like this unit should be returned to Dlink for RMA..